Hi, Error starting server would be coming from your app - I see you have a healthy deploy now, were you able to resolve the issue ?

Hi, Error starting server would be coming from your app - I see you have a healthy deploy now, were you able to resolve the issue ?

The problem is not due to errors in the application because when the application wouldn't start, I restored the old deployment, but it still didn't work. Only a rollback helped.

I restored the old deployment, but it still didn't work. Only a rollback helped.

Can you clarify the difference between restoring the old deploy vs rolling back ?

I'd also like to reaffirm that this error is coming from your application and does not come from our platform.

My application works very smoothly on the local machine, and from the logs in Railway, I'm not even able to figure out what the problem is

You might need to add more error logging/catching to your app. You could also check if your environment variables are up to date on railway.

You might need to add more error logging/catching to your app. You could also check if your environment variables are up to date on railway.

i have still problem witch this deployment, there are no error f810822a-7001-499a-a643-9d01a7688e96

that deployment is old though, your new ones are fine ? not sure why you're looking to "fix" an old deployment. the latest ones I see are either fine or application errors