Describe the Bug
Connection to Cursor server failed: Couldn’t install Cursor Server, install script returned non-zero exit status: Code server did not start successfully
2025-07-05 00:45:26.357 [info] (ssh_tunnel) stderr: 2025-07-05 00:45:26 (4.01 MB/s) - ‘cursor-server-4d54ef3a-091f-4701-883b-5aa120060fd5.tar.gz’ saved [68062292/68062292]
2025-07-05 00:45:31.516 [info] (ssh_tunnel) stdout: Checking node executable
2025-07-05 00:45:31.516 [info] (ssh_tunnel) stderr: bash: line 327: /grid/siepel/home/xing/.cursor-server/bin/031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0/node: Permission denied
2025-07-05 00:45:31.516 [info] (ssh_tunnel) stdout: Node executable at /grid/siepel/home/xing/.cursor-server/bin/031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0/node is not working, checking system node
2025-07-05 00:45:31.550 [info] (ssh_tunnel) stdout: System node version: v20.14.0
2025-07-05 00:45:31.580 [info] (ssh_tunnel) stdout: System node version is 20 or higher, creating symlink
2025-07-05 00:45:31.598 [info] (ssh_tunnel) stdout: Created symlink from /grid/siepel/home/xing/.cursor-server/bin/031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0/node to /grid/siepel/home/xing/apps/node/node20/bin/node
2025-07-05 00:45:31.619 [info] (ssh_tunnel) stdout: Checking for running multiplex server: /grid/siepel/home/xing/.cursor-server/bin/multiplex-server/45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15.js
2025-07-05 00:45:31.680 [info] (ssh_tunnel) stdout: Running multiplex server:
2025-07-05 00:45:31.687 [info] (ssh_tunnel) stdout: Creating multiplex server token file /run/user/11387/cursor-remote-multiplex.token.cc91d4e73f9acc9029da4736af160dd2.45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15
2025-07-05 00:45:31.729 [info] (ssh_tunnel) stdout: Creating directory for multiplex server: /grid/siepel/home/xing/.cursor-server/bin/multiplex-server
2025-07-05 00:45:31.762 [info] (ssh_tunnel) stdout: Writing multiplex server script to /grid/siepel/home/xing/.cursor-server/bin/multiplex-server/45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15.js
2025-07-05 00:45:31.783 [info] (ssh_tunnel) stdout: Starting multiplex server: /grid/siepel/home/xing/.cursor-server/bin/031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0/node /grid/siepel/home/xing/.cursor-server/bin/multiplex-server/45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15.js 3ad56de0-658e-4085-87f5-69d7fe013601
2025-07-05 00:45:31.797 [info] (ssh_tunnel) stdout: Multiplex server started with PID 1519299 and wrote pid to file /run/user/11387/cursor-remote-multiplex.pid.cc91d4e73f9acc9029da4736af160dd2.45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15
2025-07-05 00:45:31.798 [info] (ssh_tunnel) stdout: Reading multiplex server token file /run/user/11387/cursor-remote-multiplex.token.cc91d4e73f9acc9029da4736af160dd2.45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15
2025-07-05 00:45:31.798 [info] (ssh_tunnel) stdout: Multiplex server token file found
2025-07-05 00:45:31.824 [info] (ssh_tunnel) stdout: Reading multiplex server log file /run/user/11387/cursor-remote-multiplex.log.cc91d4e73f9acc9029da4736af160dd2.45e440a0fc5a5d12380c7a83a49ab82c55f715a5d60292da31f8d75730a9ee15
2025-07-05 00:45:31.841 [info] (ssh_tunnel) stdout: Checking for code servers
2025-07-05 00:45:31.892 [info] (ssh_tunnel) stdout: Code server script is not running
Creating code server token file /run/user/11387/cursor-remote-code.token.cc91d4e73f9acc9029da4736af160dd2
2025-07-05 00:45:31.948 [info] (ssh_tunnel) stdout: Starting code server script /grid/siepel/home/xing/.cursor-server/bin/031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0/bin/cursor-server --start-server --host=127.0.0.1 --port 0 --connection-token-file /run/user/11387/cursor-remote-code.token.cc91d4e73f9acc9029da4736af160dd2 --telemetry-level off --enable-remote-auto-shutdown --accept-server-license-terms &> /run/user/11387/cursor-remote-code.log.cc91d4e73f9acc9029da4736af160dd2 &
2025-07-05 00:45:31.948 [info] (ssh_tunnel) stdout: Code server started with PID 1519323 and wrote pid to file /run/user/11387/cursor-remote-code.pid.cc91d4e73f9acc9029da4736af160dd2
2025-07-05 00:45:31.958 [info] (ssh_tunnel) stdout: Code server log file is /run/user/11387/cursor-remote-code.log.cc91d4e73f9acc9029da4736af160dd2
2025-07-05 00:47:08.742 [info] (ssh_tunnel) stdout: Error code server did not start successfully
2025-07-05 00:47:08.901 [info] (ssh_tunnel) stdout: -rw-r–r-- 1 xing siepel lab staff 136 Jul 5 00:45 /run/user/11387/cursor-remote-code.log.cc91d4e73f9acc9029da4736af160dd2
2025-07-05 00:47:08.919 [info] (ssh_tunnel) stdout: bash: line 475: /grid/siepel/home/xing/.cursor-server/bin/031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0/bin/cursor-server: Permission denied
2025-07-05 00:47:08.920 [info] (ssh_tunnel) stdout: 4a785f6569801d5165ef1250: start
exitCode==1==
2025-07-05 00:47:08.921 [info] (ssh_tunnel) stdout: nodeExecutable==/grid/siepel/home/xing/.cursor-server/bin/031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0/node==
multiplexListeningOn==44905==
multiplexConnectionToken==3ad56de0-658e-4085-87f5-69d7fe013601==
codeListeningOn====
errorMessage==Code server did not start successfully==
isFatalError==false==
codeConnectionToken==5131ce7c-9f98-4888-b063-a333730df431==
detectedPlatform==linux==
2025-07-05 00:47:08.924 [info] (ssh_tunnel) stdout: arch==x64==
2025-07-05 00:47:08.947 [info] (ssh_tunnel) stdout: SSH_AUTH_SOCK====
4a785f6569801d5165ef1250: end
2025-07-05 00:47:08.951 [info] Server install command exit code: 1
2025-07-05 00:47:08.958 [error] Error installing server: Couldn’t install Cursor Server, install script returned non-zero exit status: Code server did not start successfully
2025-07-05 00:47:08.958 [info] Deleting local script C:\Users\16147\AppData\Local\Temp\cursor_remote_install_30291.sh
2025-07-05 00:47:08.963 [error] Error resolving SSH authority Couldn’t install Cursor Server, install script returned non-zero exit status: Code server did not start successfully
2025-07-05 00:47:08.964 [info] (ssh_tunnel) stdout: Unlocking /run/user/11387/cursor-remote-lock.cc91d4e73f9acc9029da4736af160dd2
2025-07-05 00:47:08.965 [info] (ssh_tunnel) stderr: main: line 187: 1519179 Terminated while [ $counter -lt 900 ]; do
date +%s > “$lockfile”; sleep 1; counter=$((counter + 1));
done
2025-07-05 00:47:08.978 [info] (ssh_tunnel) stderr: debug1: client_input_channel_req: channel 2 rtype exit-status reply 0
2025-07-05 00:47:09.306 [info] (ssh_tunnel) stderr: debug1: channel 2: free: client-session, nchannels 3
2025-07-05 00:47:09.319 [info] (ssh_tunnel) stderr: debug1: channel 0: free: port listener, nchannels 2
2025-07-05 00:47:09.324 [info] (ssh_tunnel) stderr: debug1: channel 1: free: port listener, nchannels 1
2025-07-05 00:47:09.331 [info] (ssh_tunnel) stderr: Transferred: sent 30836, received 1128520 bytes, in 124.2 seconds
2025-07-05 00:47:09.333 [info] (ssh_tunnel) stderr: Bytes per second: sent 248.2, received 9084.0
2025-07-05 00:47:09.335 [info] (ssh_tunnel) stderr: debug1: Exit status 1
2025-07-05 00:47:09.397 [info] (ssh_tunnel): exit: code=1 signal=null
Steps to Reproduce
I tried chmod +x curser-server, but it always redownloaded everything and gave the same error.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.1 (user setup)
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:16:02.610Z
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.26100
Does this stop you from using Cursor
Yes - Cursor is unusable