Photo by Michael Vi / Shutterstock.com
Building a website is one thing but hosting it and properly managing traffic is another. Admins have to deal with DNS records, CNAMES and a bunch of other things on the backend to keep the site up and running. While there are tools and services to help with these, troubleshooting any errors can still be a hassle at times.
In this article, we’re talking about Cloudflare error 1014, its causes and what you can do to fix the problem.
What causes this error?
The error is generally triggered when you’re using two different domains with Cloudflare and one has a CNAME record pointed towards the other. This is fine as long as the domains are under the same Cloudflare account, but if you’re using different accounts, you’re going to have to use Cloudflare for SaaS to fix the problem.
How to fix the problem?
Try the following three fixes to fix the issue.
Disable Cloudflare on one domain
Disabling Cloudflare on the domain with the CNAME record pointing to the second one will resolve this error as this will resolve the CNAME conflict. Note that if you want to continue using Cloudflare on both domains, you’re going to have to use Cloudflare for SaaS to fix the issue.
Change the CNAME
Changing the CNAME to an A record pointing to the same server can also resolve the conflicting CNAMEs on both domains and eventually resolve the issue. Note that the exact steps for the procedure will be different based on your domain registrar.
Contact Cloudflare support
If nothing else works, the best option is to contact Cloudflare support and have them fix the problem for you. Alternatively, you can ask a question on Cloudflare’s community forum to see if someone experienced the same problems as you before and the steps they took to fix them.
Also read: How to fix Cloudflare error 1015?
Someone who writes/edits/shoots/hosts all things tech and when he’s not, streams himself racing virtual cars.
You can contact him here: [email protected]