During last two days, I continuously met the internal error issue. I submited the case through app, but no reply. I tried every solution I could ,restart, clean cache, can’t works, anyone can help?
I did the network diagnostics, it’s ok.
An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.
at mAf (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9278:6675)
at zYi (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9278:5410)
at mTp (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9279:11972)
at Object.classify (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9279:16501)
at vAf (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9279:5856)
at async lYo.runWithSharedTurnRunner (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9279:15853)
at async YH.runAgentLoop (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15854:72761)
at async q1a.streamFromAgentBackend (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15882:14489)
at async q1a.getAgentStreamResponse (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15882:24576)
at async eDe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9452:2491)
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Describe the Bug
Whatever my request are, after 2-3 minutes, the system show this internal error. “An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.”
Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!
IDE, Agent , auto
submit a request
3. after couple minutest, the bug appears
Expected Behavior
it should work well, or tell what’s going wrong.
at mAf (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9278:6675)
at zYi (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9278:5410)
at mTp (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9279:11972)
at Object.classify (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9279:16501)
at vAf (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9279:5856)
at async lYo.runWithSharedTurnRunner (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9279:15853)
at async YH.runAgentLoop (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15854:72761)
at async q1a.streamFromAgentBackend (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15882:14489)
at async q1a.getAgentStreamResponse (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15882:24576)
at async eDe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9452:2491)
can't use for 3days
Hey, thanks for the detailed report with stack traces and the Request IDs. That helped a lot.
I checked your Request IDs. On our side the requests completed normally, then the server just stopped receiving data from the client. The BAD_DECRYPT error from BoringSSL means TLS packets are getting corrupted somewhere on the network path between you and our servers. So this is a transport level issue, not an on our servers outage like the generic message says. I know that message is misleading.
A typical sign is that short requests like network diagnostics work, but long agent streams break. That often happens with a VPN, a corporate proxy, a network accelerator, or antivirus HTTPS scanning that interferes with long lived connections.
What to try, in order:
Settings → Network → HTTP Compatibility Mode → HTTP/1.1 or enable Disable HTTP/2. HTTP/1.1 changes framing and connection lifetime and often avoids corruption on long HTTP/2 streams. This is the first thing to try.
Turn off your VPN, network accelerator, and antivirus HTTPS or SSL scanning, or add Cursor to the allowlist.
Quick test: connect using a different network, like a phone hotspot, and see if the error still happens. If it works on another network, the issue is definitely in the original network path.
Let me know if switching to HTTP/1.1 helps. If it still happens even on another network, we can dig deeper.
