2025-06-26 12:57:31.313 [error] [LocalProcess0][resolveAuthority(ssh-remote,1)][295493ms] returned an error {“code”:“NotAvailable”,“message”:“EISDIR: illegal operation on a directory, read”,“detail”:true}
2025-06-26 12:57:31.313 [error] resolveAuthority(ssh-remote) returned an error after 295493 ms EISDIR: illegal operation on a directory, read
2025-06-26 12:57:31.313 [error] Error received from starting extension host (kind: Remote)
2025-06-26 12:57:31.313 [error] CodeExpectedError: EISDIR: illegal operation on a directory, read
at MUs.ub (vscode-file://vscode-app/c:/Users/paolo.forni/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6707:53321)
at async MUs.tb (vscode-file://vscode-app/c:/Users/paolo.forni/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6707:52687)
at async MUs.gc (vscode-file://vscode-app/c:/Users/paolo.forni/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6713:3640)
at async vscode-file://vscode-app/c:/Users/paolo.forni/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47:94153
2025-06-26 12:57:31.313 [error] [remote-connection][attempt 1] An error occurred in initial connection! Will retry… Error:
Hi @paolo.forni91 , thanks – it looks like the remote server might be corrupted:
2025-06-26 12:57:31.313 [error] Error received from starting extension host (kind: Remote)
Could you try the command “Remote SSH: Reinstall Server and Reload Window” from the command palette? If that doesn’t work, could you try manually removing the ~/.cursor and ~/.cursor-server folders on your remote machine?
Hi @paolo.forni91, taking a closer looks at the logs, it seems like this might be client side. Could you double check that ~/.ssh/config is a file (or doesn’t exist)? I was able to reproduce this error by making that path a folder.
If that isn’t it, could you try removing ~/.cursor/extensions/anysphere.remote-ssh-* and then reinstall the remote SSH extension? It’s possible that the extension installation is corrupted, which could also cause this error.