Could you please tell me what could be the problem? The code base is not indexed

AndrewG · August 29, 2024, 1:46pm

2024-08-29 16:40:54.841 [info] Repo client: syncing embeddings with backend:  https://repo42.cursor.sh
2024-08-29 16:40:54.841 [info] Creating merkle client.
2024-08-29 16:40:54.841 [info] Done creating merkle client.
2024-08-29 16:40:54.841 [info] Doing a startup handshake.
2024-08-29 16:40:54.841 [info] Finished initializing merkle tree in 1535.9279999881983 ms.
2024-08-29 16:40:54.841 [info] Doing the initial handshake with hash: 18470b057b0a3395bec1c518e8b31f893c472bb598d7a2e8f1ff6c31c72b0726
2024-08-29 16:40:54.841 [info] Handshake start
2024-08-29 16:40:57.542 [info] Handshake start
2024-08-29 16:41:02.511 [info] Handshake start
2024-08-29 16:41:04.069 [error] ConnectError: [internal] Protocol error
    at Function.from (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1716331)
    at R (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1690313)
    at Promise.reject (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1701895)
    at ClientHttp2Stream.<anonymous> (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1700259)
    at ClientHttp2Stream.emit (node:events:514:28)
    at ClientHttp2Stream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)

Tried using vpn proxy nothing works

AndrewG · August 30, 2024, 4:18pm

please help me

litecode · August 30, 2024, 4:30pm

Hi @AndrewG ,

Can you please add system info from Cursor > Help > About.

It may assist with further troubleshooting.

Also, in regard to reproducable steps, is clicking re-index codebase from Cursor settings causing those error logs?

AndrewG · September 2, 2024, 7:09am

Yes, any action related to code base indexing causes a protocol error

truell20 · September 2, 2024, 8:10am

Do you still see this? Made a change on our end.

AndrewG · September 2, 2024, 8:41am

I first checked for updates and cleared the cache, then reinstalled cursor ide. Started indexing

2024-09-02 11:39:23.126 [info] Repo client: syncing embeddings with backend:  https://repo42.cursor.sh
2024-09-02 11:39:23.126 [info] Creating merkle client.
2024-09-02 11:39:23.126 [info] Done creating merkle client.
2024-09-02 11:39:23.126 [info] Doing a startup handshake.
2024-09-02 11:39:23.126 [info] Finished initializing merkle tree in 1270.8634000122547 ms.
2024-09-02 11:39:23.126 [info] Doing the initial handshake with hash: eb896787bd5ebe796c8efe8a31d80c6e9a726bb9a0f4dd460300c12b68c8a33f
2024-09-02 11:39:23.126 [info] Handshake start
2024-09-02 11:39:26.135 [info] Handshake start
2024-09-02 11:39:30.813 [info] Handshake start
2024-09-02 11:39:32.134 [error] ConnectError: [internal] Protocol error
    at Function.from (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1716331)
    at R (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1690313)
    at Promise.reject (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1701895)
    at ClientHttp2Stream.<anonymous> (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1700259)
    at ClientHttp2Stream.emit (node:events:514:28)
    at ClientHttp2Stream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-09-02 11:39:33.387 [error] ConnectError: [internal] Protocol error
    at Function.from (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1716331)
    at R (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1690313)
    at Promise.reject (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1701895)
    at ClientHttp2Stream.<anonymous> (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1700259)
    at ClientHttp2Stream.emit (node:events:514:28)
    at ClientHttp2Stream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-09-02 11:39:34.933 [error] ConnectError: [internal] Protocol error
    at Function.from (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1716331)
    at R (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1690313)
    at Promise.reject (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1701895)
    at ClientHttp2Stream.<anonymous> (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1700259)
    at ClientHttp2Stream.emit (node:events:514:28)
    at ClientHttp2Stream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-09-02 11:39:35.891 [error] ConnectError: [internal] Protocol error
    at Function.from (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1716331)
    at R (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1690313)
    at Promise.reject (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1701895)
    at ClientHttp2Stream.<anonymous> (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1700259)
    at ClientHttp2Stream.emit (node:events:514:28)
    at ClientHttp2Stream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-09-02 11:39:37.093 [error] ConnectError: [internal] Protocol error
    at Function.from (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1716331)
    at R (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1690313)
    at Promise.reject (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1701895)
    at ClientHttp2Stream.<anonymous> (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1700259)
    at ClientHttp2Stream.emit (node:events:514:28)
    at ClientHttp2Stream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-09-02 11:39:39.462 [info] Handshake start
