New Feature: Monitoring Password-Protected Websites

The websites or web pages preferring to stay private and having a password (Basic access authentication), normally returns HTTP 401 status which ends up being marked as “down” by Uptime Robot.

Uptime Robot now has support for monitoring password-protected websites by optionally mentioning the username-password in the monitor’s settings.

The feature exists for both HTTP and Keyword monitors and can be found in the “optional settings” link of “Add New and Edit Monitor dialogs”.

P.S. The API requests, responses and documentation are updated accordingly.

If you find Uptime Robot useful, help us spreading the word:

Comments

  1. Ruben Mkv

    Awesome new features , I am simply loving it , I don’t know why not many people use uptimerobot , its super easy set up .

    I have been using this service since the time it was launched (about 1.5 years I think and its been real help in knowing who are reliable webhosting companies).

    Reply
  2. Beben Koben

    awesome…this is a good news…ty \m/

    Reply
  3. Miquel Burns

    CloudFlare can be a good reason to not use Uptime Robot. CloudFlare blocks request from Uptime Robot for some reason.

    If Uptime Robot sends their robots to a site protected by Bad Behavior, and that is blocked (they can set up a server themselves if they want), then whatever causes the block there may be the reason CloudFlare is blocking them. If their bots can get through Bad Behavior’s checks, then their bots are doing something else CloudFlare doesn’t like.

    Reply
  4. admin Post author

    @Miquel,

    CloudFlare allows only the well-known bots (Google, Yahoo, etc.) and blocks all others by default.

    Uptime Robot makes standard requests as any other visitor or uptime service would do and, as far as I know, users can allow Uptime Robot checks.

    Reply
  5. Woo Commerce

    @Miquel & @admin

    I always use CloudFlare and everything seems okay. I use HTTP and keyword check, uptimerobot running as should be. Do I miss something?

    Reply
  6. admin Post author

    @Woo Commerce,

    Actually, not sure with CloudFlare as we got mixed messages. Few users had reported that they needed to whitelist IPs and some others mentioned that everything worked great by default. Not sure.

    Maybe, they have few distributed setups and one setup is different than other, not sure again :)

    Reply
  7. barko

    When will you guys have reports we can include on our websites? Add that and you rule ;-)

    Reply
  8. admin Post author

    @barko,

    It is now very close to the top of our to-do-list.

    We want it badly too :)

    Reply
  9. kp

    hi
    how do monitoring our site.
    do we must give our address of blog or our password.
    this is a danger for site

    Reply
  10. admin Post author

    @kp,

    The password is the “basic access authentication” as mentioned but not a login or blog password. But that’s still a valuable info for many and totally optional to use.

    Reply
  11. Sam

    Big fan of the service, have used it for several years now. Great design, super easy to use, and solid. Trying to get the password authentication to work. Works great when I push the refresh button (monitor shows up) but monitor goes back down 1 minute later when the auto-check happens. Push refresh button again, monitor goes up, one minute later monitor goes down again on auto-check. Bug in the auto-check for http SSL authentication?

    Reply
  12. admin Post author

    @Sam,

    CAn you send a ticket to [email protected] with more details and we’ll check.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>