10 days ago
```
$ railway open
$ railway check_updates
You are on the latest version of the CLI, v4.5.5
$ railway status
Project: <project-name>
Environment: production
Service: <service-name>
$ railway redeploy
> Redeploy the latest deployment from service <service-name> in environment production? Yes
The latest deployment from service <service-name> 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 <your-workspace>
> Select a project <project-name>
> Select an environment production
> Select a service <service-name>
Project <project-name> linked successfully! ๐
$ railway up
Indexed
Compressed [====================] 100%
Failed
Failed to upload code with status code 403 Forbidden
```
4 Replies
10 days 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!
Status changed to Awaiting User Response Railway โข 9 days ago
3 days 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 โข 3 days ago
ben5516
Did you ever get this working? I'm currently having the same issue and it's blocking production deployment (sigh).
2 days 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 โข 2 days ago