Remotte-SSH : can't install the Cursor server

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi !

Since last week, my developers have been unable to connect to two servers via SSH.

It was working perfectly, but suddenly it stopped working.

I installed the latest version of Cursor and Remote-SSH on my machine to test and I’m experiencing the same problem.
It seems the error lies here:

info] SSH connection established after 3616ms (first stdout received)
[info] (ssh_tunnel) stdout: Using TMP_DIR: /run/user/1001

[error] Error installing server: [o [RemoteSSHError]: Failed to configure the Cursor server on the remote SSH host. Please check the logs for more details.
at t.installCodeServer (c:\Users\Utilisateur.cursor\extensions\anysphere.remote-ssh-1.0.53\dist\main.js:4:197302)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async c:\Users\Utilisateur.cursor\extensions\anysphere.remote-ssh-1.0.53\dist\main.js:4:477294] {
disconnectReason: ‘unknown’
}
[info] Deleting local script C:\Users\UTILIS~1\AppData\Local\Temp\cursor_remote_install_146d40da-78d5-48b9-9b8e-ca85ba373dd4.sh
[error] Error resolving SSH authority [o [RemoteSSHError]: Failed to configure the Cursor server on the remote SSH host. Please check the logs for more details.
at t.installCodeServer (c:\Users\Utilisateur.cursor\extensions\anysphere.remote-ssh-1.0.53\dist\main.js:4:197302)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async c:\Users\Utilisateur.cursor\extensions\anysphere.remote-ssh-1.0.53\dist\main.js:4:477294] {
disconnectReason: ‘unknown’
}

I tried doing the same thing in VS Code and it works.

Can you help us ?
Thanks !

Steps to Reproduce

Create a new host ssh or use an existent.
Connect remote ssh.

Operating System

Windows 10/11

Version Information

Version: 3.5.33 (user setup)
VSCode Version: 1.105.1
Commit: aac81804b986d739acab348ed96b8bea6e83cc50
Date: 2026-05-22T06:47:48.039Z
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
OS: Windows_NT x64 10.0.19045

Additional Information

My remote server is a dedicated server running Debian 12.
SSH in CLI works.
I also check .bashrc, to delete old cursor folder on the serve.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this is part of an already tracked regression in anysphere.remote-ssh: Bug Report: Remote SSH extension v1.0.51 breaks Connect to Host. Version 1.0.53 just shipped and was supposed to fix it: Bug Report: Remote SSH extension v1.0.51 breaks Connect to Host - #18 by Colin, but based on your log you’re already on 1.0.53 and it’s still failing during the server install phase.

Can you reply in that thread under Colin’s post and say that 1.0.53 doesn’t help? That’ll help the team see the fix doesn’t cover this case.

For now, as a workaround, roll back to v1.0.50 and disable auto-update:

  • Extensions panel Ctrl+Shift+X, find anysphere.remote-ssh.
  • Click the gear next to the extension, then Install Another Version..., then pick 1.0.50.
  • In the same menu, uncheck Auto Update so it won’t update back.
  • Run Ctrl+Shift+P then Developer: Reload Window.

After that, Remote-SSH Connect to Host should work. If it doesn’t, send the full log from the Remote-SSH output panel.

Yes, sorry, I forgot to mention that, but I did see the other thread. Even after installing version 1.0.50, I have the same problem.

That’s why I created another topic. Would you still like me to reply to the other one?

here is the ful output log (i just hide the server name)

log.txt (3,5 Ko)

No, stay in this thread. Your error is different from that regression. Your SSH tunnel comes up fine, the install script starts on the remote and then crashes there. This is a server-side issue, not the 1.0.51 client bug, so downgrading didn’t help.

Most often it’s one of these two:

  1. /run/user/1001 is mounted as tmpfs with noexec (common on some Debian setups), and the installer can’t run the unpacked binaries from TMP_DIR.
  2. After you deleted the old .cursor folder on the server, some leftovers stayed behind, or $HOME (or the partition for ~/.cursor-server) is also mounted with noexec.

Can you send the following from the remote host, using the same user you connect with:

mount | grep -E "/run/user/1001|$HOME"
ls -la /run/user/1001
ls -la ~/.cursor-server ~/.cursor 2>/dev/null
cat ~/.cursor-server/.cursor-server.log 2>/dev/null | tail -80
df -h /run/user/1001 $HOME

And if it exists, the contents of ~/.cursor-server/.cursor-server.log (or any *.log in ~/.cursor-server). It should show exactly what part of the install is failing.

Workaround A: if /run/user/1001 has noexec. Add this on the remote in ~/.bashrc (or ~/.profile):

export XDG_RUNTIME_DIR="$HOME/.cache/cursor-runtime"
mkdir -p "$XDG_RUNTIME_DIR"
chmod 700 "$XDG_RUNTIME_DIR"

Workaround B: if the partition with ~/.cursor-server has noexec. Move the directory to a partition with exec and make a symlink:

mkdir -p /path/to/exec-partition/.cursor-server
mv ~/.cursor-server /path/to/exec-partition/.cursor-server 2>/dev/null || true
ln -s /path/to/exec-partition/.cursor-server ~/.cursor-server

After either workaround, in Cursor run Ctrl+Shift+P then Remote-SSH: Kill VS Code Server on Host..., then connect again. If noexec is the cause, it should work.