a month ago
Every build on my service is failing with ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 402 Payment Required')) from pip during pip install -r requirements.txt. I am on the Pro plan, current project usage is $0.56, no billing issues anywhere on my account. The 402 is coming from Railway's egress proxy itself, not from any package registry. This has persisted across multiple retries over several days. Builds 28 minutes before the first failure worked fine with no config/dep changes. Please reset whatever stale flag is on my account's egress proxy.
3 Replies
Status changed to Awaiting Railway Response Railway • 28 days ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 28 days ago
a month ago
account-level stuck flag on the build egress proxy. railway-side, only their team can clear it. tag @brody with project id + the exact ProxyError(... 402 Payment Required) line from a failed build — he handles the proxy/egress side. usually resolves within a day on these.
if production is blocked while you wait, you can sidestep the proxy entirely by vendoring the deps as wheels:
pip download -r requirements.txt -d wheels/
git add wheels/ && git commit -m "vendor deps to bypass build egress"then change the install step to:
pip install --no-index --find-links=wheels -r requirements.txtugly but it removes pip's network dependency at build time so the proxy is never invoked. revert once the flag is cleared.
richwardle
account-level stuck flag on the build egress proxy. railway-side, only their team can clear it. tag @brody with project id + the exact `ProxyError(... 402 Payment Required)` line from a failed build — he handles the proxy/egress side. usually resolves within a day on these. if production is blocked while you wait, you can sidestep the proxy entirely by vendoring the deps as wheels: ``` pip download -r requirements.txt -d wheels/ git add wheels/ && git commit -m "vendor deps to bypass build egress" ``` then change the install step to: ``` pip install --no-index --find-links=wheels -r requirements.txt ``` ugly but it removes pip's network dependency at build time so the proxy is never invoked. revert once the flag is cleared.
a month ago
Hey, thanks for offering your help, and this is what stupid Claude and the Railway AI debug kept telling me the issue was as well. I actually found the 402 payment required error was being relayed from a proxy VPN service I was incorporating as a third party, and I had run out of credits there.
a month ago
yeah, fair callout. took the "from railway's egress proxy" framing in your post at face value instead of testing whether the 402 could be coming from an upstream proxy in your stack. vpn-credits-exhausted as a 402 source is also genuinely uncommon — good catch tracking it down.
Status changed to Open sam-a • 27 days ago
Status changed to Solved sam-a • 27 days ago