`WSL:Connect to WSL` fails (can not download) #660

sisrfeng · 2023-06-24T02:28:22Z

command

error

In wsl, this command fails:
wget 'https://update.code.visualstudio.com/commit:e3abfc3de36742f113a8f1f4648d8c7044ec2f31/server-linux-x64/stable'

OS

win11, wsl

cat /etc/issue :
Ubuntu 22.04.2 LTS \n \l

The text was updated successfully, but these errors were encountered:

truell20 · 2023-06-28T21:46:28Z

~~Thanks for reporting this! We're looking into the issue.~~

EDIT: To fix this, do the following:

Ctrl + Shift + P to open the Command Palette
Select "Fix WSL Install" and hit enter

Now, if you install the WSL extension and run Ctrl + Shift + P then the "Connect to WSL" command, you should be able to open a WSL folder in Cursor.

benherve · 2023-07-02T08:50:18Z

same problem

but,
dowload: https://github.com/VSCodium/vscodium/releases/download/1.79.2.23166/vscodium-reh-linux-x64-1.79.2.23166.tar.gz
cd /home/wf/.vscodium-server/bin
mkdir e3abfc3de36742f113a8f1f4648d8c7044ec2f31
tar xvfz vscodium-reh-linux-x64-1.79.2.23166.tar.gz .

then try

sisrfeng · 2023-07-02T10:41:45Z

same problem

but, dowload: https://github.com/VSCodium/vscodium/releases/download/1.79.2.23166/vscodium-reh-linux-x64-1.79.2.23166.tar.gz cd /home/wf/.vscodium-server/bin mkdir e3abfc3de36742f113a8f1f4648d8c7044ec2f31 tar xvfz vscodium-reh-linux-x64-1.79.2.23166.tar.gz .

then try

I use ubuntu, so should I use VSCodium-linux-x64-1.79.2.23166.tar.gz ?

what is e3abfc3de36742f113a8f1f4648d8c7044ec2f31 ?

benherve · 2023-07-02T11:01:39Z

e3abfc3de36742f113a8f1f4648d8c7044ec2f31 is the commit that your install is searching. (look you log)
try first create dir e3abfc3de36742f113a8f1f4648d8c7044ec2f31 ,
then, restart cursor, you will have a new error.
it will find a binary. (me it looking for codium-server)
codium-server is present in the release that i have downloaded.

in your release VSCodium-linux-x64-1.79.2.23166.tar.gz.
in bin folder you have only codium binary

benherve · 2023-07-07T09:23:06Z

the problem is that with every cursor update it tries to download a new version of vscodium based on the cursor commit.
currently the manual solution is to create a directory with the name of the new commit cursor and drop the vscodium install in it.

sisrfeng · 2023-07-10T01:59:07Z

To create a directory with the name of the new commit cursor and drop the vscodium install in it.

Is there any script to make this easier?

benherve · 2023-07-10T05:44:06Z

To create a directory with the name of the new commit cursor and drop the vscodium install in it.

Is there any script to make this easier?

It’s already easy manually.
juste create a dir and extract an archive. 🤷🏼‍♂️

learno · 2023-07-11T02:51:40Z

VSCodium/vscodium#1265 (comment)
Here is a solution for VSCodium, I have modified the script to also work with Cursor.
Add the following lines to ~/.vscodium-server/server-env-setup:

# uncomment the following line to enable debugging
#export VSCODE_WSL_DEBUG_INFO=true

