502 Error On Sleepy Apps
btnalexandre
PROOP

a year ago

Hello,

I'm coming back to you regarding the Railway team's announcement of a fix for error 502 when cold starting an application in sleep mode.

It works very well on public URLs, but I still get 502 errors on URLs on the Railway private network. Is this normal? Is there a fix in the pipeline?

Thanks for your help.

Solved

5 Replies

brody
EMPLOYEE

a year ago

For the internal network you should have your request on a retry, it would not be feasible to patch that on the internal network due to there not being a proxy to hold and retry traffic while the container wakes up.

btnalexandre
PROOP

a year ago

Oh okay thanks for your quick reply and these details.

brody
EMPLOYEE

a year ago

You can think of the private network like a local LAN network, just with IPv6 and a DNS server for convenience, there's really no easy way to hold onto traffic and replay it like we can on the public edge proxy.

btnalexandre
PROOP

a year ago

Yeah I understand slightly_smiling_face emoji

So I will use on my main project in Next.js the lib fetch-retry-ts to handle 502 responses, and retry after a certain amount of time.

brody
EMPLOYEE

a year ago

Perfect! we're glad the changes have worked for public traffic!

+11

Status changed to Solved brody • over 1 year ago

Loading...