Hi @delvai
Once you have set your domain to “DNS Only” in Cloudflare, it’s right that you will see a certificate error. Only once that is set up can we issue the certificate. Please let us know when you’ve done that, and we’ll go ahead with setting up the certificate. Then everything should work correctly!
Okay I just set it back to DNS Only.
I set it back to Proxied a few days back and left it like that since it seemed to have resolved the issue, but now it’s re-occurring.
Please let me know any other steps to take, and also any steps I can take to prevent this from happening again in the future. Thank you very much.
Great. The changes haven’t propagated yet, but once we see the domain pointing to the correct Anvil IP, we’ll issue the certificate.
That looks good to me. Right now CloudFlare’s own DNS server is still returning the old IP, but hopefully that will change soon:
$ nslookup <YOUR_DOMAIN> 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
Name: <YOUR_DOMAIN>
Address: 198.185.159.144
The CloudFlare DNS server is still returning the same incorrect IP address. You may want to take this up with them!
Hi @daviesian ,
I’ve just checked both nslookup and dnschecker, and they both confirm that my domain is now pointing to the IP address 52.56.203.177.
Could you please check again and verify this on your end?
Yep, now we see this too, and your certificate is (finally) issued and working! Thanks for your patience. Hopefully this resolves the issues - please let us know if not.
It’s finally okay, thank you!
Is there anything I can do to prevent this issue from re-occurring? Or was the fact it was Proxied the cause of all the issues prior?
I believe that was the issue, yes. So hopefully all should be good from now on!
