RPC showing forbidden access 403
Hi. I've got some crypto related script which pings an RPC server - it works fine locally but on railway the server is blocking all requests with 403 forbidden, perhaps knowing its a development call instead of user. Any ideas to get around it?
13 Replies
Project ID:
N/AN/A
railway would not be blocking you, whatever you are calling is blocking you
I appreciate that. It does work for other RPCs I've tried but this particular one for some reason is blocking requests coming from the app hosted on railway and not local
they could be blocking gcp, railway runs on gcp, someone in the past may have abused the rpc server and caught a block, and ips are shared, so you got blocked too
Yeah good shout, wonder if theres some kind of proxy that could be put in place to get around that
there is plenty of proxy services you could use
but what id do is take a gamble and create a totally separate railway project, and hope that you land on a different host that doesn't have its ip banned
cheers will give that a go
since i think it goes without saying, but railway cant do much for you if some server chooses to block one of railways hosts
No luck with creating new projects, tried a few times
ah then I'm sorry but you'll have to look into using a proxy in your code
I shall look into it, cheers for your help
no problem