Error 1000 Suddenly on GoDaddy Hosted Website

What is the name of the domain?

ncuisao.org

What is the issue you’re encountering

My website is not resolvable currently and is presenting Error 1000

What steps have you taken to resolve the issue?

We’ve double checked our DNS entries. No changes have been made recently to DNS, it just stopped working yesterday. The A record is confirmed to be correctly pointing to the hosted GoDaddy IP. No response from Cloudflare support in approx 24 hours. We also walked through the CF support article on the topic. We are not running load balancers or using X-Forward.

Anyone else know having this issue or know if CF is working on a fix? I’ve seen other posts where, with GoDaddy and this error, the site started working a couple of days later.

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

Visit https://ncuisao.org

Screenshot of the error

Godaddy has been increasingly using Cloudflare to announce some IP ranges. Check your IP address here and if it reports it is AS209242 then it is now through Cloudflare…
https://radar.cloudflare.com

Set your DNS record to “DNS only” for a quick fix. I’m not sure of the actual fix to work with the proxy, someone will mention if they know. Ask Godaddy support if they have an alternative IP address or CNAME you can use, it may take some time to find a support agent there that knows about this.

2 Likes

Thank you - that is a new recommendation compared to other threads, so it is very much appreciated.

Unfortunately, IP 198.71.190.196 is on AS398101; GO-DADDY-COM-LLC, US per the tool.

Turning off the proxy yesterday still resulted in the same error. I just toggled it off again and will let it sit for a bit.

Turning the proxy off did not resolve the issue, and it still presents Error 1000.

If you are still getting a Cloudflare error when not proxied, it looks like the IP range is (now) using Cloudflare and something isn’t set up at the Godaddy end for your domain. Ask Godaddy support for help, it may take some time to find an agent that that understands this is happening without the Cloudflare proxy being enabled.

1 Like

Okay, thanks for the suggestions.

I did find a knowledgeable individual who offered a workaround. I hope this is helpful for someone else reading this in the future.

GoDaddy managed WordPress offers a CDN feature that I was not using. The CDN leverages Cloudflare, interestingly enough.

FIX When you toggle this feature on and refresh the GoDaddy management panel, your website is assigned a new IP address. Entering the new IP into DNS instantly resolved the issue.

Since the “Prohibited IP” error was present with and without Cloudflare’s proxy, I’m speculating it may have been on a CF internal blocklist. There are nearly 800 websites on that host, so I’d say it is plausible.

2 Likes

It’s not that. “Prohibited” in this case just means your domain resolved to a now Cloudflare announced IP address but Cloudflare didn’t know where to send the requests for your domain that it received due to not being configured by Godaddy.

Thanks for feeding back your findings, will help to explain to others what the solution is.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.