Repository navigation
[BUG] [deepseek-web] 502 Error: DeepSeek error: onmessage is not defined #2680
The BugWhen trying to use the DeepSeek Web Cookie Provider with a valid user token, the model fails to stream responses and returns a The console/dashboard displays the following error: The Steps that i made
Expected BehaviorThe local proxy should successfully capture the stream from DeepSeek's web endpoint and return the completed response to the client. If DeepSeek recently updated their web client's stream structure, the parser is likely failing to bind the message listener correctly. |
Replies: 3 comments 1 reply
|
Hey @xspylol! Thanks for the very specific report — this is a real bug. I traced it to The file is a Web Worker bundle. At the end of the body it does a bare I have opened issue #2724 to track the fix (probably by stripping the worker-only block from the bundle at extract time so it loads cleanly under CJS). The model itself works — the 502 is only raised because we throw on load before reaching the fetch. As a workaround until the patch ships, you can try |
|
Closing this thread as stale due to inactivity. No maintainer follow-up happened after the last maintainer message for over 15 days. If this is still relevant, feel free to open a new discussion with updated logs/steps and I’ll pick it up with fresh context. |
Glad it helps, @xspylol! I'll keep #2724 updated as soon as the strict-mode patch lands and ping you here so you can re-test. Appreciate the report -- specific repro like yours is what made the root cause obvious in 5 minutes.