Failed to establish a socket connection to proxies: PROXY 127.0.0.1:7897DHe: [internal] Failed to establish a socket connection to proxies: PROXY 127.0.0.1:7897at Dlk (

Support Help
1

Request ID: 8190bf2b-1f66-4f37-a4de-d7d5ae04fcc7
[internal] Failed to establish a socket connection to proxies: PROXY 127.0.0.1:7897
DHe: [internal] Failed to establish a socket connection to proxies: PROXY 127.0.0.1:7897
at Dlk (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35695:26781)

5

Hey, thanks for the report. This error means Cursor is trying to route traffic through a proxy on your machine at 127.0.0.1:7897 (usually a proxy client like Clash), but nothing is responding on that port. Most likely the proxy client was running in the morning, then it got closed or changed its port.

What to try:

  1. If you’re intentionally using a proxy, make sure the client is running and still listening on port 7897. If the port changed, update it in Cursor settings via http.proxy and also in the Windows system proxy settings.
  2. If you don’t need a proxy, remove it in Windows: Settings > Network & Internet > Proxy (turn off both manual and auto), then clear http.proxy in Cursor settings and restart.
  3. For a quick check, run Cursor once with --no-proxy-server. If that fixes it, the proxy is definitely the cause.

Windows note: Chromium (which Cursor is based on) can keep picking up proxy settings from the system registry even after you turn it off in the proxy client UI. So if you closed the client but the error is still there, check the Windows system proxy settings.

Let me know if that helps.