2 months ago
Containers will not start and my services return 502 right now.
Attachments
Pinned Solution
2 months ago
the deploy is being stuck on "configuring network" for 5 mins - thats usually railway side, not you. cancel it and redeploy, and check status.railway.com if other people's containers arent starting either.
but the 502 is probably a port mismatch. vaultwarden listens on port 80 inside the container and railway's proxy doesnt know that. go to service settings → networking → click edit on your public domain and set the target port to 80. or add a variable ROCKET_PORT=8080 and set the domain target to 8080, either works.
if it still 502s after the deploy actually finishes, paste your deploy logs
1 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 2 months ago
2 months ago
the deploy is being stuck on "configuring network" for 5 mins - thats usually railway side, not you. cancel it and redeploy, and check status.railway.com if other people's containers arent starting either.
but the 502 is probably a port mismatch. vaultwarden listens on port 80 inside the container and railway's proxy doesnt know that. go to service settings → networking → click edit on your public domain and set the target port to 80. or add a variable ROCKET_PORT=8080 and set the domain target to 8080, either works.
if it still 502s after the deploy actually finishes, paste your deploy logs
Status changed to Solved medim • 2 months ago