JBM
December 12, 2020, 4:08pm
#1
It has been more than 24 hours since I pointed my DFYeCom.com custom domain to 209.151.154.183 nameserver but it still shows a 404 error.
I noticed Cloudflare is pointing to a different IP address(es)
It appears my A record may be using the wrong IP address. You can see here that 209.151.154.183 is not showing up in my DNS records.
I contacted the developer and he indicated that if I can’t get it sorted I should contact Cloudflare support for assistance with the setup.
Any help would be much appreciated
sdayman
December 12, 2020, 6:20pm
#2
Domains here should use Cloudflare’s name servers. If you want to use a different name server, you would need to change this at your domain registrar.
That’s because Cloudflare is proxying your traffic.
JBM
December 12, 2020, 6:50pm
#3
Actually, they are. My domain nameservers are pointing to Cloudflare
And the Cloudflare A record is pointing to the correct IP
According to this, it should be working fine
But it still is showing a 404 error
Can’t figure out what is wrong except for the fact that it is showing a different IP in mytoolbox
Any other suggestions?
Thanks
sdayman
December 12, 2020, 6:57pm
#4
JBM:
Actually, they are.
Then this comment is not clear to me, unless you meant web server.
I see you’re getting a 404 when using HTTPS. Was your site working with HTTPS before you added it to Cloudflare?
JBM
December 12, 2020, 7:42pm
#5
Good point. Actually, it is a brand new domain so the answer is no, it did not have HTTPS before Cloudflare.
Do you think that is the problem?
I also noticed it is registering the traffic so I have no idea why the 404 error.
Thanks
sdayman
December 12, 2020, 8:30pm
#6
That’s a significant problem.
Flexible
The connection between your visitor and Cloudflare is secured, but the connection between Cloudflare and your server is not. You will not need a certificate on your server for this mode. This option is NOT RECOMMENDED.
Flexible makes your site only partially secure - it encrypts the connection between the visitor and Cloudflare - this means they see the in their browser and the site leaves the impression to be secure! However the connection between Cloudflare and your origin se…
404 errors still count as traffic.
JBM
December 12, 2020, 9:09pm
#7
Thanks for your help, much appreciated but I am still confused why the A record is using a different IP than the one I added. Also, the domain is pointing to Cloudflare’s Nameservers, so everything should be working fine, but I am still getting a 404 error.
I turned off the SSL/TLS and it still gives me a 404 error, so it must be something else.
Any other suggestions?
sdayman
December 12, 2020, 9:24pm
#8
Let’s back up a bit and take Cloudflare out of the loop. Go to the Overview tab in dash.cloudflare.com and click “Pause Cloudflare on Site” in the lower right corner. It will take five minutes for this to take effect. Then see if the site starts working again.
JBM
December 12, 2020, 9:45pm
#9
Paused it and now the A record is showing the correct IP…BUT, I am still getting a 404 error
Do I enable it?
sdayman
December 12, 2020, 9:48pm
#10
Then it’s a server issue you need to resolve with your host.
1 Like
sdayman
December 12, 2020, 10:18pm
#12
If it’s not hosted anywhere, what is your developer working on?
sdayman
December 12, 2020, 11:09pm
#14
Ok, that’s where it’s hosted and you need to work this out with them.
JBM
December 12, 2020, 11:55pm
#15
Mystery solved!!! I had entered the domain with Capital letters, and that was triggering all the problems
Thank you so much for taking the time to help me troubleshoot the issue
2 Likes
system
closed
December 17, 2020, 11:55pm
#16
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.