Failed to upload code with status code 403 Forbidden with CLI
aikoze
PROOP

10 months ago

$ railway open

$ railway check_updates

You are on the latest version of the CLI, v4.5.5

$ railway status

Project:

Environment: production

Service:

$ railway redeploy

Redeploy the latest deployment from service in environment production? Yes

The latest deployment from service has been redeployed

$ railway up

Indexed

Compressed [====================] 100%

Failed

Failed to upload code with status code 403 Forbidden

$ rm -rf .railway

$ railway logout

$ railway login

Logged out successfully

Unable to parse config file, regenerating

Unable to parse config file, regenerating

Open the browser? Yes

Logged in as email@domain.com

$ railway link

Select a workspace

Select a project

Select an environment production

Select a service

Project linked successfully! 🎉

$ railway up

Indexed

Compressed [====================] 100%

Failed

Failed to upload code with status code 403 Forbidden

Solved

6 Replies

Railway
BOT

10 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


10 months ago

Hi, is this issue recurring/consistent or a one-off?


Status changed to Awaiting User Response Railway • 10 months ago


ben5516
PRO

10 months ago

Did you ever get this working? I'm currently having the same issue and it's blocking production deployment (sigh).


Status changed to Awaiting Railway Response Railway • 10 months ago


ben5516

Did you ever get this working? I'm currently having the same issue and it's blocking production deployment (sigh).

chandrika
EMPLOYEE

10 months ago

Hey Ben, just replied on your other thread with us where you figured this one out 🙌

OP, could you please try re-clone or deploy from a new folder? There may be some unintended temporary or dot files causing a time out


Status changed to Awaiting User Response Railway • 10 months ago


chandrika

Hey Ben, just replied on your other thread with us where you figured this one out 🙌 OP, could you please try re-clone or deploy from a new folder? There may be some unintended temporary or dot files causing a time out

fut
HOBBY

9 months ago

worked thanks


Status changed to Awaiting Railway Response Railway • 9 months ago


Beautiful, going to close this one out.


Status changed to Awaiting User Response Railway • 9 months ago


Status changed to Solved angelo-railway • 9 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...