Subscribe
Quick links
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.
IMPORTANT: These settings don’t work with flattened CNAMEs, disable this feature first.
Who needs the custom configuration?
If the 3 items below match your case, then the custom config is needed:
- Use Cloudflare as your domain’s DNS provider
- Have a status page with custom domain in Uptime Robot
- Have the “Crypto” setting as “Flexible” in Cloudflare
How to make the custom config?
That is so easy:
- Login to your Cloudflare account
- Click the domain of your status page
- Click “Page Rules>Create Page Rule”
- Enter *MyStatusPageCustomDomain* (like *status.mydomain.com*) into “If the URL matches” field
- Click “Add Setting>SSL>Full”
- Click “Save and Deploy”
- That’s it.
And, here is a screenshot of the setting:
In case it’s not working check the change the DNS settings to OnlyDNS (grey cloud) instead of Proxied (orange):
19 replies on “Configuring Cloudflare for Status Pages (with Custom-Domains)”
Thank you!!
I tried to connect it last week and it did not work out, and here is your article ❤️
We have Full SSL setup but still see a SSL Handshake error in our status page through Cloudflare. Any ideas?
Any issues must be clarified now.
I’m still getting the Handshake Failed error from Cloudflare. Tried Full and Strict page rules for the status.domain.com
Great work guys!
I did this but i’m gettin an error, it says “Error 525: SSL handshake failed”, any ideas on how to solve this?
here comes the solution !
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.
07/06/18
Hi still having trouble. What should we be putting down as “status”
Thanks
I fixed this by simply bypassing the CloudFlare proxy for the status.tsugicloud.org subdomain. This reveals the real IP address of stats.uptimerobot.com – but it saves a page rule – which might cost you money.
If I set CF to:
* Strict: times-out with 525 http error
* Full: times-out with 525 http error
* Flexible: redirect-loop (e.g. triest to redirect to https:// URL even though I am accessing it from https://
If I disable reverse-proxy, then the https fails because there is no valid cert for my domain.
Cheers,
Hi there,
not sure if you are still having the issue, but if you do, please send us all the details to support@uptimerobot.com and we will be happy to take a look at it 🙂
Because of this issue i am leaving uptimerobot my spent more than 3-4 hr in cloudflare handshake issue.
Hi Akhbar, our customers don’t report such issues and usually, we’re able to help them get this right. I understand you probably already left us, but we’ll be happy to take a look at any issues you might have and help you.
still Having the 525 cloudflare handshake error, can anyone fix this or provide fix for this issue?
Please help!
Hi,
please send us the details to support@uptimerobot.com and we’ll be happy to take a look at it, if you believe your CNAME DNS settings are correct you can also check with Cloudflare, just to be sure.
This worked for me. Thank you.
Still doesn’t work.
Returns Error 525 SSL handshake failed.
Please contact us at support@uptimerobot.com and share all details, thank you.