Cursor stopped working after I updated it to version 3.8.11

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

It functioned perfectly fine before the update. I update the app with almost every new release, so the previous version I was using must have been 3.8.10. Right after upgrading, it became unusable. I’ve disabled HTTP/2 and set up the proxy as usual—none of these settings have been modified at all.I tried rolling back the version, but I couldn’t find 3.8.10, so I downgraded to 3.7.42. Unfortunately, it still doesn’t work.
Request ID: 1862ae3d-3c1e-42f6-8159-277459bb947f
[internal] Failed to establish a socket connection to proxies: PROXY 192.168.0.127:7890
RetriableError: [internal] Failed to establish a socket connection to proxies: PROXY 192.168.0.127:7890
at Nk1 (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35723:27652)
at Eag (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35723:26381)
at Wk1 (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35724:7469)
at Mag.run (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35724:12367)
at async zle.runAgentLoop (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48116:2927)
at async W$g.streamFromAgentBackend (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48187:13900)
at async W$g.getAgentStreamResponse (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48187:22728)
at async hut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35854:1970)
at async Object.oo [as onSubmit] (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47078:33305)
at async vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44977:103149

Steps to Reproduce

Open cursor
Use any model

Operating System

Windows 10/11

Version Information

3.8.11, 3.7.42.

Does this stop you from using Cursor

Yes - Cursor is unusable

4

hey @congcongzhidao, you can try switching to a lower http version in the network settings of cursor, it’s easy and it should fix all your issue, start by selecting 1.1 instead of 2.0 and if that doesn’t work, you can try 1.0, it should fix all your issue, even on the latest version

6

it doesn’t work

7

I delete C:\Users\Administrator\AppData\Roaming\Cursor\User\globalStorage,now,it cannot log in.

8

oh, maybe your installation was corrupted, I advise you to reinstal cursor with a fresh download, also, have you try to launch a fresh chat without past messages in it? one thing that may have led to that is either corrupted or malformed chat, if you don’t want to lose the context of it, you can just refference it using “@” and selecting past chat

11

How to uninstall cursor,I uninstall from control ,and install a new one ,version 3.7.42. It also cannot log in,I try the edge and sougou (chrome core) ,web can log in ,and I click ‘yes,log in’,cursor has no react.

12

Hey, thanks for the detailed report and the log. This isn’t about version 3.8.11, that’s why rolling back to 3.7.42 didn’t help. The error Failed to establish a socket connection to proxies: PROXY 192.168.0.127:7890 means Cursor is trying to use your local proxy at 192.168.0.127:7890, but it can’t connect to it.

192.168.0.127 is a local network address. The most common reasons are:

  • The proxy app Clash, v2ray, etc isn’t running
  • The proxy machine’s IP changed, DHCP gave it a new address
  • That machine is off or not reachable

What to do:

  • Check the proxy is actually running and reachable, for example telnet 192.168.0.127 7890 or ping. If the address changed, update it in your settings.
  • If you don’t need a proxy, remove it from Windows system proxy settings and from Cursor settings Ctrl+,, search proxy, then fully restart Cursor.

About login after deleting globalStorage. It’s most likely the same cause, the login flow can’t reach the app through the proxy. Try this:

  • Ctrl+, then search proxy support
  • Find Http: Proxy Support and set it to on so Cursor uses the Windows system proxy
  • Restart Cursor and click Sign In again

If you do need the proxy, but the address or port is different, you can set it manually in settings.json. Use Ctrl+Shift+P then Open User Settings JSON:

{
  "cursor.general.disableHttp2": true,
  "http.proxy": "http://192.168.0.127:7890",
  "https.proxy": "http://192.168.0.127:7890",
  "http.proxyStrictSSL": false
}

Replace the address and port with the correct ones. A detailed breakdown is here: OAuth login silently fails behind local proxy — fix is changing one default setting

Let me know if you can reach the proxy, the next steps depend on that.

13

