I have been experiencing the same issue for the past five days. It starts working suddenly but then, after some time, the same WebSocket error occurs.
1 Like
Today OpenAI customer support sent me this note. I take them at face value that OpenAI is looking at the issue, actively. However, it would be nice of they send a blast mail acknowledging outage or at least someone from investigating team writes on this forum about investigation. We and many who are facing problem are startups. If we dont hear from OpenAI officially about the problem, we keep on investing our hardest commodity (Engineers) in debugging. This hurts us financially and makes us look bad in the eyes of early customers. An announcement from OpenAI solves both of these issues. cc: @kwhinnery
1 Like
Hey all - just chiming in here to reiterate that we are continuing to investigate on our side. We definitely believe what folks are seeing, we are just trying to understand and reproduce the exact conditions under which these problems are happening. We are exploring several possibilities right now. I’ll update here when we have more definitive information for you.
4 Likes
I was asked three questions by Colms, who apparently may be working with you. Providing them to you to expedite.
The answer to these questions below:
-
This is the problem. When the application works we see headers and they are correct. When the application does not work the headers are just not there. Please see below.
-
The errors that we seen in console are in the pic below:
-
The log from Terminal below:
2 Likes
I am tracking the support conversation in Intercom also, but thanks for providing that here. Will update when we have more information.
5 Likes
A big THANK YOU to @kwhinnery . He worked with me 1-on-1 and the issue has been fixed. The help came late but once he joined, things got in the right direction. I am a small player in a very large pond and appreciate the Kevin according me MVP treatment. Back to hustle now.
4 Likes
Congratulations to @kwhinnery and @chinmay1 for solving this mysterious issue! What was the exact cause, and how did you ultimately resolve it?
2 Likes
Hi everyone - thank you for your patience while we diagnosed this problem.
Our investigation showed that due to a combination of recent TLS configuration changes on our servers, and a bug in in the TLS implementation in WebSockets for some versions of Chromium, some web browsers were not able to establish socket connections to the Realtime API. That resulted in some browser clients being unable to access the Realtime preview beta models.
We have reverted our TLS configuration changes until we can roll them out in a way that will not cause disruption to Realtime API users in browser environments that have this bug.
Thank you to everyone who contributed to investigating this issue with us!
11 Likes
thanks for the resolution!
1 Like
Not sure if its completely fixed, I am still facing the issue. Tried using webrtc and the speech(audio) is abruptly getting stopped once we get the transcript available. This is happening when using tool (functions) with it. Till last week it was working perfectly fine.
1 Like
Hi!
I am quite sure that is a different issue because this topic is about being unable to create a connection in the first place when using Chrome browsers.
Please create a new topic in the API category and share some additional info.
Thank you!
This problem has come back @kwhinnery
Yes – back – its sure looking like the endpoint security is refusing anything but a “Bearer token” again…
1 Like
This time it is not working on any browser. Safari or Chrome
I have been told it wd be fixed in a few mins
Thanks for taking the time to report this, I’ve raised it with OpenAI.
1 Like
Realtime API is coming back now!
3 Likes
This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.