SSE Connection Fails with HTTP/2 Error on Railway After 5 Minutes
saidovzohid
TRIALOP

a year ago

We are experiencing an issue with our service when deployed to Railway, where SSE (Server-Sent Events) connections encounter a failure after running for 5 minutes and 0 seconds. The specific error observed is as follows:
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)

Details:

Environment:

• Deployment works as expected on AWS Lightsail, where SSE connections remain stable.

• The issue occurs consistently on Railway, suggesting an environment-specific problem.

Symptoms:

• Events are received successfully for 5 minutes.

• After 5 minutes, the connection terminates with the above error.

What We Tried:

• Deployed the service on AWS Lightsail for verification. SSE works perfectly without termination.

• Tested on Railway but encountered the same behavior on Railway.

Solved

2 Replies

saidovzohid
TRIALOP

a year ago

screenshot of error after 5m0s

Attachments


brody
EMPLOYEE

a year ago

Hello,

We have a standard 5 minute timeout for http requests on our platform, you would want to handle reconnections on your side.

Best,
Brody


Status changed to Solved brody 11 months ago


Loading...