Remote-SSH "No route to host" on Raspberry Pi 4 - Works in VS Code but fails in Cursor

Support Help
,
1

Description: I am unable to connect to my Raspberry Pi 4 via Remote-SSH in Cursor, even though it works perfectly in VS Code using the same configuration.

Error Logs:

  • (ssh_tunnel) stderr: ssh: connect to host <local ip> port 22: No route to host.

  • Error installing server: Failed to connect to the remote SSH host.

  • Occasionally seeing channel open failed in terminal attempts, but standard ssh <host> terminal connection works.

Environment & Troubleshooting already performed:

  • Host: Raspberry Pi 4.

  • SSH Config: Using a fixed IP in ~/.ssh/config.

  • Server-side: Enabled AllowTcpForwarding yes in sshd_config.

  • Cleanup: Already tried deleting ~/.cursor-server on the Pi and using “Kill VS Code Server on Host” command.

  • Cursor Settings: Set “Local Server Download” to always.

  • Comparison: VS Code connects instantly without any “No route” errors.

image
image1223Ă—279 89 KB

4

Hey, thanks for the report.

The “No route to host” error in Cursor, when everything works in VS Code, is a known macOS issue with Local Network permissions. macOS manages network access per app, so Cursor needs its own permission, separate from VS Code.

Try this:

  • Open System Settings > Privacy & Security > Local Network
  • Make sure Cursor is enabled there (sometimes it shows up under a different name)
  • If it’s already enabled, toggle it off, restart Cursor, then toggle it back on. macOS should prompt for permission again
  • Or run ping <your Pi’s IP> in Cursor’s built-in terminal. That often triggers the permission prompt

Same issue and fix here: Ssh: No route to host

One more thing. Can you run uname -a on your Raspberry Pi? Cursor supports 64-bit ARM (aarch64) but not 32-bit (armv7l). I want to rule that out as a secondary cause.

Let me know how it goes.

1 Like