I just replaced the IP in an A record that had been working fine with the IP of a new Digital Ocean droplet. The previous IP that was working fine was also a Digital Ocean IP in the same data center.
All the issues mentioning this problem seem to be people putting in a Cloudflare IP but this is not my case.
The IP address I have put in is the IP assigned by Digital Ocean, not a Cloudflare IP, I’ve checked and double checked.
That message does not come from your request. Apparently the request does go through Cloudflare to your server, but your server then proxies onwards and that request gets the 1000 error. Check out the client IP address it mentions on the page.
Okay… This server is a copy (snapshot) of the previous one that was working. Nothing special in my Nginx config. It’s a dev server, not critical, but this is weird.
For some reason it will proxy the requests onwards, apparently to a host with a forbidden address or possibly to itself, but thats something only your server logs and configuration can tell you.
