I’m really enjoying development with Cursor! Currently, I’m working on multiple projects in parallel using separate windows - one with a local directory and another connected to a remote server via SSH.
However, I’m experiencing an issue where starting the local development server causes the SSH connection to the remote server to drop. Even after the connection is restored, I often need to reconnect several times before I can resume development on the remote side.
Is there any workaround or solution for this issue? Has anyone else experienced similar problems when running local and remote development environments simultaneously?
Any help would be appreciated!
Steps to Reproduce
Open two Cursor windows
Connect one to remote server via SSH
Start local development server in the other window
SSH connection drops
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
I was previously using the VSCode Remote SSH extension, but I’ve now switched to the Anysphere one.
However, before making that switch, I realized the issue might have been caused by the following scenario:
I am developing using Nuxt, and I had my development server running on port 3000 for debugging purposes.
When Cursor establishes an SSH connection to a remote server, it creates a local port-forwarding (tunnel). If Cursor’s default port happens to conflict with Nuxt’s default port (3000), each time I start or restart the Nuxt server, that port gets reset. This action interrupts Cursor’s internal SSH tunnel and can cause the SSH connection to disconnect.
Port Conflict Flow:
Cursor establishes an SSH tunnel:
e.g., Cursor → localhost:3000 → VPS
Nuxt starts on the local environment:
Running npm run dev occupies port 3000 (conflicts if Cursor is already using this port for tunneling)
Cursor’s SSH tunnel breaks:
The port reuse interrupts the tunnel → SSH connection is disconnected.
After changing the Nuxt port to 3100, this issue no longer occurred.
Hi @reskillin – interesting thought. We always pick a remote server port at random, so it would be unlikely that port 3000 conflicts. But, it is possible that an old instance of Nuxt (or something else) is bound to port 3000.
According to the AI analysis, the error was caused by a conflict on port 3000.
Either way, after changing the Nuxt development server’s port and switching the SSH connection to Anysphere, the issue was resolved. Thank you very much for your support!
I look forward to building many more products with Cursor, and I’ll continue cheering for your development!
Port Conflict Flow: