Configuring Cloudflare for Status Pages (with Custom-Domains)

Cloudflare is an impressive service/platform for securing and speeding-up websites.

If you use Cloudflare and have a “status page with a custom-domain” in Uptime Robot, “there may be a small configuration needed” to make sure things work smooth.

Who needs the custom configuration?

If the 3 items below match your case, then the custom config is needed:

  1. Use Cloudflare as your domain’s DNS provider
  2. Have a status page with custom domain in Uptime Robot
  3. Have the “Crypto” setting as “Flexible” in Cloudflare

How to make the custom config?

That is so easy:

  1. Login to your Cloudflare account
  2. Click the domain of your status page
  3. Click “Page Rules>Create Page Rule”
  4. Enter *MyStatusPageCustomDomain* (like **) into “If the URL matches” field
  5. Click “Add Setting>SSL>Full”
  6. Click “Save and Deploy”
  7. That’s it.

And, here is a screenshot of the setting:

Custom Domain Status Page

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


  1. Andrey

    Thank you!!
    I tried to connect it last week and it did not work out, and here is your article ❤️

  2. Mauricio Freitas

    We have Full SSL setup but still see a SSL Handshake error in our status page through Cloudflare. Any ideas?

    1. Umut Muhaddisoglu Post author

      Any issues must be clarified now.

      1. S

        I’m still getting the Handshake Failed error from Cloudflare. Tried Full and Strict page rules for the

  3. Gaming

    Great work guys!

  4. Rodrigo Aguilar

    I did this but i’m gettin an error, it says “Error 525: SSL handshake failed”, any ideas on how to solve this?

  5. Frank

    here comes the solution !

  6. Aiden Andrews

    Tried this last night my crypto is set to Full for all my domains on my account, CNAME is in place tested it this morning and get Error 525 SSL Handshake failed.

    Please Advise.


  7. Comms

    Hi still having trouble. What should we be putting down as “status”

  8. Charles R. Severance

    I fixed this by simply bypassing the CloudFlare proxy for the subdomain. This reveals the real IP address of – but it saves a page rule – which might cost you money.


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>