3 months ago
Hello team,
We are recently facing lots of 502 bad gateway issues on all my projects, which are made separately, and on refresh, it works fine for a while.
Please check it as it seems to be related to Railway latest change, as one of my application were not changed yet facing it as wello.
Appreciate the help.
2 Replies
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
I believe it is related to serverless, and the cold start of the application, however the feature is really needed as some of my apps are not used 24/7 but when needed.
2 months ago
Hey, thanks for the report. You're correct that this is related to serverless wake-up. We've identified a bug where the gateway gives up too quickly while the service is starting, and we're tracking a fix internally.
In the meantime, if you need to avoid the 502s, you can disable serverless sleep on the affected services as a workaround until we get this resolved. We'll follow up once the fix is out.
Status changed to Awaiting User Response Railway • 2 months ago
Status changed to Solved jake • 2 months ago