Custom Domains: Troubleshooting
Here are some common issues you may encounter, especially when it comes to integration with Cloudflare.
SSL errors in browser.
Possible reasons:
Wait 1h, sometimes it really does take more time to propagate.
Browser / OS cache – restart browser, restart operating system.
Proxy not enabled in Cloudflare for your subdomain.
DNS not really moved to Cloudflare (check nameservers are pointing at cloudflare such as shown below). If not, validate settings in your domain provider (e.g. GoDaddy). If all good, wait 24 hours, as sometimes it does take that long.
For nameservers verification, it may help to use whatsmydns.net. With our custom domain example used (app.freeiot.io) if we look up the root domain (DNS Propagation Checker - Global DNS Checker Tool ) the expected result should point at cloudflare.com servers:We have noticed that if SSL/TLS settings are set to Flexible instead of Full in Cloudflare settings, you will get a redirect error. Adjusting the setting to Full fixes this issue. Do not use Full (strict).
HTTPS working, but whitelabel site does not work properly
Examples are redirect loop error, visually corrupted website:
You have Personalized domain mismatch between Cloudflare settings and in the myDevices URL. Make sure that you double-check the whitelabel domain configured in the IoT Console matches what you have in your Cloudflare settings. E.g. you have the CNAME target pointed at your internal myDevices URL. E.g. app → yourcompany.mydevices.com.
Â
Â