as the output shown here, the ssh connection becomes very fragile and opening folder gets much slower than before. However I can successfuly connect via terminal so I guess it’s something wrong with my cursor.
output.txt (34.3 KB)
Hi @Ruby-719, from the logs I see:
(ssh_tunnel) stderr: debug1: expecting SSH2_MSG_KEX_ECDH_REPLY\cb1
\cb2 [Trace - 13:03:28.92] (ssh_tunnel) stderr: Connection reset by 140.210.209.209 port 54981\cb1
\
This indicates some sort of network issue. Have you adjusted any settings on the ssh client or server from their defaults?
thanks for the reply, but I don’t even know how to check if the ssh client/server’s setting was adjusted
When searching for that error code, it seems like it might be related to the MTU Size: https://unix.stackexchange.com/questions/722954/ssh-stuck-at-expecting-ssh2-msg-kex-ecdh-reply. It could also be an issue with the key exchange.
When you connect, could you try using this command (cmd/ctrl-shift-p, then “Remote-SSH: Connect to Host…”) and paste in the same ssh command that you used in the terminal, just to confirm the settings are the same for both?
I used the same command as you suggested and have some new error:
output2.txt (39.0 KB)
Hi @Ruby-719, it looks like it hit a timeout with the download. Could you try increasing it (maybe set it 300 or 600 seconds) and try it again? The default is 180 (3 minutes).
I used solutions like wiping .cursor-server and increasing the timeout. I just change another gpu server to see if this is something wrong with that. However I still cannot connet with cursor, even though I can successfully connect with either terminal or vscode. The error just said: (ssh_tunnel) stderr: ln: failed to create hard link ‘/tmp/cursor-remote-lock.02f8004e40c905d5d56514de1f758ee5407c992587af6d2e6f984a24ef7da549’: File exists
output3.txt (48.8 KB)
- I found the solution to “failed to create hard link ‘tmp/cursor-remote-lock.■■■’”: just ssh in (with terminal or vscode) to ‘tmp/’ and delete all the file started with ‘cursor-remote-lock’
- Then the lock issue can be resolved. Now I get the classic error: hanging with ‘wget’ to download the cursor-server. This could be resolved by increasing timeout to 600
- I still cannot connect to my original gpu server but I don’t wanna cope with that now. I think that might just be some issue with that platform
thanks @ravirahman for the help!
Hi @Ruby-719, wanted to share that we made some fixes to the Remote SSH extension
- Old lockfiles are auto-removed, so if a previous connection failed and left behind a lockfile, it won’t cause the next connection to fail.
- The timeoout will auto-reset when progress is being made on the download.
Could you try upgrading to version 1.0.6 of the Anysphere Remote SSH extension and share if you’re still running into issues? Thanks!
Hi @ravirahman, Hope you are well.
As a new cursor user, would like to report exactly the same issues as above on version 1.0.9. see below a snippet of output:
2025-06-10 15:42:45.843 [info] (ssh_tunnel) stderr: main: line 174: /run/user/10222/cursor-remote-lock.xxxxxxxxxxx: cannot overwrite existing file
I do not get the wget error, and am able to ssh into another machine.
Below are the specs:
from: MacOS 14.2.1
to:SUSE Linux Enterprise Server 15 SP4 (failed), 3.10.0-1160.119.1.el7.x86_64(succeeded)
Note: was able to ssh into both servers on vscode. Please let me know whether you need more debug logs.
Thanks
Hi @cxu28, could you try manually removing the lockfile, or on that machine try the option “reinstall server”? That should forcibly remove the file
Hi @cxu28, do you have the noclobber (set -o noclobber) set in your .bash_profile / .bashrc? It looks like we’re inheriting this option which is causing these errors. We’ll release an update to fix this, but in the meantime, could you try removing that option?
Hi @ravirahman ,
That is the culprit! I removed the set -o noclobber from my .bashrc on the remote machine and now am able to connect to the remote. Thank you very much for your help and I’ll now go enjor cursor.
For future reference, when people are experiencing issues such as
“cannot overwrite existing files” from the output of the remote-ssh extension, please follow the advice above.
I have deleted the previous post as the debug log contains information that I would not want to keep forever on the internet.
Thanks again for the help!
1 Like