fix_download() {
    case "$QUALITY" in
        stable)
            local repo_name='vscodium'
            local app_name='codium';;
        insider)
            local repo_name='vscodium-insiders'
            local app_name='codium-insiders';;
        *)
            echo "unknown quality: $QUALITY" 1>&2
            return 1;;
    esac
    local ps='/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe'
    local cmd="(Get-Command $app_name).Path | Split-Path | Split-Path"
    local install_dir=$(wslpath -u "$($ps -nop -c "$cmd | Write-Host -NoNewLine")")
    local product_json="$install_dir/resources/app/product.json"
    local release=$(jq -r .release "$product_json")
    local version=$(jq -r .vscodeVersion "$product_json" | sed "s#\(-$QUALITY\)\?\$#.$release&#")
    case $version in null.*)
        version=$(jq -r .version "$product_json" | sed "s#\(-$QUALITY\)\?\$#.$release&#");;
    esac
    local arch=$(uname -m)
    case $arch in
        x86_64)
            local platform='x64';;
        armv7l | armv8l)
            local platform='armhf';;
        arm64 | aarch64)
            local platform='arm64';;
        *)
            echo "unknown machine: $arch" 1>&2
            return 1;;
    esac
    local url="https://github.com/VSCodium/$repo_name/releases/download/$version/vscodium-reh-linux-$platform-$version.tar.gz"
    export VSCODE_SERVER_TAR=$(curl -fLOJ "$url" --output-dir /tmp -w '/tmp/%{filename_effective}')
    export REMOVE_SERVER_TAR_FILE=true
}
[ "$VSCODE_WSL_DEBUG_INFO" = true ] && set -x
if [ ! -d "$HOME/$DATAFOLDER/bin/$COMMIT" ]; then
    if [ ! -d "$HOME/$DATAFOLDER/bin_commit" ]; then
        set -e
        fix_download
        set +e
    fi
fi
unset fix_download

benherve · 2023-07-11T07:42:21Z

server-env-setup

if we don't have this file, we can create it and only past your code ? or we need the default file before? (and where to get it?)

Edit: try with only your code, seems good, thx man

sisrfeng · 2023-07-17T07:23:45Z

VSCodium/vscodium#1265 (comment) Here is a solution for VSCodium, I have modified the script to also work with Cursor. Add the following lines to ~/.vscodium-server/server-env-setup:

# uncomment the following line to enable debugging
#export VSCODE_WSL_DEBUG_INFO=true

fix_download() {
    case "$QUALITY" in
        stable)
            local repo_name='vscodium'
            local app_name='codium';;
        insider)
            local repo_name='vscodium-insiders'
            local app_name='codium-insiders';;
        *)
            echo "unknown quality: $QUALITY" 1>&2
            return 1;;
    esac
    local ps='/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe'
    local cmd="(Get-Command $app_name).Path | Split-Path | Split-Path"
    local install_dir=$(wslpath -u "$($ps -nop -c "$cmd | Write-Host -NoNewLine")")
    local product_json="$install_dir/resources/app/product.json"
    local release=$(jq -r .release "$product_json")
    local version=$(jq -r .vscodeVersion "$product_json" | sed "s#\(-$QUALITY\)\?\$#.$release&#")
    case $version in null.*)
        version=$(jq -r .version "$product_json" | sed "s#\(-$QUALITY\)\?\$#.$release&#");;
    esac
    local arch=$(uname -m)
    case $arch in
        x86_64)
            local platform='x64';;
        armv7l | armv8l)
            local platform='armhf';;
        arm64 | aarch64)
            local platform='arm64';;
        *)
            echo "unknown machine: $arch" 1>&2
            return 1;;
    esac
    local url="https://github.com/VSCodium/$repo_name/releases/download/$version/vscodium-reh-linux-$platform-$version.tar.gz"
    export VSCODE_SERVER_TAR=$(curl -fLOJ "$url" --output-dir /tmp -w '/tmp/%{filename_effective}')
    export REMOVE_SERVER_TAR_FILE=true
}
[ "$VSCODE_WSL_DEBUG_INFO" = true ] && set -x
if [ ! -d "$HOME/$DATAFOLDER/bin/$COMMIT" ]; then
    if [ ! -d "$HOME/$DATAFOLDER/bin_commit" ]; then
        set -e
        fix_download
        set +e
    fi
fi
unset fix_download

Thx!

The diff is :

benherve · 2023-07-19T12:38:53Z

@sisrfeng do you have a fix_download script update ?

WSL don't work with new version of cursor:

[2023-07-19 12:36:35.692] Setting up server environment: Looking for /home/ben/.vscodium-server/server-env-setup. Found, executing...
[2023-07-19 12:36:41.483] Get-Command : Le terme �codium� n'est pas reconnu comme nom d'applet de commande, fonction, fichier de script ou
[2023-07-19 12:36:41.483] programme ex�cutable. V�rifiez l'orthographe du nom, ou si un chemin d'acc�s existe, v�rifiez que le chemin d'acc�s
[2023-07-19 12:36:41.483] est correct et r�essayez.
[2023-07-19 12:36:41.483] Au caract�re Ligne:1 : 2
[2023-07-19 12:36:41.483] + (Get-Command codium).Path | Split-Path | Split-Path | Write-Host -NoN ...
[2023-07-19 12:36:41.483] + ~~~~~~~~~~~~~~~~~~
[2023-07-19 12:36:41.483] + CategoryInfo : ObjectNotFound: (codium:String) [Get-Command], CommandNotFoundException
[2023-07-19 12:36:41.483] + FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.GetCommandCommand
[2023-07-19 12:36:41.483]
[2023-07-19 12:36:41.483] Split-Path : Impossible de lier l'argument au param�tre ��Path��, car il a la valeur Null.
[2023-07-19 12:36:41.483] Au caract�re Ligne:1 : 29
[2023-07-19 12:36:41.483] + (Get-Command codium).Path | Split-Path | Split-Path | Write-Host -NoN ...
[2023-07-19 12:36:41.483] + ~~~~~~~~~~
[2023-07-19 12:36:41.483] + CategoryInfo : InvalidData : (:) [Split-Path], ParameterBindingValidationException
[2023-07-19 12:36:41.483] + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.SplitPathCo
[2023-07-19 12:36:41.483] mmand

[2023-07-19 12:36:42.481] --2023-07-19 14:36:42-- https://update.code.visualstudio.com/commit:2d7a33f66a5157c6378a1621ddb89d4130ab3659/server-linux-x64/stable
[2023-07-19 12:36:42.481] Resolving update.code.visualstudio.com (update.code.visualstudio.com)... 13.107.213.42, 13.107.246.42, 2620:1ec:46::42, ...
[2023-07-19 12:36:42.481] Connecting to update.code.visualstudio.com (update.code.visualstudio.com)|13.107.213.42|:443... connected.
[2023-07-19 12:36:42.481] HTTP request sent, awaiting response... 404 Not Found
[2023-07-19 12:36:42.481] 2023-07-19 14:36:42 ERROR 404: Not Found.

Version: 0.2.49
VSCode Version: 1.80.0
Commit: 2d7a33f66a5157c6378a1621ddb89d4130ab3659
Date: 2023-07-18T23:36:31.672Z
Electron: 22.3.10
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.22621

dylang93 · 2023-07-19T18:40:48Z

@truell20, any updates on this? Planning on trialling this IDE for my team. But we use WSL2 for our work, and it's not currently working. Even with these workarounds, any ETA?

sisrfeng · 2023-07-20T03:04:57Z

@sisrfeng do you have a fix_download script update ?

Sorry, no.

I used diff and posted that reply, and then did something else. Days later I come back to the script and find the script does not work

dylang93 · 2023-07-22T19:24:09Z

