-
Notifications
You must be signed in to change notification settings - Fork 18k
proxy.golang.org 403 forbidden much like #48107 #62448
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @martinrode, would you be able to provide us with that IP or let us know which country that IP is originating from? Thanks! |
Hi,
we caught at least one affected IP which was 167.235.252.67.
Country of origin is probably Germany (or Finnland).
BR
Martin
|
Is there any update? |
Hi @suzmue, we've encountered a similar issue. The affected IP address is I've attached the complete logs from the The bottom of the logs shows that. How can we find the exact reason why it's not available?
|
CC @samthanawalla, @findleyr, @hyangah. |
@enescakir a geoip lookup for that IP reports a different, embargoed country. |
It’s an IP address from Germany (Hetzner Falkenstein) |
@enescakir sorry, it is an internal tool, and I didn't realize it disagreed with external tooling. I've hidden the specific country in my and your comment out of an abundance of caution. The exact country is probably fine to share, but also isn't relevant for this discussion: the point is that our hosting infrastructure disagrees about the location of that IP, and thinks that it is in a restricted location. Unfortunately, I also looked into filing a dispute for this IP, and it does not look feasible. Therefore, your options are to try to acquire a new IP for this machine, or wait to see if the issue resolves itself. Sorry for not being able to provide a more satisfactory solution. |
Thanks for the detailed explanation, @findleyr. We will indeed return this subnet and acquire a new one. However, the challenging question is, how can we prevent this from happening again with one of our IP subnets? |
Hey @findleyr - I had a quick question. I read @martinrode and @enescakir's comments. It looks like your internal tool is blocking some of Hetzner's IPs. Hetzner is Europe's largest bare metal and cost-effective cloud provider. https://www.hetzner.com They have regions in Germany and Finland. We'll ask to recycle the IPs on our end. However, given the internal tool, it looks like we're going to run into this issue again. What's a good way to remedy it? |
@ozgune based on my reading, it sounds like there's nothing we can really do for individual IPs. I would however hope that this is a rare occurrence, since the internal tool should meet a high standard for accuracy. If this proves to be a persistent problem, we can revisit. |
Closing this as (Unfortunately) unactionable. Will revisit if this proves to be a persistent problem. |
Using Go 1.20 in our Github CI chain, we experience 403 errors from certain IPs of our CSP (dedicated runner at our CSPs) when accessing a specific package.
Using CURL or our laptop computers and most IPs from our ISP work fine.
Our CSP is unable to block assigning that IP (if you need it, I can dig it up) to their VMs.
The text was updated successfully, but these errors were encountered: