Skip to content
WebSocket Connection Issues - US East to Brazil
sermi13
OP

a year ago

Project id: aa9a5ad0-1ff9-44a2-b309-6127aaafee57

I have this production environment for a modified version of the Chatwoot project. As of today (20/06), my clients started experiencing issues with WebSocket connections to my app.

My project is entirely on US East (Virginia, USA) and my users are from Brazil - São Paulo.

There wasn't any update - it just started having issues. Some connections have timeouts (rare), but the main issue is WebSocket connections constantly resetting and not staying open.

I've checked service status on all my services and found no incidents, including my DNS (Bunny DNS).

This post is mainly to see if anyone else is having similar WebSocket trouble right now.

Solved

16 Replies

jamela08

a year ago

I think I’m seeing the same issue. My users are getting logged out a few minutes after logging in, even though nothing has changed on the backend and sessions should be valid.


timurkin

a year ago

I'm not sure if it's related but we do have the same problem with SSE. Connection drops in the middle of requests.


sermi13
OP

a year ago

Totally valid! Could be a problem caused by the latest package drop incident, or maybe even just general instability.

I have new relic connected to my app and have seen some timeout errors showing up too.


muhammetakkurtt

a year ago

I have a similar problem, connections close after 20-30 seconds with error 1006.


a year ago

hello, thank you for the reports, we will be looking into this


gustavocryptofring

a year ago

yo there,i think i have smth similar to this problem,coz me webpage says that lost connecting like once a 60-12 sec

and always i can see that log

its triple coz of 3 active users on page

1385680686178111528


gustavocryptofring

a year ago

so im not sure if its problem in my code socket connecting or in host


sermi13
OP

a year ago

Ty Brody!


sermi13
OP

a year ago

I've downgraded the metal edge domain like Brody said to in another thread, but I'm still having issues with websockets not staying alive.


namrastanov

a year ago

Downgrading helped in my case. I was getting unexpected web socket closures with the close code 1006.


simonberens

a year ago

Yep I've been getting websockets closed on me since this morning.

Project ID 0967f744-e6ac-4b09-b47e-996248d6c08f


a year ago

Thank you for letting us know, we are actively working on a fix.


a year ago

Hello all,

We have fixed the regression on the Metal proxy and confirmed that WebSockets and SSEs do not drop anymore.

Please re-enable the Metal edge if you had disabled it.


simonberens

a year ago

Why wasn’t this issue surfaced on the status page?


muhammetakkurtt

a year ago

The same problem started again


muhammetakkurtt

The same problem started again

a year ago

I'm was not able to reproduce this issue after we rolled out the fix, and I just tried again and still cannot reproduce.

So please open a new thread.


Status changed to Solved brody • over 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...