Okay, so I took the script above that someone wrote in the VSCodium issues and then tweaked it further. Ensure you are updated to the latest version of Cursor (at the time it's 0.3.1).

Create a folder in your home directory. If this folder exists, make sure to delete everything in it. It will make your WSL extensions need to be reinstalled but that is no issue to do them cause they are stored on the Windows side.

mkdir $HOME/.vscodium-server
cd $HOME/.vscodium-server

then

nano server-env-setup

and then paste this code into there and save the file.

NOTE: If you don't have the cursor command installed for CLI use (Way easier if do install it with cursor command installed). Please update the app_name to the directory of the bin file.
Example: c:\Users\{YOUR_WINDOWS_USER}\AppData\Local\Programs\cursor\resources\app.
This will fetch relevant information from Cursor to run the script.

export VSCODE_WSL_DEBUG_INFO=true

fix_download() {
    case "$QUALITY" in
        stable)
            local repo_name='vscodium'
            local app_name='cursor';;
        insider)
            local repo_name='vscodium-insiders'
            local app_name='codium-insiders';;
        *)
            echo "unknown quality: $QUALITY" 1>&2
            return 1;;
    esac
    local ps='/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe'
    local cmd="(Get-Command $app_name).Path | Split-Path | Split-Path"
    local install_dir=$(wslpath -u "$($ps -nop -c "$cmd | Write-Host -NoNewLine")")

    local product_json="$install_dir/product.json"
    local release=$(jq -r .release "$product_json")
    local version=$(jq -r .vscodeVersion "$product_json" | sed "s#\(-$QUALITY\)\?\$#.$release&#")
    case $version in null.*)
        version=$(jq -r .version "$product_json" | sed "s#\(-$QUALITY\)\?\$#.$release&#");;
    esac
    local arch=$(uname -m)
    case $arch in
        x86_64)
            local platform='x64';;
        armv7l | armv8l)
            local platform='armhf';;
        arm64 | aarch64)
            local platform='arm64';;
        *)
            echo "unknown machine: $arch" 1>&2
            return 1;;
    esac
    local url="https://github.com/VSCodium/$repo_name/releases/download/$version/vscodium-reh-linux-$platform-$version.tar.gz"
    export VSCODE_SERVER_TAR=$(curl -fLOJ "$url" --output-dir /tmp -w '/tmp/%{filename_effective}')
    export REMOVE_SERVER_TAR_FILE=true
}
[ "$VSCODE_WSL_DEBUG_INFO" = true ] && set -x
if [ ! -d "$HOME/$DATAFOLDER/bin/$COMMIT" ]; then
    if [ ! -d "$HOME/$DATAFOLDER/bin_commit" ]; then
        set -e
        fix_download
        set +e
    fi
fi
unset fix_download

Then open Cursor in Windows, and install the extensions Remote Development and WSL into Cursor. Then click the bottom right blue box and click Connect to WSL.

This will open a new Cursor window with it initializing the WSL connection. It will then set up the vscodium-server using the script we pasted.

And Tada should have WSL working. This is a hacky workaround and might have some hiccups.

walnutwaldo · 2023-07-23T20:47:54Z

^ confirmed by the devs that this should work. Make sure to double check that jq is installed in WSL and cursor is installed in Windows

walnutwaldo · 2023-08-01T02:22:31Z

LATEST FIX as of July 31, 2023

We are now hosting our own Cursor servers so you can use AI tools inside of WSL!

MAKE SURE:

You have cursor or cursor-nightly properly installed on your Windows machine (old version of Cursor wouldn't install this correctly so make sure to check the path)
You have jq installed in the WSL
You have the folder ~/.cursor-server and nothing else in that server to start with (remove anything if needed)

Inside of ~/.cursor-server of your WSL machine, create the script server-env-setup and fill it with this:

export VSCODE_WSL_DEBUG_INFO=true

fix_download() {
    case "$QUALITY" in
        stable)
            local app_name='cursor';;
        *)
            echo "unknown quality: $QUALITY" 1>&2
            return 1;;
    esac
    local ps='/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe'
    local cmd="(Get-Command $app_name).Path | Split-Path | Split-Path"
    local install_dir=$(wslpath -u "$($ps -nop -c "$cmd | Write-Host -NoNewLine")")

    local product_json="$install_dir/product.json"
    local release=$(jq -r .cursorServerRelease "$product_json")
    local vscodium_release=$(jq -r .release "$product_json")
    local version=$(jq -r .version "$product_json")
	local vscodium_version=$(jq -r .vscodeVersion "$product_json")
    case $version in null.*)
        version=$(jq -r .version "$product_json");;
    esac
    case $vscodium_version in null.*)
        vscodium_version=$(jq -r .version "$product_json");;
    esac
    local arch=$(uname -m)
    case $arch in
        x86_64)
            local platform='x64';;
        armv7l | armv8l)
            local platform='armhf';;
        arm64 | aarch64)
            local platform='arm64';;
        *)
            echo "unknown machine: $arch" 1>&2
            return 1;;
    esac
    local url="https://cursor.blob.core.windows.net/remote-releases/${version}-${release}/vscode-reh-linux-${platform}.tar.gz"
    local fallback_url="https://github.com/VSCodium/vscodium/releases/download/${vscodium_version}.${vscodium_release}/vscodium-reh-linux-${platform}-${vscodium_version}.${vscodium_release}.tar.gz"

    # Attempt to download from the initial URL
    export VSCODE_SERVER_TAR=$(curl -fLOJ "$url" --output-dir /tmp -w '%{filename_effective}')
    if [ $? -ne 0 ]; then
        # If the download fails, attempt to download from the fallback URL
        export VSCODE_SERVER_TAR=$(curl -fLOJ "$fallback_url" --output-dir /tmp -w '/tmp/%{filename_effective}')
    fi

    export REMOVE_SERVER_TAR_FILE=true
}
[ "$VSCODE_WSL_DEBUG_INFO" = true ] && set -x
if [ ! -d "$HOME/$DATAFOLDER/bin/$COMMIT" ]; then
    if [ ! -d "$HOME/$DATAFOLDER/bin_commit" ]; then
        set -e
        fix_download
        set +e
    fi
