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 were HTTPs-enabled since day one.

However, the ones behind a custom domain (like 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:


  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 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”.

    I setup the CNAME and status page for 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?

    1. Umut Muhaddisoglu Post author

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

      1. Cătălin

        Meanwile problem solved

  2. Adam H

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

  3. Symani


  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.

  5. Z

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

    1. Bobby Wibowo

      With Cloudflare, I’m getting 526 – Invalid SSL certificate. I have it set on Full (Strict).

  6. liwanglin12

    But this might have security issue?

  7. Z

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

  8. lmspw

    Hi, i have setup CNAME for 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.

    1. lmspw

      Works now, thank you

  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..

  10. neo Felhz

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

  11. Bleery

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

  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?



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


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

      1. Umut Muhaddisoglu Post author

        Yes, if such a preventive CAA record exists, it is needed to make sure Let’s Encrypt certs are permitted.

    1. Umut Muhaddisoglu Post author

      It must be a temp issue and all fine now.

  14. Matt

    Can’t seem to get this to work. Using cloudflare disabled using cloudflare CDN but still getting the error message ‘No such site at′

    Any ideas why?

  15. Andreas

    Great, so now the “mixed content” warnings are over, finally.

    Like UTR :-)

  16. Fred Sessoms

    This seems to have stopped working. Bummer.

  17. Arcad

    The status page is really nice.

    On our website, we have a link pointing to the status page.
    Is there a way to place a “Home” link on the status page to send the user back to our home page?


  18. felixggru

    If I try to register my CNAME in following error is displayed:
    ”Bitte korrigieren Sie Ihre Eingabe. Es muss ein absoluter Servername angegeben werden, das heißt der Servername muss mit einem Punkt nach der Topleveldomain enden. IP-Adressen können nicht angegeben werden!”

  19. Colin

    Why only 7 days for the status report?

    Can we also have month report in there – is this available in the pro plan ?

    Also – can we please have incident pages / ability to add note on why downtime is happening?

    1. Umut Muhaddisoglu Post author

      We are working on displaying/paginating through the dates.

      And, announcements is an upcoming feature.

  20. Dragos

    Hi, I have setup CNAME for but it gives me SSL_ERROR_INTERNAL_ERROR_ALERT

    1. Umut Muhaddisoglu Post author

      It must be a temp issue due to the SSL issuance process. The status page now works all fine.


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>