# Cursor started ignoring Http 1.1 Proxy settings **URL:** \ **Category:** Bug Reports\ **Created:** [July 1, 2026, 6:23pm UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581 "2026-07-01T18:23:51Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Guy\_Blumental](https://avatars.discourse-cdn.com/v4/letter/g/90ced4/32.png) [@Guy\_Blumental](https://forum.cursor.com/u/Guy_Blumental)\ **Post date:** [July 1, 2026, 6:23pm UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/1 "2026-07-01T18:23:52Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug When setting a http proxy via VS Code settings, cursor bypasses the proxy and goes straight to the internet. Before re opening the app, we even got an “internal Error - An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.” Steps to Reproduce 1. Enter VS Code settings. 2. Enter your proxy address under “Http: Proxy”. 3. Try send any prompt in an agent chat. ### Expected Behavior We expect traffic to go through our proxy and not bypassing it. ### Screenshots / Screen Recordings ![image (9).png](https://us1.discourse-cdn.com/cursor1/original/3X/2/6/2654b69918dbab12d7ebc3cb0c0aa9ca771af34d.jpeg) ### Operating System MacOS ### Version Information Version: 3.9.16 VS Code Extension API: 1.105.1 Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80 Date: 2026-06-27T06:41:01.941Z Layout: editor Build Type: Stable Release Track: Default Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.256 OS: Darwin arm64 25.4.0 ### For AI issues: which model did you use? Auto ### For AI issues: add Request ID with privacy disabled Request ID: 61e4f76c-5edc-4dbf-b0d7-7f3b2e3bc3e6 [internal] Failed to establish a socket connection to proxies: PROXY \ RetriableError: [internal] Failed to establish a socket connection to proxies: PROXY \ at uAS (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12056:27795) at EMc (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12056:26530) at Fny (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12057:11929) at Object.classify (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12057:16434) at hAS (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12057:5824) at async Oqm.runWithSharedTurnRunner (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12057:15786) at async iH.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:24486:3041) at async Lkh.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:24505:13862) at async Lkh.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:24505:22888) at async IRe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12142:2399) ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 2, 2026, 5:19am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/6 "2026-07-02T05:19:50Z")
Hey, thanks for the detailed report with the Request ID and stack trace. This is part of a known cluster of proxy issues in 3.9.16. We’re tracking the issue, but there’s no exact ETA for a fix yet. In your case, the error `Failed to establish a socket connection to proxies: PROXY ` means Cursor resolved the address from `Http: Proxy`, but couldn’t open a connection to the proxy itself. A few things to check or try: 1. Make sure the proxy host and port are correct and reachable from this machine, and that the proxy allows `CONNECT` to `*.cursor.sh` / `*.cursor.com` on port 443. 2. If you actually have direct internet access, try setting `Http: Proxy Support` = `off`. This bypasses proxy-agent and avoids this specific `PacProxyAgent` error. 3. If the proxy is required and it doesn’t support HTTP/2, enable `Settings → Network → HTTP Compatibility Mode → HTTP/1.1` (or `cursor.general.disableHttp2: true`), then fully quit and restart Cursor, not just reload window. The HTTP/1.1 path properly goes through the proxy. Let me know if that helped, and what type of proxy you’re using corporate, PAC, or local. That’ll help narrow it down. ---
**Author:** ![Vladimir\_Romanov](https://avatars.discourse-cdn.com/v4/letter/v/dfb087/32.png) [@Vladimir\_Romanov](https://forum.cursor.com/u/Vladimir_Romanov)\ **Post date:** [July 8, 2026, 9:39am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/7 "2026-07-08T09:39:31Z")
Same here. After recent upgrade to 3.10, Cursor ignores all proxy settings. Env variables, system settings, Cursor’s own settings - all of them. Had to downgrade all the way to 3.7 before anything started working again. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 8, 2026, 11:12am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/8 "2026-07-08T11:12:57Z")
Hey @Vladimir_Romanov, it’s important to separate your case from the original report. That one was on 3.9.16, and you’re on 3.10, where some proxy fixes should already be included. If 3.10 still ignores the settings, that’s a separate signal, and we need details to figure out if this is a regression or a config issue. Can you share: 1. The exact 3.10.x version `Help > About` where it reproduced, and your OS. 2. Your proxy type, corporate, PAC, or local, and how it’s set up, env `HTTP_PROXY`/`HTTPS_PROXY`, system settings, or `Http: Proxy` in Cursor settings. 3. A Request ID with Privacy Mode turned off, chat, top-right menu \> Copy Request ID. 4. Whether you tried `Settings → Network → HTTP Compatibility Mode → HTTP/1.1` or `cursor.general.disableHttp2: true` with a full Cursor restart, not just Reload Window, and whether that helps on 3.10. With that info I can tell if it’s the same baseline issue or something new in 3.10. ---
**Author:** ![Vladimir\_Romanov](https://avatars.discourse-cdn.com/v4/letter/v/dfb087/32.png) [@Vladimir\_Romanov](https://forum.cursor.com/u/Vladimir_Romanov)\ **Post date:** [July 8, 2026, 5:16pm UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/9 "2026-07-08T17:16:12Z")
This might take some time, I’ll have to switch back from working setup to 3.10 to collect the diags data. Be back in couple of hours. ---
**Author:** ![Vladimir\_Romanov](https://avatars.discourse-cdn.com/v4/letter/v/dfb087/32.png) [@Vladimir\_Romanov](https://forum.cursor.com/u/Vladimir_Romanov)\ **Post date:** [July 9, 2026, 6:59am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/10 "2026-07-09T06:59:34Z")
Hello there. I’m back with diags. 1. Cursor: ```plaintext Version: 3.10.20 VS Code Extension API: 1.125.0 Commit: 23b9fb205fe595ea2be29da7214e19762d037fc0 Date: 2026-07-07T07:03:33.071Z (1 day ago) Layout: IDE Build Type: Stable Release Track: Default Electron: 40.10.3 Chromium: 144.0.7559.236 Node.js: 24.15.0 V8: 14.4.258.32-electron.0 xterm.js: 6.1.0-beta.256 OS: Darwin arm64 25.5.0 ``` 1. It’ s a personal local proxy I use for traffic splitting when i connect to customer’s networks. Exposed at `localhost:28080` with envoy underneath. I start Cursor with env variables set: `http_proxy="``http://127.0.0.1:28080``"` `https_proxy="``http://127.0.0.1:28080``"` `HTTPS_PROXY="``http://127.0.0.1:28080``"` `HTTP_PROXY="``http://127.0.0.1:28080``"` 2. RequestIds: `178754a9-fc05-46fd-84fe-769d4d20cfb,`efcdb642-5730-4289-8d5b-e1672b4b24fe 3. Cursor’s `settings.json` for this run: ``` “http.proxy”: “[http://127.0.0.1:28080](http://127.0.0.1:28080)”, Really hope that helps. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 9, 2026, 8:09am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/11 "2026-07-09T08:09:39Z")
Thanks for the detailed troubleshooting, @Vladimir_Romanov, this is exactly what we needed. The fact that the proxy is ignored on 3.10.20 even with `cursor.general.disableHttp2: true` and HTTP/1.1 Compatibility Mode, and that it happens across all channels at once env vars, system settings, and `http.proxy` in settings.json, is a really useful signal. It shows that the HTTP/1.1 path that should have avoided the issue is not working for you on 3.10.x. This is part of a known cluster of proxy issues, the issue is being tracked, but I can’t share an exact ETA for a fix yet. For now, your best workaround is to stay on 3.7 since proxy routing works correctly there. If you want to stop updates from being pulled automatically, stick to the Release Track and turn off auto-update so it doesn’t jump back to 3.10. One quick clarification so we can log this more precisely: - On 3.7, which exact version are you on `Help > About` that works without issues? Once there’s an update on the fix, I’ll post it here. ---
**Author:** ![Vladimir\_Romanov](https://avatars.discourse-cdn.com/v4/letter/v/dfb087/32.png) [@Vladimir\_Romanov](https://forum.cursor.com/u/Vladimir_Romanov)\ **Post date:** [July 9, 2026, 8:33am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/12 "2026-07-09T08:33:00Z")
Thank you. As for 3.7 version currently i use the latest that was available for download. Details: `Version: 3.7.42` `VS Code Extension API: 1.105.1` `Commit: 5702c9cfca656d8710fad58402fe37f14345e3a0` `Date: 2026-06-15T19:39:42.738Z` `Layout: editor` `Build Type: Stable` `Release Track: Default` `Electron: 39.8.1` `Chromium: 142.0.7444.265` `Node.js: 22.22.1` `V8: 14.2.231.22-electron.0` `xterm.js: 6.1.0-beta.256` `OS: Darwin arm64 25.5.0` Also an interesting detail, that too might be of use - 3.10 and 3.7 cannot co-exist. When i install 3.10 version, overwriting whatever was before and then install a 3.7 side-by-side (e.g. `/Applications/Cursor-3.7.app/`` ), the 3.7 starts to show the very same symptoms. And just a wild guess - if done vice-versa this might actually lead to a working 3.10 instance. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 9, 2026, 9:16am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/13 "2026-07-09T09:16:33Z")
Thanks, I’ve noted 3.7.42. The detail about them coexisting is really helpful. Most likely both versions use the same user-data directory `~/Library/Application Support/Cursor` and `~/.cursor`, so the state and config that 3.10 writes leaks into 3.7. Then 3.7 starts behaving like 3.10 even though the binary is different. Just installing them side by side doesn’t isolate them. To actually separate them, try launching 3.7 with its own data directory: ```bash /Applications/Cursor-3.7.app/Contents/MacOS/Cursor \ --user-data-dir ~/cursor-3.7-data \ --extensions-dir ~/cursor-3.7-ext ``` This way 3.7 won’t share config with 3.10, and it also tests the theory. If 3.7 is stable under the isolated directory even after installing 3.10, then the issue is the shared state. Let me know how it goes. To prevent 3.10 from pulling in automatically and overwriting your working setup, turn off auto-update on 3.7 and stay on Release Track Default. I also logged your diagnostic data for 3.10.20. The proxy is ignored in all channels even with `disableHttp2: true` and HTTP/1.1 Compatibility Mode. This is part of a known cluster of proxy issues. It’s being tracked, but I can’t share an exact fix date yet. Once there’s an update, I’ll reply in the thread. ---
**Author:** ![Vladimir\_Romanov](https://avatars.discourse-cdn.com/v4/letter/v/dfb087/32.png) [@Vladimir\_Romanov](https://forum.cursor.com/u/Vladimir_Romanov)\ **Post date:** [July 13, 2026, 8:59am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/15 "2026-07-13T08:59:51Z")
Hello Dean, Looks like v3.11.13 fixes the problem, Cursor now respects both internal settings and env variables - checked several times just to be sure. System proxy settings are still ignored, but that’s fine by me. Hope that’ll hold. Current version info: `Version: 3.11.13` `VS Code Extension API: 1.125.0` `Commit: 3f21b08f0b436a07be29fbfe00b304fa15553350` `Date: 2026-07-10T01:45:28.254Z` `Layout: Agent Window` `Build Type: Stable` `Release Track: Default` `Electron: 40.10.3` `Chromium: 144.0.7559.236` `Node.js: 24.15.0` `V8: 14.4.258.32-electron.0` `xterm.js: 6.1.0-beta.256` `OS: Darwin arm64 25.5.0` ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 13, 2026, 11:43am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/16 "2026-07-13T11:43:40Z")
Hey, great news. Thanks for coming back and double-checking on 3.11.13. That matches what we expected from the proxy changes in this branch, `http.proxy` in settings.json and env vars should be respected correctly again. About system proxy settings, the fact they’re still being ignored is separate behavior, I’ll track it separately. Since your setup works via env vars and internal settings, you’re not blocked, but good call flagging it. If anything starts acting weird with proxy again after the next updates, reply here with the version from `Help > About` and the Request ID with Privacy Mode off, and I’ll take a look. ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [July 15, 2026, 12:21pm UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/18 "2026-07-15T12:21:55Z")
Hey @Guy_Blumental, since your report we changed how Cursor works with proxy connections. Can you check on the latest version 3.11.19+? Quick check: 1. In Settings, set your proxy address under `Http: Proxy`. 2. Fully quit and restart Cursor, not just Reload Window. 3. Send any prompt in agent chat. Let me know if you can still reproduce the error `Failed to establish a socket connection to proxies: PROXY `. If yes, please share your proxy host and port and its type corporate, PAC, or local, and whether it requires HTTP/1.1. That should help us dig deeper. ---
**Author:** ![Guy\_Blumental](https://avatars.discourse-cdn.com/v4/letter/g/90ced4/32.png) [@Guy\_Blumental](https://forum.cursor.com/u/Guy_Blumental)\ **Post date:** [July 16, 2026, 6:05am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/19 "2026-07-16T06:05:48Z")
Hi @deanrie, I can confirm that the issue has been resolved after updating to the latest version of cursor. Thanks for your hard work and for the quick response! ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [July 18, 2026, 6:06am UTC](https://forum.cursor.com/t/cursor-started-ignoring-http-1-1-proxy-settings/164581/21 "2026-07-18T06:06:55Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.