fi
unset fix_download

Cafezinho · 2023-08-01T05:01:44Z

DO NOT WORK WITH LATEST 0.6 VERSION.

Had to go back to 0.5.1

Edit: It automatically updated back to 0.6.0. SO IT IS NOT WORKING

walnutwaldo · 2023-08-01T05:45:14Z

@Cafezinho are you using the newest script I just posted above? What error do you get?

Cafezinho · 2023-08-01T13:45:09Z

@walnutwaldo When I install 0.6.0, when I put the script in the new folder it gives me:

".cursor-server/bin/74f6148eb9ea00507ec113ec51c489d6ffb4b771/bin/codium-server: not found"

When I rename code-server to codium-server it gives me type mismatch

Thanks for the help

4rt3mi5 · 2023-08-01T15:55:25Z

@Cafezinho I think I understand your issue now; I've encountered it before as well. This happens because before you created the script, the WSL extension downloaded an incompatible version on its own. After creating the script, it didn't update it due to the existence of the server component. The solution is to delete everything in the ~/.cursor-server directory except for server-env-setup. Then, reopen Cursor, and the script will take effect and download the correct components.

Cafezinho · 2023-08-01T20:32:27Z

Still did not work

4rt3mi5 · 2023-08-01T20:37:21Z

@Cafezinho Can you show me the complete terminal output? It seems like the script did not work in your environment.

Cafezinho · 2023-08-01T20:40:41Z

Here it is:

4rt3mi5 · 2023-08-01T20:49:35Z

@Cafezinho In your WSL environment, is there codium-server or code-server in the directory ~/.cursor-server/bin/74f6148eb9ea00507ec113ec51c489d6ffb4b771/bin?

Cafezinho · 2023-08-01T21:01:41Z

code-server

walnutwaldo · 2023-08-01T21:04:33Z

@Cafezinho usually you need to clear out your entire ~/.cursor-server folder except for the server-env-setup file and then retry.

truell20 · 2023-08-26T05:20:46Z

Failed to connect to the remote extension host server (Error: WebSocket close with status code 1006)

Have seen this work if you close of the window and try again? @Tusen183 Is it persistent?

truell20 · 2023-08-26T05:21:37Z

@lacion Did you run "Fix WSL" first? If yes, then can you send the output of these two commands:

(wsl -l -q).Trim() -split "`n" | ForEach-Object { $_ -replace '[^a-zA-Z0-9\._-]', '' } | Where-Object { $_ -ne '' }

wsl -e whoami

Tusen183 · 2023-08-26T07:11:15Z

@truell20 I Tried it. There wasn't any output, so I don't know if it executed it. This issue only happens with Centos 7, I have no problem with Ubuntun 20.04. I guess it's not Cursor's problem.

karthik-pepperdex · 2023-08-26T09:23:23Z