i have the same issue, but wierdly other than cursor itself everything is fine.
Cursor Network Diagnostic Results

FAILED (4): API, Ping, Chat, Agent

DNS: Success
Logs:
[2026-07-02T02:38:41.182Z] Host: api2.cursor.sh
[2026-07-02T02:38:41.182Z] Servers: 10.30.10.47,10.30.10.34
[2026-07-02T02:38:41.182Z] Resolved to 44.218.197.23 in 1ms
[2026-07-02T02:38:41.185Z] Resolved to 44.218.197.23 in 1ms
[2026-07-02T02:38:41.188Z] Resolved to 44.218.197.23 in 3ms
[2026-07-02T02:38:41.191Z] Resolved to 44.218.197.23 in 2ms
[2026-07-02T02:38:41.193Z] Host: api2.cursor.sh
[2026-07-02T02:38:41.193Z] Servers: system
[2026-07-02T02:38:41.193Z] Resolved to 98.82.103.121, 54.204.187.99, 54.163.169.83, 54.86.48.209, 54.146.199.111, 54.243.155.247, 34.230.206.74, 44.218.197.23 in 1ms
[2026-07-02T02:38:41.193Z] Resolved to 98.82.103.121, 54.204.187.99, 54.163.169.83, 54.86.48.209, 54.146.199.111, 54.243.155.247, 34.230.206.74, 44.218.197.23 in 1ms
[2026-07-02T02:38:41.194Z] Resolved to 98.82.103.121, 54.204.187.99, 54.163.169.83, 54.86.48.209, 54.146.199.111, 54.243.155.247, 34.230.206.74, 44.218.197.23 in 0ms
[2026-07-02T02:38:41.194Z] Resolved to 98.82.103.121, 54.204.187.99, 54.163.169.83, 54.86.48.209, 54.146.199.111, 54.243.155.247, 34.230.206.74, 44.218.197.23 in 0ms
[2026-07-02T02:38:41.194Z] Result: true

SSL: Running
Logs:
[2026-07-02T02:38:41.166Z] Start
[2026-07-02T02:39:04.006Z] URL: undefined
[2026-07-02T02:39:04.006Z] Status: undefined
[2026-07-02T02:39:04.006Z] IP: undefined
[2026-07-02T02:39:04.006Z] Issuer: undefined
[2026-07-02T02:39:04.006Z] Name: undefined
[2026-07-02T02:39:04.006Z] AltName: undefined
[2026-07-02T02:39:04.006Z] DNS Time: undefinedms
[2026-07-02T02:39:04.006Z] Connect Time: undefinedms
[2026-07-02T02:39:04.006Z] TLS Time: undefinedms

API: Error: [unavailable]
Logs:
[2026-07-02T02:38:41.166Z] Start
[2026-07-02T02:39:04.067Z] Error: ConnectError: [unavailable]

Ping: Error: [unavailable]
Logs:
[2026-07-02T02:38:41.166Z] Sending ping 1
[2026-07-02T02:39:04.096Z] Error: ConnectError: [unavailable]

Chat: Error: [unavailable]
Logs:
[2026-07-02T02:38:41.167Z] Starting streamSSE
[2026-07-02T02:39:04.178Z] Error: ConnectError: [unavailable]

Agent: Error: [unavailable]
Logs:
[2026-07-02T02:38:41.168Z] Starting stream
[2026-07-02T02:38:41.168Z] Pushing first message
[2026-07-02T02:39:04.135Z] Error: ConnectError: [unavailable]

Marketplace: Success
Logs:
[2026-07-02T02:38:41.163Z] Host: marketplace.cursorapi.com
[2026-07-02T02:38:41.704Z] Response in 541ms
[2026-07-02T02:38:41.704Z] Response: 200
[2026-07-02T02:38:41.704Z] Response Type: cors
[2026-07-02T02:38:41.704Z] Server: null
[2026-07-02T02:38:41.704Z] Result: OK in 541ms

