Node.js App Wake from Sleep 502 Status Code
I have two environments set up for an app I'm deploying, one for staging new features, and another in case I somehow mess up the staging branch.
The latter is set to sleep, so when my app makes a request to my railway app, it gets a 502 error in return as opposed to perhaps keeping the connection for a little longer.
Is there anyway to either allow more time before a 502 is returned, or somehow configure the return message to be more helpful than "Application failed to respond".
I'm tempted to use associate the 502 error with App Waking, but that obviously doesn't seem like the right way to handle this error.
proj id: a83758cd-7f2e-490a-814b-83a31c1dc56d
Solution:Jump to solution
@jason
We've resolved an issue where apps with longer startup times were showing 502 errors. Apps now have up to 10 seconds to start accepting traffic, thus preventing these error pages from appearing.
You will need to trigger a deployment so that the changes we have made take effect....
3 Replies
Project ID:
a83758cd-7f2e-490a-814b-83a31c1dc56dwe are aware of this issue, it's not the user can do to fix it.
I've added your thread to our internal ticket so that I can update you when it's solved.
Solution
@jason
We've resolved an issue where apps with longer startup times were showing 502 errors. Apps now have up to 10 seconds to start accepting traffic, thus preventing these error pages from appearing.
You will need to trigger a deployment so that the changes we have made take effect.