Still does not work for me too

Tusen183 · 2023-08-26T09:44:44Z

@truell20 It can work now.But I don't know which step make it work. I removed all the servers related to cursor and vscode, did what @danielvds01x mentioned, and opened tcpforward in the ssh config.

maxritter · 2023-08-28T05:52:13Z

@lacion Did you run "Fix WSL" first? If yes, then can you send the output of these two commands:
(wsl -l -q).Trim() -split "`n" | ForEach-Object { $_ -replace '[^a-zA-Z0-9\._-]', '' } | Where-Object { $_ -ne '' }
wsl -e whoami

> (wsl -l -q).Trim() -split "`n" | ForEach-Object { $_ -replace '[^a-zA-Z0-9\._-]', '' } | Where-Object { $_ -ne '' }
Ubuntu-CommPrev
docker-desktop-data
docker-desktop

> wsl -e whoami
max

I get this error inside WSL, even after running the "fix WSL" script:

> cursor
To use Cursor with the Windows Subsystem for Linux, please install Cursor in Windows and uninstall the Linux version in WSL. You can then use the `cursor` command in a WSL terminal just as you would in a normal command prompt.
Do you want to continue anyway? [y/N] y
To no longer see this prompt, start Cursor with the environment variable DONT_PROMPT_WSL_INSTALL defined.
/mnt/c/Users/mail/AppData/Local/Programs/cursor/resources/app/bin/cursor: 62: /mnt/c/Users/mail/AppData/Local/Programs/cursor/resources/app/bin/../cursor: not found

truell20 · 2023-08-28T17:38:17Z

Ah, right now we only support opening WSL from Cursor itself, instead of from the command line. You need to run Ctrl+Shift+P, "Connect to WSL."

Tusen183 · 2023-08-31T01:48:13Z

@truell20

Error:

There was a problem connecting to WSL after the updated version, the link is invalid. Can I roll back the version, and it will work normally after manually installing the server in the previous version.

Os:

wsl ubuntu20.04 LTS

Version: 0.9.1
VSCode Version: 1.80.1
Commit: 30d21e59529ff0a52d8a847c419e668f2fd2d620
Date: 2023-08-30T23:17:14.710Z
Electron: 22.3.10
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.19045

Error

[2023-08-31 01:35:58.833] --2023-08-31 09:35:58-- https://update.code.visualstudio.com/commit:30d21e59529ff0a52d8a847c419e668f2fd2d620/server-linux-x64/stable
[2023-08-31 01:35:58.833] Resolving update.code.visualstudio.com (update.code.visualstudio.com)... 13.107.246.73, 13.107.213.73, 13.107.246.1, ...
[2023-08-31 01:35:58.833] Connecting to update.code.visualstudio.com (update.code.visualstudio.com)|13.107.246.73|:443...
[2023-08-31 01:35:59.145] connected.
[2023-08-31 01:35:59.145] HTTP request sent, awaiting response...
[2023-08-31 01:35:59.158] 404 Not Found
[2023-08-31 01:35:59.158] 2023-08-31 09:35:59 ERROR 404: Not Found.
[2023-08-31 01:35:59.158]
[2023-08-31 01:35:59.158] ERROR: Failed to download https://update.code.visualstudio.com/commit:30d21e59529ff0a52d8a847c419e668f2fd2d620/server-linux-x64/stable to /home/tusen183/.cursor-server/bin/30d21e59529ff0a52d8a847c419e668f2fd2d620-1693445758.tar.gz

Cafezinho · 2023-08-31T02:44:35Z

Error in version 0.9.1. Keeps happening every 3 updates. Needs fix ASAP

Cafezinho · 2023-08-31T02:53:14Z

HELPPPPPPPPPPPPPPPPPPPP

Tusen183 · 2023-08-31T03:26:40Z

@Cafezinho I use 0.8, can work.

Cafezinho · 2023-08-31T12:09:39Z

How can I download 0.8 now?

Cafezinho · 2023-08-31T12:14:29Z

