Describe the Bug
Having issues with Remote SSH everything works fine on Visual Studio Code. But I’m unable to get one host to work. This host works fine on Visual Studio. Here is the error message I’m in my 14-day trial period, so hoping this can be resolved and I can sigh up for pro.
cursor logs
2025-07-08 15:38:22.830 [info] Resolving ssh remote authority ‘y108p30’ (Unparsed ‘ssh-remote+7b22686f73744e616d65223a2279313038703330227d’) (attempt #1)
2025-07-08 15:38:22.843 [info] SSH askpass server listening on /var/folders/w3/tqkx0b4n0t913cv24651fnn00000gn/T/cursor-ssh-QGZiHe/socket.sock
2025-07-08 15:38:22.844 [info] Using configured platform linux for remote host y108p30
2025-07-08 15:38:22.845 [info] Using askpass script: /Users/admin/.cursor/extensions/anysphere.remote-ssh-1.0.20/dist/scripts/launchSSHAskpass.sh with javascript file /Users/admin/.cursor/extensions/anysphere.remote-ssh-1.0.20/dist/scripts/sshAskClient.js. Askpass handle: /var/folders/w3/tqkx0b4n0t913cv24651fnn00000gn/T/cursor-ssh-QGZiHe/socket.sock
2025-07-08 15:38:22.847 [info] Launching SSH server via shell with command: cat “/var/folders/w3/tqkx0b4n0t913cv24651fnn00000gn/T/cursor_remote_install_31259.sh” | ssh -v -T -D 61722 y108p30 bash --login -c bash
2025-07-08 15:38:22.847 [info] Started installation script. Waiting for it to finish…
2025-07-08 15:38:22.847 [info] Waiting for server to install via process(822)…
2025-07-08 15:38:22.855 [info] (ssh_tunnel) stderr: OpenSSH_9.8p1, LibreSSL 3.3.6
2025-07-08 15:38:22.855 [info] (ssh_tunnel) stderr: debug1: Reading configuration data /Users/admin/.ssh/config
debug1: /Users/admin/.ssh/config line 1: Applying options for *
2025-07-08 15:38:22.855 [info] (ssh_tunnel) stderr: debug1: /Users/admin/.ssh/config line 31: Applying options for y108p30
2025-07-08 15:38:22.855 [info] (ssh_tunnel) stderr: debug1: Reading configuration data /etc/ssh/ssh_config
2025-07-08 15:38:22.856 [info] (ssh_tunnel) stderr: debug1: Reading configuration data /etc/ssh/ssh_config.d/100-macos.conf
2025-07-08 15:38:22.856 [info] (ssh_tunnel) stderr: debug1: /etc/ssh/ssh_config.d/100-macos.conf line 1: Applying options for *
2025-07-08 15:38:22.856 [info] (ssh_tunnel) stderr: debug1: Reading configuration data /etc/ssh/crypto.conf
2025-07-08 15:38:22.856 [info] (ssh_tunnel) stderr: debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to 192.168.15.102 [192.168.15.102] port 2222.
2025-07-08 15:38:22.881 [info] (ssh_tunnel) stderr: debug1: Connection established.
2025-07-08 15:38:22.882 [info] (ssh_tunnel) stderr: debug1: identity file /Users/admin/.ssh/id_rsa type 0
debug1: identity file /Users/admin/.ssh/id_rsa-cert type -1
2025-07-08 15:38:22.884 [info] (ssh_tunnel) stderr: debug1: identity file /Users/admin/.ssh/id_ecdsa type 2
2025-07-08 15:38:22.884 [info] (ssh_tunnel) stderr: debug1: identity file /Users/admin/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/admin/.ssh/id_ecdsa_sk type -1
debug1: identity file /Users/admin/.ssh/id_ecdsa_sk-cert type -1
2025-07-08 15:38:22.885 [info] (ssh_tunnel) stderr: debug1: identity file /Users/admin/.ssh/id_ed25519 type 3
debug1: identity file /Users/admin/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/admin/.ssh/id_ed25519_sk type -1
2025-07-08 15:38:22.885 [info] (ssh_tunnel) stderr: debug1: identity file /Users/admin/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /Users/admin/.ssh/id_xmss type -1
debug1: identity file /Users/admin/.ssh/id_xmss-cert type -1
debug1: identity file /Users/admin/.ssh/id_dsa type -1
debug1: identity file /Users/admin/.ssh/id_dsa-cert type -1
2025-07-08 15:38:22.885 [info] (ssh_tunnel) stderr: debug1: Local version string SSH-2.0-OpenSSH_9.8
2025-07-08 15:38:22.896 [info] (ssh_tunnel) stderr: debug1: Remote protocol version 2.0, remote software version Go
debug1: compat_banner: no match: Go
debug1: Authenticating to 192.168.15.102:2222 as ‘[email protected]@10.150.108.30’
2025-07-08 15:38:22.897 [info] (ssh_tunnel) stderr: debug1: load_hostkeys: fopen /Users/admin/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
2025-07-08 15:38:22.897 [info] (ssh_tunnel) stderr: debug1: SSH2_MSG_KEXINIT sent
2025-07-08 15:38:22.899 [info] (ssh_tunnel) stderr: debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: ecdh-sha2-nistp256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: [email protected] MAC: compression: none
2025-07-08 15:38:22.899 [info] (ssh_tunnel) stderr: debug1: kex: client->server cipher: [email protected] MAC: compression: none
2025-07-08 15:38:22.900 [info] (ssh_tunnel) stderr: debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
2025-07-08 15:38:22.925 [info] (ssh_tunnel) stderr: debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-rsa SHA256:BXebZf3vjmswh1/jnmj8x2xGXW9lsrZxNK5XVtRNG6M
2025-07-08 15:38:22.925 [info] (ssh_tunnel) stderr: debug1: load_hostkeys: fopen /Users/admin/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
2025-07-08 15:38:22.925 [info] (ssh_tunnel) stderr: debug1: Host ‘[192.168.15.102]:2222’ is known and matches the RSA host key.
debug1: Found key in /Users/admin/.ssh/known_hosts:10
2025-07-08 15:38:22.926 [info] (ssh_tunnel) stderr: debug1: rekey out after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
2025-07-08 15:38:22.926 [info] (ssh_tunnel) stderr: debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 4294967296 blocks
2025-07-08 15:38:23.017 [info] (ssh_tunnel) stderr: debug1: SSH2_MSG_SERVICE_ACCEPT received
2025-07-08 15:38:23.028 [info] (ssh_tunnel) stderr: debug1: Authentications that can continue: password,publickey
debug1: Next authentication method: publickey
2025-07-08 15:38:23.028 [info] (ssh_tunnel) stderr: debug1: get_agent_identities: bound agent to hostkey
2025-07-08 15:38:23.028 [info] (ssh_tunnel) stderr: debug1: get_agent_identities: ssh_fetch_identitylist: agent contains no identities
debug1: Will attempt key: /Users/admin/.ssh/id_rsa RSA SHA256:Lv07uQJQYX/WrUzD1jKVFOLO/tsikDYpv7XHD7MWshU
debug1: Will attempt key: /Users/admin/.ssh/id_ecdsa ECDSA SHA256:f9bsi3ofYK0tk4EtHSrY4WiFdz5TZjp5CtUkrGinQzI
debug1: Will attempt key: /Users/admin/.ssh/id_ecdsa_sk
debug1: Will attempt key: /Users/admin/.ssh/id_ed25519 ED25519 SHA256:etQi2wgSCNDS84vi2ehaCrkeOs8ZRvVGKW6mZtiRMP8
debug1: Will attempt key: /Users/admin/.ssh/id_ed25519_sk
debug1: Will attempt key: /Users/admin/.ssh/id_xmss
debug1: Will attempt key: /Users/admin/.ssh/id_dsa
debug1: Offering public key: /Users/admin/.ssh/id_rsa RSA SHA256:Lv07uQJQYX/WrUzD1jKVFOLO/tsikDYpv7XHD7MWshU
2025-07-08 15:38:23.073 [info] (ssh_tunnel) stderr: debug1: Authentications that can continue: password,publickey
debug1: Offering public key: /Users/admin/.ssh/id_ecdsa ECDSA SHA256:f9bsi3ofYK0tk4EtHSrY4WiFdz5TZjp5CtUkrGinQzI
2025-07-08 15:38:23.187 [info] (ssh_tunnel) stderr: debug1: Authentications that can continue: password,publickey
debug1: Trying private key: /Users/admin/.ssh/id_ecdsa_sk
debug1: Offering public key: /Users/admin/.ssh/id_ed25519 ED25519 SHA256:etQi2wgSCNDS84vi2ehaCrkeOs8ZRvVGKW6mZtiRMP8
2025-07-08 15:38:23.247 [info] (ssh_tunnel) stderr: debug1: Authentications that can continue: password,publickey
debug1: Trying private key: /Users/admin/.ssh/id_ed25519_sk
2025-07-08 15:38:23.247 [info] (ssh_tunnel) stderr: debug1: Trying private key: /Users/admin/.ssh/id_xmss
debug1: Trying private key: /Users/admin/.ssh/id_dsa
debug1: Next authentication method: password
debug1: read_passphrase: requested to askpass
2025-07-08 15:38:23.341 [info] Askpass server received request: POST /
2025-07-08 15:38:23.341 [info] Askpass server received request body: {“request”:"[email protected]@[email protected]’s password: "}
2025-07-08 15:38:23.341 [info] Received SSH askpass request: [email protected]@[email protected]’s password:
2025-07-08 15:38:28.527 [info] (ssh_tunnel) stderr: Authenticated to 192.168.15.102 ([192.168.15.102]:2222) using “password”.
debug1: Local connections to LOCALHOST:61722 forwarded to remote address socks:0
2025-07-08 15:38:28.527 [info] (ssh_tunnel) stderr: debug1: Local forwarding listening on ::1 port 61722.
debug1: channel 0: new port-listener [port listener] (inactive timeout: 0)
debug1: Local forwarding listening on 127.0.0.1 port 61722.
debug1: channel 1: new port-listener [port listener] (inactive timeout: 0)
debug1: channel 2: new session [client-session] (inactive timeout: 0)
2025-07-08 15:38:28.527 [info] (ssh_tunnel) stderr: debug1: Entering interactive session.
debug1: pledge: filesystem
2025-07-08 15:38:28.539 [info] (ssh_tunnel) stderr: debug1: Sending environment.
debug1: Sending command: bash --login -c bash
2025-07-08 15:38:28.991 [info] (ssh_tunnel) stdout: Using TMP_DIR: /run/user/2003
Killing all running Cursor servers
2025-07-08 15:38:29.000 [info] (ssh_tunnel) stdout: No running code servers found
Killing running code servers:
2025-07-08 15:38:29.004 [info] (ssh_tunnel) stdout: Killing all running multiplex servers
2025-07-08 15:38:29.110 [info] (ssh_tunnel) stdout: No running multiplex servers found
Killing running multiplex servers:
Removing all existing Cursor installations
removed directory ‘/home/junbo.geng/.cursor-server/bin/faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0’
removed directory ‘/home/junbo.geng/.cursor-server/bin’
Deleting left behind cursor servers, except for /home/junbo.geng/.cursor-server/cursor-server-c79444a6-1b26-49b8-8a87-ad036b418eeb.tar.gz
2025-07-08 15:38:29.111 [info] (ssh_tunnel) stdout: Done deleting left behind cursor servers
Locking /run/user/2003/cursor-remote-lock.cbbc73ec7fc8acc44ccfa068d7b0cf28
Downloading server via wget from xxxxto cursor-server-4ad3468d-1e5b-4c6b-82a4-2a52fd081c67.tar.gz
2025-07-08 15:38:48.679 [info] (ssh_tunnel) stdout: Checking node executable
2025-07-08 15:38:48.682 [info] (ssh_tunnel) stdout: v20.18.2
2025-07-08 15:38:48.684 [info] (ssh_tunnel) stdout: Checking for running multiplex server: /home/junbo.geng/.cursor-server/bin/multiplex-server/45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15.js
2025-07-08 15:38:48.784 [info] (ssh_tunnel) stdout: Running multiplex server:
Creating multiplex server token file /run/user/2003/cursor-remote-multiplex.token.cbbc73ec7fc8acc44ccfa068d7b0cf28.45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15
Creating directory for multiplex server: /home/junbo.geng/.cursor-server/bin/multiplex-server
Writing multiplex server script to /home/junbo.geng/.cursor-server/bin/multiplex-server/45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15.js
Starting multiplex server: /home/junbo.geng/.cursor-server/bin/faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0/node /home/junbo.geng/.cursor-server/bin/multiplex-server/45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15.js 6c4efa51-0ba9-491f-8a2f-a9133c616384
Multiplex server started with PID 468302 and wrote pid to file /run/user/2003/cursor-remote-multiplex.pid.cbbc73ec7fc8acc44ccfa068d7b0cf28.45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15
Reading multiplex server token file /run/user/2003/cursor-remote-multiplex.token.cbbc73ec7fc8acc44ccfa068d7b0cf28.45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15
Multiplex server token file found
Reading multiplex server log file /run/user/2003/cursor-remote-multiplex.log.cbbc73ec7fc8acc44ccfa068d7b0cf28.45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15
2025-07-08 15:38:49.264 [info] (ssh_tunnel) stdout: Checking for code servers
2025-07-08 15:38:49.273 [info] (ssh_tunnel) stdout: Code server script is not running
Creating code server token file /run/user/2003/cursor-remote-code.token.cbbc73ec7fc8acc44ccfa068d7b0cf28
2025-07-08 15:38:49.273 [info] (ssh_tunnel) stdout: Starting code server script /home/junbo.geng/.cursor-server/bin/faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0/bin/cursor-server --start-server --host=127.0.0.1 --port 0 --connection-token-file /run/user/2003/cursor-remote-code.token.cbbc73ec7fc8acc44ccfa068d7b0cf28 --telemetry-level off --enable-remote-auto-shutdown --accept-server-license-terms &> /run/user/2003/cursor-remote-code.log.cbbc73ec7fc8acc44ccfa068d7b0cf28 &
2025-07-08 15:38:49.274 [info] (ssh_tunnel) stdout: Code server started with PID 468361 and wrote pid to file /run/user/2003/cursor-remote-code.pid.cbbc73ec7fc8acc44ccfa068d7b0cf28
2025-07-08 15:38:49.276 [info] (ssh_tunnel) stdout: Code server log file is /run/user/2003/cursor-remote-code.log.cbbc73ec7fc8acc44ccfa068d7b0cf28
2025-07-08 15:48:49.229 [info] (ssh_tunnel) stderr: Connection to 192.168.15.102 closed by remote host.
2025-07-08 15:48:49.230 [info] (ssh_tunnel) stderr: debug1: channel 0: free: port listener, nchannels 3
debug1: channel 1: free: port listener, nchannels 2
debug1: channel 2: free: client-session, nchannels 1
Transferred: sent 31572, received 5268 bytes, in 620.7 seconds
Bytes per second: sent 50.9, received 8.5
debug1: Exit status -1
2025-07-08 15:48:49.233 [info] (ssh_tunnel): exit: code=255 signal=null
2025-07-08 15:48:49.236 [error] Error installing server: Failed to install the Cursor Server. Please check the logs for more details.
2025-07-08 15:48:49.236 [info] Deleting local script /var/folders/w3/tqkx0b4n0t913cv24651fnn00000gn/T/cursor_remote_install_31259.sh
2025-07-08 15:48:49.236 [error] Error resolving SSH authority Failed to install the Cursor Server. Please check the logs for more details.
cursor-server logs
junbo.geng@y108p31:~$ tail -f /run/user/1015/cursor-remote-code.log.cbbc73ec7fc8acc44ccfa068d7b0cf28
Extension host agent listening on 25711
[15:26:43]
[15:26:43] Extension host agent started.
[15:26:43] Started initializing default profile extensions in extensions installation folder. file:xxx
[15:26:43] Completed initializing default profile extensions in extensions installation folder. file:xxxx
Last EH closed, shutting down
[15:31:43] Last EH closed, shutting down
Steps to Reproduce
First, I deleted the cursor-server directory on the remote server.
Then, I used Cursor’s Remote-SSH to connect to the remote server.
After that, there was a long wait. The installation and running of cursor-server on the server were both normal.
However, after cursor-server started successfully, Cursor did not connect to cursor-server as expected. After some time, the connection timed out and failed.
With the same configuration file, VSCode works perfectly.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.2
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:08:52.104Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0