why my websocket connection keeps timing out?
edwinencomienda
PROOP

2 months ago

So my issue is whenever so my application connects to my service which is a WebSocket server now there are times that you know like the WebSocket server would should make my connection time out for some reason. But there's also a period where it is consistent. And even my API endpoints as well is timing out for some reason. I'm kind of thinking this is kind of railway network or DNS issue. how we how I can avoid this because my app really is super dependent on web sockets because without it my application my application main function is going to be not reliable

$10 Bounty

2 Replies

edwinencomienda
PROOP

2 months ago

it seems like it was working all day yesterday, but this morning it keeps giving me a timeout for some reason


Railway
BOT

2 months ago

Your "Beyond Whisper API" service is currently deployed successfully and your websocket-api.beyondwhisper.com domain's DNS and certificate are both healthy. However, api.beyondwhisper.com has a DNS record status of "requires update" - it appears to be routed through Cloudflare's proxy (orange cloud) instead of pointing directly to us, which can interfere with WebSocket connections since Cloudflare applies its own timeouts and buffering. If you're using Cloudflare, try setting the CNAME record for api.beyondwhisper.com to DNS-only mode (grey cloud). Your resource usage is very low, so this does not appear to be a resource constraint issue. You can also check your HTTP logs and compare totalDuration vs upstreamRqDuration to confirm whether latency is introduced before the request reaches your app.


Status changed to Awaiting User Response Railway about 2 months ago


Railway
BOT

2 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...