Worked on 0.9.1 if you apply fix inside cursor using Ctrl P + Fix WSL and after restart your computer.

bhaskoro-muthohar · 2023-09-02T04:19:55Z

Worked on 0.9.1 if you apply fix inside cursor using Ctrl P + Fix WSL and after restart your computer.

whoaa, I just tried it and it works

karthik-pepperdex · 2023-09-03T14:24:23Z

still no luck on my end

karthik-pepperdex · 2023-09-03T14:40:05Z

im still stuck at this error, im on the latest version of cursor, did the fix wsl part and still nothing.

karthik-pepperdex · 2023-09-03T14:42:01Z

Ah, right now we only support opening WSL from Cursor itself, instead of from the command line. You need to run Ctrl+Shift+P, "Connect to WSL."

I dont even find such a command in my command palette

truell20 · 2023-09-06T01:27:47Z

You need to install the WSL extension @Kardev07

vmasrani · 2023-09-06T19:00:04Z

How can I download 0.8 now?

Also want to know this! Previous versions were working for me but now everything is broken :(

truell20 · 2023-09-10T10:37:26Z

@vmasrani What problem are you encountering? Could you provide a screenshot?

tonydavis629 · 2023-09-20T15:07:12Z

Latest update has broken my WSL. Having the same issue as discussed here, even after running Fix WSL and restarting.

Version: 0.10.4
VSCode Version: 1.80.1
Commit: c0db898419c36107211de244bdcf5f412c1a4920
Date: 2023-09-10T05:39:06.846Z
Electron: 22.3.10
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Windows_NT x64 10.0.19044

Vitalsine85 · 2023-09-20T18:14:35Z

Latest update has broken my WSL. Having the same issue as discussed here, even after running Fix WSL and restarting.

Version: 0.10.4 VSCode Version: 1.80.1 Commit: c0db898419c36107211de244bdcf5f412c1a4920 Date: 2023-09-10T05:39:06.846Z Electron: 22.3.10 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.19044

Rolling back worked for me. See: https://forum.cursor.sh/t/cant-connect-to-remote-ssh-server-after-recent-update/632/5

johannesmichael · 2023-10-10T03:11:02Z

After running the Fix WSL I had to convert the server-env-setup file from ANSI to UTF-8, since my user name contains german special characters.
Did it with 0.10.4 and then installed 0.12.3.
Running fine

eino-makitalo · 2023-10-23T04:41:58Z

After running the Fix WSL I had to convert the server-env-setup file from ANSI to UTF-8, since my user name contains german special characters. Did it with 0.10.4 and then installed 0.12.3. Running fine

This helped me with finish version of machine... fix it to utf-8 automatically

sisrfeng · 2023-11-13T07:39:03Z

Any latest official solution for connecting to wsl ? Since the time I commented (#660 (comment)), I can connect to wsl. But recently it fails again.

IncubatorShokuhou · 2023-12-21T07:43:34Z

Same issue. Hope if will be fixed ASAP as it is a critical bug in my opinion.

batjko · 2024-01-30T15:21:16Z

EDIT: To fix this, do the following:

Ctrl + Shift + P to open the Command Palette

Select "Fix WSL Install" and hit enter

Now, if you install the WSL extension and run Ctrl + Shift + P then the "Connect to WSL" command, you should be able to open a WSL folder in Cursor.

This solved it for me as well, thanks 👍

RossMcMillan92 · 2024-08-11T19:49:54Z

Fixed for me by opening settings UI and changing "Remote.SSH.Local Server Download" from "auto" to "always".

WarningRoo · 2025-02-12T02:39:52Z

If Docker is installed, Connect to WSL may default to Docker's WSL instance.

This could cause errors, like download failures or other environment issues.

Use Connect to WSL using distro... to select the correct WSL.

danperks added the bug Something isn't working label Jul 3, 2023

benherve mentioned this issue Jul 7, 2023

404 when ssh-ing after latest update #651

Open

learno mentioned this issue Jul 12, 2023

Unknown method $provideTextSearchResults on actor ExtHostTask #678

Closed

walnutwaldo mentioned this issue Jul 28, 2023

WSL: codium-server: not found and version mismatch #703

Closed

ShisunXia mentioned this issue Sep 4, 2024

Cursor is not starting in WSL #1508

Open

WSL:Connect to WSL fails (can not download) #660

WSL:Connect to WSL fails (can not download) #660

Comments

sisrfeng commented Jun 24, 2023

command

error

OS

truell20 commented Jun 28, 2023 • edited Loading

benherve commented Jul 2, 2023 • edited Loading

sisrfeng commented Jul 2, 2023

benherve commented Jul 2, 2023 • edited Loading

benherve commented Jul 7, 2023

sisrfeng commented Jul 10, 2023

benherve commented Jul 10, 2023

learno commented Jul 11, 2023 • edited Loading

benherve commented Jul 11, 2023 • edited Loading

sisrfeng commented Jul 17, 2023

benherve commented Jul 19, 2023 • edited Loading

dylang93 commented Jul 19, 2023

sisrfeng commented Jul 20, 2023 • edited Loading

dylang93 commented Jul 22, 2023 • edited Loading

walnutwaldo commented Jul 23, 2023

walnutwaldo commented Aug 1, 2023 • edited Loading

Cafezinho commented Aug 1, 2023 • edited Loading

walnutwaldo commented Aug 1, 2023

Cafezinho commented Aug 1, 2023

4rt3mi5 commented Aug 1, 2023

Cafezinho commented Aug 1, 2023

4rt3mi5 commented Aug 1, 2023

Cafezinho commented Aug 1, 2023

4rt3mi5 commented Aug 1, 2023

Cafezinho commented Aug 1, 2023

walnutwaldo commented Aug 1, 2023

truell20 commented Aug 26, 2023

truell20 commented Aug 26, 2023

Tusen183 commented Aug 26, 2023

karthik-pepperdex commented Aug 26, 2023

Tusen183 commented Aug 26, 2023 • edited Loading

maxritter commented Aug 28, 2023 • edited Loading

truell20 commented Aug 28, 2023

Tusen183 commented Aug 31, 2023 • edited Loading

Error:

Os:

Error

Cafezinho commented Aug 31, 2023

Cafezinho commented Aug 31, 2023

Tusen183 commented Aug 31, 2023

Cafezinho commented Aug 31, 2023

Cafezinho commented Aug 31, 2023

bhaskoro-muthohar commented Sep 2, 2023

karthik-pepperdex commented Sep 3, 2023

karthik-pepperdex commented Sep 3, 2023

karthik-pepperdex commented Sep 3, 2023

truell20 commented Sep 6, 2023

vmasrani commented Sep 6, 2023

truell20 commented Sep 10, 2023

tonydavis629 commented Sep 20, 2023

Vitalsine85 commented Sep 20, 2023

johannesmichael commented Oct 10, 2023

eino-makitalo commented Oct 23, 2023

sisrfeng commented Nov 13, 2023

IncubatorShokuhou commented Dec 21, 2023

batjko commented Jan 30, 2024

RossMcMillan92 commented Aug 11, 2024

WarningRoo commented Feb 12, 2025

`WSL:Connect to WSL` fails (can not download) #660

`WSL:Connect to WSL` fails (can not download) #660

truell20 commented Jun 28, 2023 •

edited

Loading

benherve commented Jul 2, 2023 •

edited

Loading

benherve commented Jul 2, 2023 •

edited

Loading

learno commented Jul 11, 2023 •

edited

Loading

benherve commented Jul 11, 2023 •

edited

Loading

benherve commented Jul 19, 2023 •

edited

Loading

sisrfeng commented Jul 20, 2023 •

edited

Loading

dylang93 commented Jul 22, 2023 •

edited

Loading

walnutwaldo commented Aug 1, 2023 •

edited

Loading

Cafezinho commented Aug 1, 2023 •

edited

Loading

Tusen183 commented Aug 26, 2023 •

edited

Loading

maxritter commented Aug 28, 2023 •

edited

Loading

Tusen183 commented Aug 31, 2023 •

edited

Loading