Can't run any comman+k prompts or chats.

[sweepy84]

Type: Bug

I simply cant run any any prompts. it keep erroring

The connection failed... Please check your internet connection or use a VPN and try again. If this persists, please email [email protected]. Your request ID is e123742e-3076-42a4-9db6-d7b19f5dc6a8.

VS Code version: Cursor 0.8.4 (74f6148eb9ea00507ec113ec51c489d6ffb4b771, 2023-08-24T22:55:42.209Z) OS version: Darwin arm64 23.0.0 Modes:

[truell20]

Do you have a firewall that's blocking cursor.sh?

[sweepy84]

Nope - no firewall, no vpn. After upgrading to paid version (and also updating), it now doesn't give the same error but just stops midway. Opening output window I can see

202-09-04 16:35:22.313 [error] Error: Unable to read file '/Users/peter/.cursor/extensions/quidgest.vscode-velocity-1.0.4/snippets/velocity.json' (Error: Unable to resolve nonexistent file '/Users/peter/.cursor/extensions/quidgest.vscode-velocity-1.0.4/snippets/velocity.json')
    at e.FileService.w (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:792:18206)
    at e.FileService.v (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:792:17867)
    at async e.FileService.u (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:792:17149)
    at async e.ExtensionResourceLoaderService.readExtensionResource (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:945:5862)
    at async Promise.all (index 17)
    at async e.SnippetsService.getSnippets (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:21473:5009)
    at async b (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20469:46072)
    at async fl.provideCodeActions (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:20568:45825)
    at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:849:64763
    at async Promise.all (index 5)
    at async n (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:849:65625) file:///Users/peter/.cursor/extensions/quidgest.vscode-velocity-1.0.4/snippets/velocity.json
2023-09-04 16:52:29.173 [error] [unknown] Failed to fetch: ConnectError: [unknown] Failed to fetch
    at w (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4:114683)
    at Object.unary (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4:120342)
    at async Object.availableDocs (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5:561)
    at async e.AIService.availableDocs (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:21139:3488)
    at async Object.fn (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:21969:68579)
2023-09-04 16:52:29.639 [error] [unknown] Failed to fetch: ConnectError: [unknown] Failed to fetch
    at w (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4:114683)
    at Object.unary (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4:120342)
    at async Object.reportBug (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:5:561)

[sweepy84]

It now fails every single time I run it! Very frustrating!

[AXSJ]

Having the same issue. Please help

[sweepy84]

FYI I've tested on multiple networks (e.g. iPhone hotspot) and happens regardless. I am on a Mac and have no private relay or vpn.

[dka58]

This happened to me as well after hitting my gpt-4 request limit Edit: Temporarily switching to gpt-3.5 and then back to gpt-4 fixed the issue

[bmikaili]

This happened to me as well after hitting my gpt-4 request limit Edit: Temporarily switching to gpt-3.5 and then back to gpt-4 fixed the issue

This helped me as well!

[stewones]

same here. you typically have to prompt something like "transform all these paths to named exports and keep generating until the end". it does 3 or 4 and errors out with the connection message.

[T-mac-one]

HTTP/2 setting: If you're behind a corporate proxy and having issues with Cursor Tab or Cmd K, try setting "cursor.general.disableHttp2": true in the settings.

It worked for me!!

[gorjs3540]

I've tried the solution of @dka58 @T-mac-one, but it hasn't worked out. Please help

[mcrookrumsey]

I'm also getting the same issue after updating to pro. Switching model does not help. Disabling http2 did not help.

[jeanlorencini]

Também estou tendo o mesmo problema após atualizar para o pro. Trocar de modelo não ajuda. Desabilitar http2 não ajudou.

I'm also getting the same issue after updating to pro. Switching model does not help. Disabling http2 did not help.

it seems like a general problem now https://www.reddit.com/r/cursor/comments/1fpzfsm/cursor_down/

[stemtra]

same here. Disabling HTTP/2 didn't fix it

[antoremin]

same here, started today.

[crow-1412]

HTTP/2 setting: If you're behind a corporate proxy and having issues with Cursor Tab or Cmd K, try setting "cursor.general.disableHttp2": true in the settings.

It worked for me!!

thank you very much!!!!

[VindiceCode]

Anyone have fix? Mine after changing http2 in settings.json for user is not a fix. Cursor Help is non responsive.

[Freddixx]

Not sure if this is helpful, but the reason might just be bot / misusage protection.

I noticed that Cursor would completely stop working while I was travelling. Not sure if it's the country, a dodgy WiFi or whatever heuristics their edge servers are employing.

But — once I VPN'ed into my home country — everything started working like a charm again.

Hope it helps!