Possible Issue with the Edge Proxy?
lucak5s
PROOP

a year ago

Hi, I'm encountering an issue with my Next.js application on railway when sending requests with a larger payload (around 50KB for a base64 image). The first request goes through successfully, but all subsequent requests (even with smaller payloads) remain pending. This only happens when I use a custom domain that I have configured on railway.

With the custom domain, the first request shows a successful response, but after that, no further requests are processed. The response shows 'server: railway-edge'. The other unsuccessful requests do not show up in any logs as far as I can tell.

However, this problem does not occur when I use a railway-generated domain, where all requests, including larger payloads, are processed without issues. The responses on the railway-generated domain also show 'server: railway'. Additionally, this blocking behavior only affects larger payloads, as smaller payload requests always work perfectly even on my custom domains. This also never happens when testing locally.

I would appreciate any help!

Solved

5 Replies

lucak5s
PROOP

a year ago

Okay, now I have the same problem even on the railway generated domain…


lucak5s
PROOP

a year ago

Generated a new random railway domain, and it worked again for some minutes (with the server showing as 'railway'). It stopped working now with the server in the response showing as 'railway-edge'



This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response angelo-railway over 1 year ago


Hey Luca,

We did find the issue you reported, traffic should be restored normally. Is this the case?

Thanks,
Angelo


Status changed to Awaiting User Response Railway over 1 year ago


lucak5s
PROOP

a year ago

Hi Angelo,

Thank you for the update. Everything seems to be working properly now.

Best regards,
Luca


Status changed to Awaiting Railway Response Railway over 1 year ago


Status changed to Solved angelo-railway over 1 year ago


Loading...