I can connect.
Then the connection drops. I get this error:
2025-07-21 14:46:35.868 [error] Error resolving SSH authority Failed to connect to Cursor code server. Ensure that your remote host ssh config has ‘AllowTcpForwarding yes’ in ‘/etc/ssh/sshd_config’. Please check the logs and try reinstalling the server.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
2025-07-21 14:46:29.112 [error] Failed to connect to Cursor server at http://127.0.0.1:57580, attempt 1 of 3 This operation was aborted
2025-07-21 14:46:29.112 [info] [forwarding][multiplex][127.0.0.1:57581 -> 127.0.0.1:35019][7b7e2d5f-3dad-4db1-91fa-3638a8f58285] received connection request
2025-07-21 14:46:29.112 [info] [command][a9675047-d69b-4c94-a9a9-e44b5a5964f3] Sending command request: {"command":"echo","args":["1"],"env":{"SSH_AUTH_SOCK":"/tmp/cursor-remote-ssh-auth-sock-8d4a0ef8-7c03-4680-98fc-3323aa5b8d6c.sock"},"token":"5058cb78-e71e-4859-b195-1f3330493fd9","id":"a9675047-d69b-4c94-a9a9-e44b5a5964f3"}
2025-07-21 14:46:29.112 [info] (ssh_tunnel) stderr: debug1: Connection to port 57669 forwarding to socks port 0 requested.
debug1: channel 5: new dynamic-tcpip [dynamic-tcpip] (inactive timeout: 0)
2025-07-21 14:46:29.176 [info] (ssh_tunnel) stderr: debug1: channel 3: free: direct-tcpip: listening port 57669 for 127.0.0.1 port 35019, connect from 127.0.0.1 port 57673 to 127.0.0.1 port 57669, nchannels 6
2025-07-21 14:46:29.206 [info] [forwarding][multiplex][127.0.0.1:57581 -> 127.0.0.1:57669 -> 127.0.0.1:35019][7b7e2d5f-3dad-4db1-91fa-3638a8f58285] socks forwarding established
2025-07-21 14:46:29.311 [info] [command][a9675047-d69b-4c94-a9a9-e44b5a5964f3] Process exited with code 0
2025-07-21 14:46:29.311 [info] [forwarding][multiplex][127.0.0.1:57581 -> 127.0.0.1:57669 -> 127.0.0.1:35019][7b7e2d5f-3dad-4db1-91fa-3638a8f58285] socks connection closed
2025-07-21 14:46:29.311 [info] [command][a9675047-d69b-4c94-a9a9-e44b5a5964f3] Socket close event received
2025-07-21 14:46:29.419 [info] (ssh_tunnel) stderr: debug1: channel 5: free: direct-tcpip: listening port 57669 for 127.0.0.1 port 35019, connect from 127.0.0.1 port 57676 to 127.0.0.1 port 57669, nchannels 5
2025-07-21 14:46:30.116 [error] Failed to connect to Cursor server at http://127.0.0.1:57580, attempt 2 of 3 This operation was aborted
2025-07-21 14:46:31.121 [error] Failed to connect to Cursor server at http://127.0.0.1:57580, attempt 3 of 3 This operation was aborted
2025-07-21 14:46:31.121 [error] Could not re-establish SOCKS forwarding; re-establishing entire SSH connection Failed to connect to Cursor code server. Ensure that your remote host ssh config has 'AllowTcpForwarding yes' in '/etc/ssh/sshd_config'. Please check the logs and try reinstalling the server.
2025-07-21 14:46:33.863 [error] Failed to connect to Cursor server at http://127.0.0.1:57580, attempt 1 of 3 This operation was aborted
2025-07-21 14:46:33.865 [info] [forwarding][code][127.0.0.1:57580 -> 127.0.0.1:39237][6fc2b2e3-da19-41c5-b42c-47c952cd039c] received connection request
2025-07-21 14:46:33.865 [info] (ssh_tunnel) stderr: debug1: Connection to port 57669 forwarding to socks port 0 requested.
debug1: channel 3: new dynamic-tcpip [dynamic-tcpip] (inactive timeout: 0)
2025-07-21 14:46:33.962 [info] [forwarding][code][127.0.0.1:57580 -> 127.0.0.1:57669 -> 127.0.0.1:39237][6fc2b2e3-da19-41c5-b42c-47c952cd039c] socks forwarding established
2025-07-21 14:46:34.866 [error] Failed to connect to Cursor server at http://127.0.0.1:57580, attempt 2 of 3 This operation was aborted
2025-07-21 14:46:35.867 [error] Failed to connect to Cursor server at http://127.0.0.1:57580, attempt 3 of 3 This operation was aborted
2025-07-21 14:46:35.868 [error] Error resolving SSH authority Failed to connect to Cursor code server. Ensure that your remote host ssh config has 'AllowTcpForwarding yes' in '/etc/ssh/sshd_config'. Please check the logs and try reinstalling the server.
2025-07-21 14:47:29.315 [info] [remote-ssh] Pinging remote server on port 127.0.0.1:57581
2025-07-21 14:47:29.316 [info] [command][bd9c0efc-1906-46b9-af49-45ac75d58afc] Sending command request: {"command":"echo","args":["1"],"env":{"SSH_AUTH_SOCK":"/tmp/cursor-remote-ssh-auth-sock-8d4a0ef8-7c03-4680-98fc-3323aa5b8d6c.sock"},"token":"5058cb78-e71e-4859-b195-1f3330493fd9","id":"bd9c0efc-1906-46b9-af49-45ac75d58afc"}
2025-07-21 14:47:29.316 [info] [forwarding][multiplex][127.0.0.1:57581 -> 127.0.0.1:35019][3d822634-0301-4e12-85e0-28f873bfbda0] received connection request
2025-07-21 14:47:29.317 [info] (ssh_tunnel) stderr: debug1: Connection to port 57669 forwarding to socks port 0 requested.
debug1: channel 5: new dynamic-tcpip [dynamic-tcpip] (inactive timeout: 0)
2025-07-21 14:47:29.444 [info] [forwarding][multiplex][127.0.0.1:57581 -> 127.0.0.1:57669 -> 127.0.0.1:35019][3d822634-0301-4e12-85e0-28f873bfbda0] socks forwarding established
2025-07-21 14:47:29.552 [info] [command][bd9c0efc-1906-46b9-af49-45ac75d58afc] Process exited with code 0
2025-07-21 14:47:29.552 [info] [forwarding][multiplex][127.0.0.1:57581 -> 127.0.0.1:57669 -> 127.0.0.1:35019][3d822634-0301-4e12-85e0-28f873bfbda0] socks connection closed
2025-07-21 14:47:29.552 [info] [command][bd9c0efc-1906-46b9-af49-45ac75d58afc] Socket close event received
2025-07-21 14:47:29.650 [info] (ssh_tunnel) stderr: debug1: channel 5: free: direct-tcpip: listening port 57669 for 127.0.0.1 port 35019, connect from 127.0.0.1 port 57707 to 127.0.0.1 port 57669, nchannels 6
This seems to only happen with a node that is using tailscale. But using VSCode w/ the VSCode Remote SSH extension works perfectly fine with the same node / ssh config.
Hi @ErwannMillon , we just released version 1.0.23 of the Remote SSH extension which should fix this issue. Earlier versions had a connection check that could cause an otherwise-working connection to fail under slow network conditions. Could you try upgrading to the latest version of the extension and see if that fixes this issue?
The issue may have to do with using remote ssh to a datacenter that is bad at hairpinning connections. But the VSCode Remote SSH extension works fine so the problem is def specific to the Cursor implementation
After the drop happens for the first time, the server seems to get permanently broken. It fails to auto reconnect, and even a reload is no longer able to connect. I need to pkill -f cursor-server && rm -rf ~/.cursor-server to be able to reconnect to the same machine after the first time the connection drops.
I can reliably induce the error by connecting to the server, opening a file, making a change and trying to save it.
Hi @ErwannMillon, thank you for sharing these. If you open a workspace containing only a few files (or no files at all), is the connection more reliable, or does it continue to crash after opening?
Yeah. So when opening a completely empty dir, it never crashes. Now, on cursor 1.3.4, opening any dir and starting to open small python files causes a full application crash (
hi, is there any news on this or any way i can help debug? Our entire company is having this issue when working on our cluster, it is severely blocking.
Hi, exactly the same issue here. I was about to open a thread and saw this one. I’m using a remote docker devcontainer via SSH (Ubuntu 25.04 locally, Debian 12 remote, SSH extension version 1.0.23).
The impact for me is similar: I mainly work on remote machines and can’t use cursor at all there.
Update: Switching back to vscode, I’ve noticed a pylance warning for my repo that there would be too many files. Adding {"python.analysis.include": \["src/\*\*/\*"\]} to my .vscode/settings.json seems to have fixed my problem also with cursor.
Hi, is there any fix for these issues yet? I recently installed cursor on a new machine and started seeing these issues. Here’s a screen recording of what I’m seeing - my connection starts lagging and skips out for several seconds at a time. Cursor — Screen Studio. Every ~30-60 second it’ll break for ~5-10 seconds. This does not happen with vscode or plain ssh, and did not happen with old cursor.
Version 1.4.5 has failed to resolve the SSH issues. After opening multiple projects, Cursor Remote SSH remains painfully slow—folder navigation and file edits suffer from unbearable latency. Worse, every time you open a new project through the same SSH connection, you’re prompted for your password (something VS Code Remote SSH never does). The fact that each update makes this basic feature worse is absurd and catastrophic. If you can’t optimize the simplest yet most fundamental workflow, stop claiming superiority over VS Code and charging for it. In its current state, Cursor Remote SSH is a black hole that disrupts the entire workflow of anyone who relies on it.
