WebSocket Streaming STT Connectivity Issues on Production (Hosted on Railway) #1338
Replies: 4 comments
-
Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently. |
Beta Was this translation helpful? Give feedback.
-
Hey there! It looks like you haven't connected your GitHub account to your Deepgram account. You can do this at https://community.deepgram.com - being verified through this process will allow our team to help you in a much more streamlined fashion. |
Beta Was this translation helpful? Give feedback.
-
It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?
|
Beta Was this translation helpful? Give feedback.
-
Language is Nodejs |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Deepgram Support,
I’m reaching out regarding an issue we're facing with the Deepgram real-time WebSocket API in our production environment, which is currently hosted on Railway (trial plan).
While the integration works perfectly in local and staging setups, the WebSocket connection either fails to establish or drops intermittently when deployed to production on Railway. We’ve verified that authentication and configuration are correct.
To help troubleshoot, could you please confirm:
If there are any known compatibility or connection issues with Railway-hosted environments?
If there are any connection limits, timeouts, or specific headers/settings required to maintain a stable WebSocket session?
If possible, can you provide any server-side logs or diagnostics from your end for our recent connection attempts?
We’d really appreciate your assistance, as this issue is impacting a critical part of our application.
Beta Was this translation helpful? Give feedback.
All reactions