Backend not showing An unexpected error occurred on our servers. Please try again, or contact support if the issue persists

Describe the Bug

Request ID: 079bb68f-ac53-48b5-88ba-744e0fb82f30
[internal] The debug configuration was not set up properly
LTe: [internal] The debug configuration was not set up properly
at kmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38337)
at Cmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37240)
at $mf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)
at ova.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)
at async qyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34190:57047)
at async Wpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:7695)
at async Wpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34239:8436)
at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)

Steps to Reproduce

It’s blocking

Expected Behavior

unblock

Operating System

MacOS

Version Information

Version: 2.4.21 (Universal)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin x64 23.6.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report. This looks like a known issue with the HTTP/2 connection.

Try this workaround:

  • Open Cursor Settings CMD+,
  • Search for “HTTP/2”
  • Switch HTTP Compatibility Mode to HTTP/1.1
  • Restart Cursor

If that doesn’t help, run Network Diagnostics (Cursor Settings > Network) and share the results here.

Thanks so much! It took a while and just automatically fixed on its own when I waited for a while and hit refresh. but I am getting another error now which is all my history are gone…

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.