a year ago
I’m having random issues with my endpoint in railway responding with a 499 status code. As an example I have a simple 200 ok response to a simple heath check monitor and it still responds with a 499 but the odd part is it happens every night at 12:00am MST
9 Replies
a year ago
499 is an issue with your app.
499 means the client closed the connection, this happens when your application takes too long to respond and the client ends up closing the request, this can happen with client side timeouts, or simply from a user closing the browser tab mid request.
I have an uptime Kuma in railway. The test endpoint does nothing but responds with 200ok I see same issue
a year ago
something is happening in your code at 12 am MST that prevents your application from returning a response in a reasonable amount of time
a year ago
sounds good
a year ago
going to mark this as solved though, given this isn't a platform issue and we unfortunately don't provide application level support
a year ago
!s
Status changed to Solved brody • over 1 year ago