Not indexing the codebase on WSL (Ubuntu)

[Siam]

Describe the Bug

I’ve recently moved my development to the WSL (Windows Subsystem for Linux), and installed the official WSL extension for Cursor. Now, when I select the ‘Connect to WSL’ from the bottom left button (the ‘Connect to Remote Window’ button), the app restarts and runs from WSL (Ubuntu).

But when I tried to put a prompt to the Agent, I’ve noticed this line:
Note: Codebase is not indexed yet. Results are much better when indexed. Currently indexing...

The settings page also shows the same (provided in the image). After showing this on the Settings Page for some time, it shows Handshake failed option on instead of the Setting up indexing ... part.

Steps to Reproduce

I’ve tried reopening the project, restarting the IDE, and even restarting my Windows, but it still doesn’t work.

Screenshots / Screen Recordings

After some time (about 5-8 minutes), the Tools and Integrations page got a Handshake failed error looks like below:

Operating System: Windows 11

Current Cursor Version: 1.2.4 (Latest)

After the Handshake failed error comes up, here’s the log from the Output panel (Cursor Indexing and Retrieval selected):

[ravirahman]

Hi @Siam, could you share the logs for the “Cursor Indexing & Retrieval” output panel?

[Siam]

Yeah, after seeing your reply (@ravirahman), I’ve updated my issue again. You can check it with a full details (with your requested screenshot).

My chat window looks like this on my WSL ():

[ravirahman]

Hi @Siam, these logs indicate that there is a network error. Could you try running the network diagnostics in the Cursor settings, and try changing the HTTP Compatibility Mode to HTTP/1.1?

[Siam]

@ravirahman

• Yeah, below is the HTTP/2 diagnostics:
  

  

• And here is the HTTP/1.1 diagnostics (the logs of the Agent here took a long time before appearing):
  

  

Hope these informations will be useful.

[Siam]

@ravirahman , any help here?

[ravirahman]

Does your network environment require a proxy? If so, these will need to be configured inside WSL (not just windows). We’ll source the .bashrc / .bash_profile when starting the server process, so you can put the configuration in there.

After changing these files, please kill the remote server with the command “WSL: Kill Remote Server and Reload Window”, so the new config will take effect:

[Siam]

I don’t know if my network need a proxy (or any already activated). Can you please tell me how I can check it?

I guess, you didn’t give me the file codes. I will be very happy for the mentioned files (.bashrc file).