Hetzner Oregon region IP's blocked by sites
I was tracking down why my app couldn't make http requests after moving to Hetzner. Initially, I suspected openssl handshake issues based on the error messages, but after making sure that all the versions were the same to compare with a working host, I realized that the oregon region IP's are just blocked. Support was quick to answer, suggesting creating another instance / IP. However, all the IP's were 5.78.x.x, and they all appear to be blocked as well.
$ curl https://www.google.com -vvv # snip
403. That’s an error.
Your client does not have permission to get URL / from this server. That’s all we know. * Connection #0 to host www.google.com left intact
Creating another VM in Virginia region running the same commands work:
$ curl https://www.google.com -vvv 302 Moved 302 Moved The document has moved here.
In this technical retrospective (2024), @jollyjerry shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
In case you haven't done so already, please let our support team know about this at the end of your support ticket: "Support was quick to answer, suggesting creating another instance / IP. However, all the IP's were 5.78.x.x, and they all appear to be blocked as well. [...] Creating another VM in Virginia region running the same commands work." It can be helpful for our team to know what troubleshooting works. And thank you in advance. --Katie
A buddy and I have both run into the bad IP range in Oregon. We moved to using VMs in Virginia. It wasn't worth chasing down the bad IP range. I always use a blacklist check - https://mxtoolbox.com/blacklists.aspx - for instance.