The last 3 days I, and others aswell, have experienced a bug with the online version of ChatGPT.
When Prompting a message, I see no response. If I check the console log I get the following error:
TypeError: Failed to execute 'getReader' on 'ReadableStream': ReadableStreamDefaultReader constructor can only accept readable streams that are not yet locked to a reader
at em (_app-ee0b14f890279a08.js:26:2445631)
at eP (_app-ee0b14f890279a08.js:26:2447847)
When I dig into the problem it seems there is an issue with some permission headers since I also get:
Error with Permissions-Policy header: Unrecognized feature: 'document-domain'.
Checking the payload I can also see that I get in the “t” the event:
“Async Response Took Too Long to Come Back”.
The names of the different chats in the Chat History is also only named “New chat” for every new chat I try.
I have tried disabling all blockers, such as Ublock Origin, Disconnect, cleared cookies, browser cache, localStorage, Session Storage. I have also tried multiple browser such as Edge and Chrome.
Researching online I find multiple reports where some is able to resolve it by disabling Privacy Badger. This does however not work for all and I do not have this extension installed. I have also tried to disable any windows related network blockers.
If I try on the mobile version I correctly get a streaming response and if I change to my work computer at work, so af different network it also works as expected.
If I refresh the browser after i receive the network response “t” I can see the full response, sometimes.
Somes times I also get the folowing error from the console.
app-ee0b14f890279a08.js:26 WebSocket connection to 'wss://chatgpt-async-_app-ee0b14f890279a08.js:26 WebSocket connection to 'wss://chatgpt-async-webps-prod-eastus-4.webpubsub.azure.com/client/hubs/conversations?access_token=OMITTED' failed:
(OMITTED: this is my access key I have Omitted for obvious reasons )
_app-ee0b14f890279a08.js:26 Uncaught (in promise) Error: [object Event]
at _socket.onerror (_app-ee0b14f890279a08.js:26:2550220)
Furthermore, if i use the API Access it also works perfectly fine, but is quite slow.
It could be awesome if someone at OpenAI would either response to some of the support tickets or at least give a heads-up if this is an issue on their end or on our end…