Codebase indexing error when ssh remote project

Bug Report
,
1

My local project can complete codebase indexing, but when I connect to the remote server project through cursor by SSH, the codebase indexing keeps prompting “handshake failed.” Could it be because my remote server is only accessible within the internal network?

1 Like
2

I encounter the same issue. Other features like Cursor Tab work properly. I wonder whether it is possible to use the local internet connection to index the codebase (through the remote-ssh tunnel) ?

3

I tried to setup cursor so it uses the local version of the retrieval plugin to index the files as shown below. However it does not seem that cursor is able to handle remote filesystems (see the redacted log file at the end).

"remote.extensionKind": {
    "anysphere.cursor-retrieval":[
        "ui"
    ],
},

2024-09-06 14:10:03.698 [debug] Disposing repo index watch.
2024-09-06 14:10:03.699 [info] Setting indexing intent to should-index
2024-09-06 14:10:03.699 [debug] Constructing repo index watch.
2024-09-06 14:10:03.699 [debug] Doing repo index watch update.
2024-09-06 14:10:03.699 [info] Creating merkle client.
2024-09-06 14:10:03.699 [info] Done creating merkle client.
2024-09-06 14:10:03.700 [info] Doing a startup handshake.
2024-09-06 14:10:03.700 [debug] Repository info: {"useLegacyRepoName":false,"value":{"repoName":"776d4de9-0aaa-4f0c-a88a-274e91a4b814","legacyRepoName":"f75c9126f723e0b022d2ffa493de8581d66a30e51914138693ae208bf675f56b-mycodedirectory","repoOwner":"google-oauth2|****","relativeWorkspacePath":".","workspaceUri":{"$mid":1,"fsPath":"\\home\\user\\mycodedirectory","_sep":1,"external":"vscode-remote://ssh-remote%2Bhost/home/user/mycodedirectory","path":"/home/user/mycodedirectory","scheme":"vscode-remote","authority":"ssh-remote+host"},"orthogonalTransformSeed":7630718874281513,"pathEncryptionKey":"****"}}
2024-09-06 14:10:03.700 [debug] Initializing merkle tree.
2024-09-06 14:10:03.701 [error] Error: Root directory does not exist!
2024-09-06 14:10:03.701 [info] Indexing job successfully done or aborted.
4

From the log it seems that it didn’t work. Did you solve this problem later?

5

Nope, it did not work.

6

logs like：

2024-09-20 05:52:30.603 [info] ExtensionService#_doActivateExtension vscode.configuration-editing, startup: false, activationEvent: ‘onLanguage:jsonc’

2024-09-20 05:52:30.604 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: ‘onLanguage:jsonc’

2024-09-20 05:52:30.604 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: ‘onLanguage:jsonc’

2024-09-20 05:52:32.883 [error] Error: connect ECONNREFUSED 13.70.79.200:443

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)

2024-09-20 05:52:35.525 [error] Error: connect ECONNREFUSED 52.168.112.67:443

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)

2024-09-20 05:52:52.370 [error] Error: connect ECONNREFUSED 52.182.143.214:443

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)

2024-09-20 05:52:55.300 [error] Error: connect ECONNREFUSED 52.168.112.67:443

at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)