Moved nameservers from netlify to cloudflare but DNS mappings doesn't seem to be working
I deleted all dns records and the site itself from netlify, changed the nameservers on my domain registrar over to cloudflare servers and got the message that my website is active on cloudflare.
DNS Setup is Full so everything is managed by cloudflare.
I was trying to setup a tunnel but since that wasnt working I've tried to redirect to another external site that I know is online with a valid SSL cert using a CNAME record.
I've also paused cloudflare processing to make sure nothing else is interfering.
On whois I can see that the cloudflare nameservers are being used and I can also see the CNAME record
There are also some A records present that I have not defined.
Finally, going to the website produces:
Secure Connection Failed
An error occurred during a connection to magnoliarun.be. Peer reports it experienced an internal error.
Error code: SSL_ERROR_INTERNAL_ERROR_ALERT
I can see the domain being hit in the DNS analytics so it seems that queries are indeed hitting the cloudlfare name servers.
Looking for advice on how to proceed...
5 Replies
Hello! You are redirecting to HTTPS, but you are serving a certificate from the server, hence the error.
You are also not using Cloudflare's CDN, but that's not relevant to the error itself.
I'm not sure what you mean by that exactly. Since I paused cloudflare I would assume that the configuration doesnt matter anymore but to test it I've set Current encryption mode:
Off (not secure) and disabled Automatic HTTPS Rewrites under edge certificates.
Yes, pausing cloudflare means you are going directly to the origin, which is exactly what I see… the server doesn’t allow for encrypted connections, so it will fail to connect to port 443.
Oh, one thing. I’m not sure what that DNS records screenshot is, it’s not cloudflare’s… the records in Cloudflare are still what counts, pausing Cloudflare won’t pause DNS resolution, otherwise your site will break. It paused all other services.
I got it working in the end, I suspect that even though cloudflare was saying everything was active that maybe some things hadnt switch over properly yet and the CNAMe might have been wrong. Anyway, thanks for helping!
No problem!