10 months ago
Hello, my staging environment is returning a 502 Bad Gateway after successful deployment.
Deploy Logs:
Starting Container
May 19 06:59:44
using config from file
May 19 06:59:44
adapted config to JSON
May 19 06:59:44
admin endpoint disabled
level:"warn"
logger:"admin"
ts:1747663183.4841776
replica: 1e34f241-5273-4a2c-a051-530109e9eb3f
View in ContextCopy as JSON
May 19 06:59:44
automatic HTTPS is completely disabled for server
May 19 06:59:44
started background certificate maintenance
May 19 06:59:44
server running
May 19 06:59:44
serving initial configuration
May 19 06:59:44
cleaning storage unit
May 19 06:59:44
finished cleaning storage units
Does this have to do with the upgrade to Railway Metal? This service was working fine earlier yesterday.
Project id: 81de2d9c-830a-4d31-b73d-af7da5d8d890
8 Replies
10 months ago
I don't think Railway Metal is the culprit here.
What are you trying to deploy?
Interesting. It's a simple React project that's been live on Railway a long time, the production environment seems fine, but now I'm hesitant to push things from stage to prod
10 months ago
What are you using to build? Do you have a Dockerfile or are you using Nixpacks or Railpack?
If it's a long running deployment it may have been built using Nixpacks, since then Railway introduced the new builder Railpack.
10 months ago
You can check in the service settings which builder it is using
True. I'm using nixpacks currently, but I'll try with Railpack and report back!
@Medim rebuilding with Railpack worked. Issue is resolved. Thank you!
10 months ago
i'm glad it worked <:salute:1137099685417451530>, gonna mark this as solved.
10 months ago
!s
Status changed to Solved medim • 10 months ago