New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: keepalive ping timeout; no close frame received #326
Comments
For this issue, the socket isn't receiving any data nor the keepalive message. That is expected behavior, but the SSL error is of concern. I don't have enough experience with the older version, so I will need to take some time to look at it. PS: I re-opened this issue #183 in order to take a look at it, but not sure when I am going to get time as I have a bunch of things on my plate. |
@SandraRodgers said she would take a look at this issue and the other one since she has more knowledge about the |
We recently migrated to v3 and implemented the flag This error seems to occur occasionally, but once it starts, it prevents us from receiving any further transcripts through that connection. Despite setting the keepalive flag, this issue persists. It would be helpful if there are specific troubleshooting steps or additional configurations we should consider to mitigate this issue |
Hi @ToxicityMax This reported issue is for |
@ToxicityMax any success with this. I too get "WebSocketException: received 1011 (internal error) Deepgram did not receive audio data or a text message within the timeout window. See https://dpgr.am/net0001; then sent 1011 (internal error) Deepgram did not receive audio data or a text message within the timeout window. See https://dpgr.am/net0001" even if keep alive is passed as true. |
Hi @rutvik106 If this is for Since we get this question a lot, here are some examples to demonstrate expected failures when not using and also how to utilize the feature: correctly #348 |
What is the current behavior?
I get the following error intermittently while sending audio packets over the deepgram socket connection.
This is often followed by the log
Steps to reproduce
P.S. the reason why I'm using the
_socket
object is that I'm usingdeepgram-sdk==2.11.0
and I had reported an issue in the past with this version. As you mentioned, the issue was fixed in a new major version, but we haven't gotten around to updating it since it had been working fine for us all this while.Expected behavior
The socket connection should not close abruptly.
Please tell us about your environment
Operating System/Version: Linux 5.10.209-198.812.amzn2.x86_64 (AWS Ubuntu)
Python Version: 3.10.12
Other information
This error only occurs once in a while, and most often when there are multiple parallel socket connections to deepgram live.
The text was updated successfully, but these errors were encountered: