a year ago
I having a problem after each deploy, so I receive an error 500 in Railway in the first call time, after first call works well but if I deploy a new version I have the same problem, first call error 500 and the next calls 200.
Doing tests I think it's problem in Railway platform but I don't know the reason.
17 Replies
a year ago
No, after 503 service unavailable message while image is updating, I receive 500 error in the first api call
a year ago
what kind of app is this?
what do the deploy logs say when you get the 500 error code?
a year ago
Is a Java application with Spring boot and not register any logs with this 500 error, for this reason I think that maybe is for Railway platform
a year ago
this error would be from your app, if you arent getting logs please make sure you are logging errors.
a year ago
I'm catching all errors with 500 code and this error is not inside my application.
a year ago
I have only 500 error first time service call after deploy new image.
a year ago
please make sure you are logging all errors, without errors there's unfortunately not much we can do to help.
a year ago
I'm sure that the application is catching all errors and for this case not print anything so I'm sure that it's happening something with Railway after each deploy.
a year ago
In the first error 500 the application not receive any request and for this reason, first, is not possible logging any error and second, I think that is happening something with Railway.
a year ago
Okey I think that I will need to change platform, thanks.
a year ago
I'm sorry you feel that way, but the 500 error code is not coming from railway, I would love to help but there's nothing I can help with if your app isn't doing error logging.
a year ago
I already told you that the application captures all errors.
a year ago
And I'm catching all errors from Exception so I should be errors in observability If the problem was the application.
Also If the problem was the application, should be fail every time but it only fails the first request after deploy or after large time without using with this 500 Internal Server Error, after this first request it works well.
Attachments
a year ago
the application is not catching this error, railway will not send a 500 error. the only error railway will send would be 503.