I am unable to connect to WSL (Ubuntu) from Cursor while using a proxy.
The key issue is that this failure occurs even though I have correctly configured proxy settings within WSL itself, and they are working properly.
I can access the WSL terminal directly, and internet connectivity (e.g., using curl, apt) is fully functional through the configured proxy.
The error log shows the Cursor server installation script fails with a “Connection timed out” when trying to download components. This strongly suggests that the installation process initiated by Cursor is not honoring the existing and working proxy environment variables (HTTP_PROXY, HTTPS_PROXY) set inside WSL.
Steps to Reproduce
Configure the Windows host to use a proxy. (I’m turn off proxy, but still not working)
Open the Cursor application.
Attempt to connect to a WSL environment (e.g., select “Connect to WSL” from the Remote Explorer).
Observe the connection process failing and check the Output panel for the error log.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.1.6 (user setup)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:20:02.577Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22000
Additional Information
I’m using a proxy.
I can’t access WSL (but VSCode connects to WSL successfully).
When I access WSL from the terminal, the internet works normally.
Environment:
Version: 1.1.6 (user setup)
VSCode Version: 1.96.2
Commit: 5b19bac7a947f54e4caa3eb7e4c5fbf832389850
Date: 2025-06-25T02:20:02.577Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22000
Error log:
2025-06-27 14:44:58.591 [info] Reloading window
2025-06-27 14:45:01.068 [info] Resolving wsl remote authority 'wsl+Ubuntu' (attempt #1)
2025-06-27 14:45:01.068 [info] Checking output for installServerScript
2025-06-27 14:45:01.068 [info] [wsl exec: installServerScript] Running command
2025-06-27 14:45:01.286 [info] [wsl exec: installServerScript][stderr]: your 131072x1 screen size is bogus. expect trouble
2025-06-27 14:45:21.400 [info] [wsl exec: installServerScript][stderr]: failed: Connection timed out.
2025-06-27 14:45:42.399 [info] [wsl exec: installServerScript][stderr]: failed: Connection timed out.
2025-06-27 14:46:04.399 [info] [wsl exec: installServerScript][stderr]: failed: Connection timed out.
2025-06-27 14:46:04.421 [error] Error installing Cursor server [wsl exec: installServerScript] Command failed with exit code 1: stdout: Killing all running Cursor servers
No running servers found
Killing running servers:
Removing all existing Cursor installations
removed directory '/home/****/.cursor-server/bin/5b19bac7a947f54e4caa3eb7e4c5fbf832389850'
removed directory '/home/****/.cursor-server/bin'
Downloading server from https://cursor.blob.core.windows.net/remote-releases/5b19bac7a947f54e4caa3eb7e4c5fbf832389850/vscode-reh-linux-x64.tar.gz
Error downloading server from https://cursor.blob.core.windows.net/remote-releases/5b19bac7a947f54e4caa3eb7e4c5fbf832389850/vscode-reh-linux-x64.tar.gz
b5c7f728b0c0e6e6db2ea572: start
exitCode==1==
listeningOn====
connectionToken====
arch==x86_64==
platform==Linux==
remoteNodePath==/home/****/.cursor-server/bin/5b19bac7a947f54e4caa3eb7e4c5fbf832389850/node==
b5c7f728b0c0e6e6db2ea572: end
Hi @user129, could you share the full logs? The latest version of the extension will attempt to download the server on the Windows side if it fails to directly download it within WSL (e.g. due to proxies). From the logs you shared, I don’t see any indication that it then attempted to retry the install.
After each cursor update, I encounter the same error as above, and each time, I have to change the ID ‘5b19bac7a947f54e4caa3eb7e4c5fbf832389850’ to the Commit ID (It appears when the error occurs, so everyone should update the commit ID according to their own version).
I tried to do exactly what you pointed out, I’ve been having this issue for days after a random update, but apparently the version of the .vsix you pointed out is not supported anymore with current cursor version.
What have you’ve been doing to solve this? It’s driving me crazy how I can’t just use cursor with WSL anymore