Origin 1016 error

[user5601]

Answer these questions to help the Community help you get started.

What is the domain name?
www.lanet.mx

Have you searched for an answer?
Yes

Please share your search results url:
Nothing has been useful

When you tested your domain, what were the results?
The domain gets to cloudflare dns

Describe the issue you are having:
I migrated my site to cloudflare, it used to have only dns so I tried the full solution after migrating nameservers to cloudlfare I got all the dns options on the cloudflare dashboard but cannot access my site I get 1016 Origin error, I added the origin server IP to the WAF and nothing still the same result,

What error message or number are you receiving?
1016

What steps have you taken to resolve the issue?

1. Check nameserver
   2.Check dns propagation
2. Added origin IP to WAF

Was the site working with SSL prior to adding it to Cloudflare?
Yes

What are the steps to reproduce the error:

1. try to go to www.lanet.mx

Have you tried from another browser and/or incognito mode?
yes 5 computers, cleared cache, copokies, flushdns, incognito, chrome, mozilla edge

[user5601]

[Chaika]

Those records don’t make much sense. It looks like the auto import got confused by your setup, or you changed it wrongly after. It looks like you already switched back to your old DNS, if you still want to switch to Cloudflare, I would manually import/make sure all of your records in Cloudflare are the same as in you current DNS, the automatic import/discover DNS Stuff isn’t perfect:

How to eliminate (or minimise) downtime when adding your domain to Cloudflare

When you add your domain using the correct procedures, your site should not experience any downtime during the change. These tips cover the full DNS setup in Cloudflare. Completing the setup in the following order should eliminate any downtime. Add the site to Cloudflare - in your Cloudflare dashboard, add the site to your account. Check that all your DNS records are correct - when you add your site, Cloudflare will scan the most common records, however, you need to check that they all mat…

Specifically, the CNAME Records on lanet.mx and www make no sense and are causing this issue. Looking at your current configuration, it looks like you’d want both www and lanet.mx to be a simple A record to “209.216.78.154”

[user5601]

Hi I returned the records to my server, I just see the reverse records for the cname and the ww, then what they should be?

Regards,

[user5601]

Hi thanks I only proxied and putted the A record for lanet.mx and did a cname for www that goes to lanet.mx I think its working now

Regards,