Railway instance getting 'Error starting server' on redeploy with new (or same) environment variable
I had a Medusa backend instance running on Railway (completely fine since December). Just changed a single environment variable (was trying to add to the CORS), and then got errors on the re-deploy, and the instance never came back up. Nothing else changed. And when I change the variable back to its previous value, it also fails... I can 'rollback' and it works though. So I'm now 'stuck' with an old deploy I can't make any changes to... Can anyone interpret the deploy logs below (in the next message for length)?
The build logs look fine too until the health check fails as a result of the server not starting...
project id:
a9d9c589-b108-418d-951e-f5817ea3bc1f
Any ideas would be amazing, or let me know if more info needed...
3 Replies
Project ID:
a9d9c589-b108-418d-951e-f5817ea3bc1f
Logs below:
Note that when I 'rollback' it says it will use the OLD environment variables (what I want) but then the UI shows the new ones.. Same in the CLI. Is there any way to see the ACTUAL environment variables being used by an instance?
these logs look bleak, that's usually a sign of structured logging, you can hover over the line and click the plus button on the left to expand them so you can look at it's attributes