Indexing error, handshake fails every single time on my codebase

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, please check this box.
on

Describe the Bug

Cursor is not indexing my codebase at all, all i am seeing are failed handhsakes.
024-12-10 22:01:40.856 [warning] Retrying handshake with timeout 64000. Error: [canceled] This operation was aborted
2024-12-10 22:01:40.856 [info] Handshake start
2024-12-10 22:01:55.858 [info] Creating Indexing Repo client: https://repo42.cursor.sh
2024-12-10 22:02:00.859 [info] Creating Indexing Repo client: https://repo42.cursor.sh
2024-12-10 22:02:59.855 [warning] Retrying handshake with timeout 128000. Error: [canceled] This operation was aborted
2024-12-10 22:02:59.856 [error] Handshake failed:
2024-12-10 22:02:59.856 [error] Error: timeout in handshake with retry
at t.RepoClientMultiplexer.handshakeWithRetry (/root/.cursor-server/bin/a846435528b4b760494a836f96f0739889253530/extensions/cursor-retrieval/dist/main.js:2:813516)
at async v.getServerStatus (/root/.cursor-server/bin/a846435528b4b760494a836f96f0739889253530/extensions/cursor-retrieval/dist/main.js:2:830054)
at async v.startIndexingRepository (/root/.cursor-server/bin/a846435528b4b760494a836f96f0739889253530/extensions/cursor-retrieval/dist/main.js:2:832745)

Steps to Reproduce

indexing a laravel codebase (maybe), it is working with another codebase, this is very annoying, i have wasted so much time on this!

Expected Behavior

Indexing a codebase

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 0.43.6
VSCode Version: 1.93.1
Commit: a846435528b4b760494a836f96f0739889253530
Date: 2024-12-06T05:11:55.168Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

Additional Information

I am on using WSL2, Cursor is so bad without it that i would consider it quite unusable

Does this stop you from using Cursor

No - Cursor works, but with this issue

I just downgraded and it started indexing directly

Update: I just reinstalled the latest version and now alhamdulillah it is working for now, as it retained the previous index.

Now my docs indexing are all failing as well (sigh)

and now the main issue is back wow

Hey, is the issue still persisting?

yes