Status Pages>Custom Domains are now HTTPs-enabled

https-smallPublic Status Pages, a feature to easily share the statuses of the monitors with others, was introduced few months ago.

The standard status page URLs (like https://stats.uptimerobot.com/xyz) were HTTPs-enabled since day one.

However, the ones behind a custom domain (like http://status.mywebsite.com) were not as it was a little more tricky to get a SSL certificate for all the custom domains.

Good news, custom domains are now HTTPs enabled too (thanks to the free + automated CA: Let’s Encrypt).

And, all status pages are actually HTTPs-only from now on.

Important note for CloudFlare users:

As the status pages are now HTTPs-only, the “flexible SSL feature of CloudFlare” will end up in an infinite redirect. There are 2 options to make it work:

  • disabling the “cloud feature” for the CNAME
  • or, using Full or Strict SSL feature
If you find Uptime Robot useful, help us spreading the word:

Comments

  1. Daniel Aleksandersen

    This is a cool feature and a good application of Let’s Encrypt!

    However, this doesn’t seem to work correctly. Over HTTPS, I receive the certificate for status.uptimerobot.com instead of a certificate for the expected domain. If I ignore the error, the expected status report pops up. However, over HTTP, I get a generic error saying “No such site at 69.162.67.140:80”.

    I setup the CNAME and status page for status.ctrl.blog just minutes ago. If this is a temporary situation, then maybe stick a message on the page clarifying that things are being configured and will start working in a little while.

    Update: Tried again just before submitting this comment, and now it says “Safari Can’t Open the Page”. Do I need a uptime monitor for my uptime monitor status page?

    Reply
    1. Umut Muhaddisoglu Post author

      We had few glitches regarding auto-SSL generation for each custom domain. Yet, they are all resolved now :).

      Reply
      1. Cătălin

        Meanwile problem solved

        Reply
  2. Adam H

    Great work guys, Always felt a little dirty not seeing https on the status page, all good now :)

    Reply
  3. Symani

    Awesome!!!

    Reply
  4. Tore Skevik

    We are also having some issues with the custom status page. Albeit I just recently configured it, but it throws an SSL error in both Firefox and Chrome.

    Reply
  5. Z

    Interestingly, CloudFlare is unable to establish HTTPs connection with uptimerobot, I’m using full (strict) :/

    Reply
  6. liwanglin12

    But this might have security issue?

    Reply
  7. Z

    Still getting invalid certificate after 2 weeks, CF passthrough disabled.

    Reply
  8. lmspw

    Hi, i have setup CNAME for stats.lmspw.com but it gives me SSL_ERROR_INTERNAL_ERROR_ALERT
    The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

    Reply
    1. lmspw

      Works now, thank you

      Reply
  9. Joonas Loppi

    I suffered from the Cloudflare “not working” issue.

    Would have been great if you’d have notified of this breaking change in advance instead of just a footnote in a blog post.

    On a separate issue my services went down, and when I had an emergency it was not fun to notice that the status page was broken as well..

    Turning off the Cloudflare proxy solved the issue. I kept receiving SSL handshake error or something like that..

    Reply
  10. neo Felhz

    That’s Great!
    I have my domain HSTS. Now I can use uptimerobot pages with my domain!

    Reply
  11. Bleery

    That’s awesome, but why the issue with the Cloudflare flex ssl certs?

    Reply
  12. Rohit

    Hi ! I have tried setting up the alerts for one of the monitors but looks like it doesn’t send any confirmation email to my corporate email id but sends it to my personal id if i add one. How can sign up my corporate id for the alerts?

    Thanks,
    Rohit

    Reply
  13. CHANG, PING-HSING

    Hello, my custom domain is https://stats.tjc.host/ , it shows “ERR_SSL_PROTOCOL_ERROR”.
    I use both HSTS and DNS CAA on my domain, are they incompatible with this service?

    Reply
    1. CHANG, PING-HSING

      It seems that the issue of certificate is blocked by DNS CAA record.
      The problem solved when I added
      0 issue “letsencrypt.org”

      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>