2024-09-02 11:39:39.606 [error] ConnectError: [internal] Protocol error
    at Function.from (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1716331)
    at R (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1690313)
    at Promise.reject (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1701895)
    at ClientHttp2Stream.<anonymous> (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1700259)
    at ClientHttp2Stream.emit (node:events:514:28)
    at ClientHttp2Stream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-09-02 11:39:42.307 [error] ConnectError: [internal] Protocol error
    at Function.from (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1716331)
    at R (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1690313)
    at Promise.reject (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1701895)
    at ClientHttp2Stream.<anonymous> (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:1700259)
    at ClientHttp2Stream.emit (node:events:514:28)
    at ClientHttp2Stream.emit (node:domain:488:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)

AndrewG · September 2, 2024, 9:11am

What could be the cause of this problem?

AndrewG · September 2, 2024, 11:47am

I installed the update, past bugs don’t seem to be crashing. There is another problem. Really like your ide, want to try how it works to its fullest potential. So far, due to bugs, I can’t experience its potential.

2024-09-02 14:44:54.352 [info] Search by message took 39.80220001935959ms for query ""
2024-09-02 14:44:58.905 [info] Search by sha took 19.02640002965927ms for query ""
2024-09-02 14:44:58.912 [info] Search by sha took 19.673699975013733ms for query ""
2024-09-02 14:44:58.931 [info] Search by message took 47.51730000972748ms for query ""
2024-09-02 14:44:58.933 [info] Search by message took 43.55519998073578ms for query ""
2024-09-02 14:45:26.117 [info] Search by sha took 18.5353000164032ms for query ""
2024-09-02 14:45:26.123 [info] Search by sha took 18.861800014972687ms for query ""
2024-09-02 14:45:26.141 [info] Search by message took 45.072899997234344ms for query ""
2024-09-02 14:45:26.146 [info] Search by message took 45.255499958992004ms for query ""
2024-09-02 14:45:29.077 [error] Handshake failed:
2024-09-02 14:45:29.078 [error] Error: timeout in handshake with retry
    at t.RepoClientMultiplexer.handshakeWithRetry (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:817710)
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processTimers (node:internal/timers:511:9)
    at w.getServerStatus (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:832927)
    at w.startIndexingRepository (c:\Users\user\AppData\Local\Programs\cursor\resources\app\extensions\cursor-retrieval\dist\main.js:2:835227)
2024-09-02 14:45:29.078 [error] Handshake failed.

AndrewG · September 3, 2024, 6:57am

What could be my problem?

AndrewG · September 3, 2024, 11:03am

I found the problem, I had to disable hhtp2 in the cursor settings. Thank you can close the appeal.

jeetgangele · October 8, 2024, 7:46am

same issue for e… dont why handshake fail? is this feature codebase indexing only for pro users?

robo_coder · October 8, 2024, 9:21am

Also not working for me today. I tried the http2 trick but didn’t help.

SeekBytes-AI · October 8, 2024, 9:38am

Same issue here, Yesterday I subscribed for Pro and now today I am having the issue. I dont understand. Please some can suggest what they have done already if todays of Index failed problem solved for them. I have reinstalled the cursor but did not helped.

Sam-Forum · October 8, 2024, 5:06pm

how can i do that ?
where in the settings that option is available ?

DaveCS · October 8, 2024, 5:13pm

Settings → General - ->Editor → Open Editor Settings
Search for Http2

I’ve tried all of the proposed fixes from many forums, nothing is working. We probably need to wait for a patch/update.

pinion · October 8, 2024, 7:25pm

its a repeating issue, probably in their backend, and i’d expect better resolution for a paid service.

AAL · October 8, 2024, 7:32pm

im going to ask for a refund for all the fast requests i wasted spending 48 hours trying to make an app work with a broken app

xz-12346 · October 8, 2024, 9:06pm

Everyone has the same issue on handshake error indexing. Disappointed so big issues were not caught before launch, and no response so far.

AAL · October 9, 2024, 1:45am

$60,000,000 funding raise and they can’t respond! Maybe we should complain to their investors.

deanrie · October 9, 2024, 3:56am

Topic		Replies	Views
Handshake, indexing the codebase Bug Report	1	348	August 1, 2024
Handshake error Indexing Discussion	0	159	August 31, 2024
Indexing no longer working Bug Report	8	447	October 25, 2023
Codebase indexing not working since yesterday + weird thing about indexing Bug Report	32	679	October 9, 2024
Codebase Indexing - Handshake failed Discussion	23	562	October 9, 2024

Could you please tell me what could be the problem? The code base is not indexed

Related topics