Authentication: Success
Logs:
[2026-07-02T02:38:41.164Z] Host: prod.authentication.cursor.sh
[2026-07-02T02:38:42.535Z] Response: 200 in 1371ms

Authentication UI: Success
Logs:
[2026-07-02T02:38:41.166Z] DNS lookup: authenticator.cursor.sh
[2026-07-02T02:38:41.182Z] Resolved authenticator.cursor.sh to 104.18.35.233 in 1ms

Cursor Tab: Success
Logs:
[2026-07-02T02:38:41.166Z] DNS lookup: api3.cursor.sh
[2026-07-02T02:38:41.251Z] Resolved api3.cursor.sh to 104.18.18.125 in 84ms

Agent Endpoint: Success
Logs:
[2026-07-02T02:38:41.166Z] DNS lookup: agent.api5.cursor.sh
[2026-07-02T02:38:41.183Z] Resolved agent.api5.cursor.sh to 50.18.248.73 in 1ms

Codebase Indexing: Success
Logs:
[2026-07-02T02:38:41.166Z] DNS lookup: repo42.cursor.sh
[2026-07-02T02:38:41.184Z] Resolved repo42.cursor.sh to 52.44.193.86 in 1ms

Downloads: Success
Logs:
[2026-07-02T02:38:41.165Z] Host: downloads.cursor.com
[2026-07-02T02:38:42.132Z] Response: 403 in 967ms

CDN: Success
Logs:
[2026-07-02T02:38:41.165Z] Host: cursor-cdn.com
[2026-07-02T02:38:41.574Z] Response: 404 in 409ms

14

hey @ZulfikarHD, have you tried switching to http 1.1 in the network settings?

15

Same issue, after login the left most bottom panel not able to display the account details (Even with http 1.1), only works after I downgraded to cursor 3.5 .

image
image739×226 18.5 KB

16

thank you for the follow up, but, im currently use the http 1.1 setting and also trying the http 1.0 setting with this same issue, i never use the http 2.0 because my windows or the company setting disabled my http 2.0 for “security purpose” they say.

17

Hey, there are a few different issues mixed together in this thread, so let’s split them up.

@ZulfikarHD, your case is different from the original one. DNS works for you, but API/Ping/Chat/Agent fail with ConnectError: [unavailable], while Auth/Marketplace/Downloads work. This is typical behind a strict corporate proxy or SSL inspection. Normal HTTPS goes through the main process, which respects the proxy, but AI requests use a separate transport that the proxy blocks or buffers. Switching the HTTP version won’t help because the issue is the network itself.

What to try:

  1. App Settings Ctrl+Shift+, then find HTTP/2 and enable Disable HTTP/2, or in settings.json:
    "cursor.general.disableHttp2": true,
"http.proxy": "http://<your-proxy>:<port>",
"http.proxySupport": "override",
"http.proxyStrictSSL": false
  2. Fully close and restart Cursor. Quit it completely, don’t just Reload Window.

But since your company disabled HTTP/2 “for security”, you’ll most likely need an IT-side fix. They need to allow or bypass SSL inspection and allow bidirectional streaming SSE without buffering for these domains:
*.cursor.sh, *.cursor.com, *.cursorapi.com, *.cursor-cdn.com

More details:

@elvincth, separately about the screenshot with getaddrinfo ENOTFOUND for authenticator.cursor.sh, api3.cursor.sh, agent.api5.cursor.sh, repo42.cursor.sh. That means DNS is not resolving the endpoints at all, so the network or firewall is blocking them at the DNS level. Only an IT allowlist for the domains above plus a working DNS can fix it. Changing HTTP versions or proxy config won’t fix this.

To avoid confusion since everyone has different setups and versions, please start separate threads for your own cases and include your Cursor version Help > About, your OS, and the full Network Diagnostics output. Then I can debug each one. This is known behavior on 3.9.x behind restrictive proxies. I can’t share an ETA for a fix yet. As a temporary workaround, some users roll back to 3.8.24 and disable auto-updates.