Failure: 403 Forbidden

[raphaelfff]

I realise that this is a dup of #1005, but I am not in Russia, this is happening in GCP

Logs:

$ buf mod update -v --debug ../protos
DEBUG   File "buf.yaml" does not specify the "name" field. Based on the dependency "buf.build/bufbuild/protovalidate", it appears that you are using a BSR instance at "buf.build". Did you mean to specify "name: buf.build/..." within "buf.yaml"?
DEBUG   get_config      {"duration": "258.173µs"}
DEBUG   buf.alpha.registry.v1alpha1.ResolveService/GetModulePins        {"duration": "278.760863ms", "net.peer.name": "buf.build", "rpc.system": "connect_rpc", "rpc.service": "buf.alpha.registry.v1alpha1.ResolveService", "rpc.method": "GetModulePins", "rpc.connect_rpc.error_code": "permission_denied"}
DEBUG   command {"duration": "300.248146ms"}
Failure: 403 Forbidden

[smallsamantha]

Hi @raphaelfff! Do you mind sharing a bit more information about the structure of your project and the contents of your buf.yaml?

In case it's helpful I've attached a sample project that imports buf.build/bufbuild/protovalidate - you can run buf mod update and buf build from the root of the sample project without logging in to the BSR if you'd like to experiment with it. Additonally, more info on the usage of protovalidate can be found here.

[raphaelfff]

I had my repo cloned in 2 machines:

• M1: Public IP: 34.141.127.71: Failure: 403 Forbidden
• M2: Public IP: <redacted>: It works as expected

I since requested a new public IP for M1, and stuff started working again, main goal of this ticket is understanding why this IP got blocked and making sure it doesnt happen again as its pretty disruptive

[smallsamantha]

Understood @raphaelfff - we're looking into this issue with the blocked IP, apologies for the inconvenience and I'll let you know when I have an update.

[smallsamantha]

Hi @raphaelfff thanks for your patience! Wanted to let you know that we've investigated this and it seems that the blocked IP was caused by an issue with our cloud provider. This was a bug and not expected so you should not experience this again. If it does please do let us know.

[ProvoloneStein]

Hi! I have the same problem. German IP

[doriable]

@ProvoloneStein Hi, could you provide additional information, e.g. the version of the CLI, the command you're running, and the debug logs, preferably on a new issue, unless your repro conditions match exactly here. Thanks!

[willavos]

I'm seeing a similar problem, but flakier. buf --version is 1.47.2.
I don't think it's a problem with the buf executable. In fact if I curl https://buf.build/settings/user it fails ~50% of the time with a 403 Forbidden.

This is on a box (Hetzner) located in Helsinki. I think some of your machines post load-balance don't like our IP address?

[nicksnyder]

Here is the entry in our documentation that explains the situation and recourse: https://buf.build/docs/bsr/bsr-faqs/#why-am-i-getting-403-forbidden-errors-in-my-ci-workflows-or-in-the-bsr-web-application

Going to lock further discussion on this old issue. If you think you have a net-new problem that is different than is what is described in the above documentation, please file a new issue.