Connection error: Connection failed. Please try again, or contact support if the issue persists

Support Help
1

Request ID: 1db51bb8-8dc8-42f9-95ff-20e2cee1e8c3
[unavailable] PING timed out
Mpe: [unavailable] PING timed out
at yy1 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35721:27577)
at hsg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35721:26306)
at Iy1 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35722:7469)
at wsg.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35722:12370)
at async Ble.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:48122:2927)
at async yJg.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:48193:12152)
at async yJg.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:48193:20412)
at async Xct.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:35852:1973)
at async Object.Qs [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:47076:33305)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44975:103626

5

Hey, thanks for the report with the Request ID and stack trace. The PING timed out error means the live connection between Cursor and our servers dropped in the middle of the request, so the keepalive ping didn’t get a response in time. The backend did receive your request and retried a few times before showing the error, so it’s almost certainly an issue in the network path between your machine and our servers, not your account or the model.

If this happens on every request and doesn’t go away in a new chat, try this:

  1. Cursor Settings > Network > Run Diagnostics. If anything fails, send the results here.
  2. In the same place, switch compatibility mode to HTTP 1.1.
  3. Restart or disable your VPN if you’re using one, or try a different network.

Another user with the exact same error fixed it by switching compatibility mode to HTTP 1.1. Let me know if that helps.

6

Request ID: 3c123e47-f6d6-4eb7-b808-66ed6ca14c8e
No resource accessor found for composer: 2e16c7f3-941c-4c4f-881a-e7a7e486a980
Error: No resource accessor found for composer: 2e16c7f3-941c-4c4f-881a-e7a7e486a980
at jXm.streamFromAgentBackend (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24426:5853)
at jXm.getAgentStreamResponse (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24426:22754)
at DIe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12054:740)
at async Object.fd [as onSubmit] (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:23360:34887)
at async vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:21257:102920

Screenshot 2026-06-21 120746
Screenshot 2026-06-21 120746651×922 24.1 KB

i switched to http 1.1 also the network diagnostic also came clean, both errors shown in screenshot disappeared, but in chat with agent, still it shows (even after computer restart) connect error

Screenshot 2026-06-21 121624
Screenshot 2026-06-21 1216241272×942 47.5 KB

7

Thanks for the update and the screenshots. I can see you already enabled HTTP 1.1 and diagnostics passes, but in one of the runs Chat and Agent still fail with “Streaming responses are being buffered by a proxy” and “Bidirectional streaming is not supported by the http2 proxy”. These messages mean something on the network path (proxy, VPN, corporate firewall, or antivirus) is interfering with the streaming connection, and agent chat depends on streaming.

Let’s try this step by step:

  1. Fully disable HTTP/2, not in the Network tab, but in App Settings: Ctrl+Shift+, > search for “HTTP/2” > turn on Disable HTTP/2 > fully quit and reopen Cursor. This is a different toggle from compatibility mode.
  2. If you use a VPN, proxy, or corporate antivirus (Zscaler and similar), temporarily turn it off and test again.
  3. To confirm it’s a network issue, connect to a completely different network, like a mobile hotspot, and run the request. If it works there, the issue is in your current network or proxy.

For the error “No resource accessor found for composer”, that’s a separate issue and not related to PING or streaming. It looks like a stale link to a chat. Start a new chat and see if it happens there too.

Can you share what network you’re on (home, corporate, or mobile), whether you have a VPN or proxy, and which Cursor version you’re using? That’ll help narrow down where the connection is getting blocked.