Failure: 403 Forbidden

[Raphael]

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

[Sam Small]

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.

[Raphael]

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

[Sam Small]

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.

[Sam Small]

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.