Indexing Error, I have this problem since the beginning

Discussion
1

Technical Details

  • Cursor is trying to connect to https://repo42.cursor.sh
  • Getting HTTP 404 errors
  • When connection succeeds, server reports codebase as empty
  • This explains why indexing shows as 100% immediately

Environment

  • OS: macOS Darwin 24.4.0
  • Cursor Version: 0.45.14
  • Architecture: ARM64

Steps to Reproduce

  1. Open a repository in Cursor
  2. Click the index button
  3. Indexing progress immediately shows 100%
  4. Repository features that require indexing don’t work

What I’ve Tried

  • Cleared Cursor cache and configuration:
    rm -rf ~/.cursor/*
rm -rf ~/Library/Application\ Support/Cursor/Cache/*
rm -rf ~/Library/Application\ Support/Cursor/CachedData/*
  • Restarted Cursor
  • Reinstalled Cursor

The issue persists after all these attempts.

Questions

  1. Is the indexing server (repo42.cursor.sh) working correctly?
  2. Are there known issues with the indexing service?
  3. Are there any additional troubleshooting steps I should try?
2

Hey, are you using a VPN or any other software that controls your internet connection? If you’re getting a server error, it means there’s something wrong with your network, as everything is fine on my end.

3

No. its muy Home internet connection… Maybe mi MacOs is doing something wrong?

4

Can you try connecting to a different network, for example, from your phone?

cc @danperks

5

same problem, at office… at home…

6

I am with this since the beginning… its true i am usiong Sequoia beta 15.4 but i cannot rool back the Os

7

Pls, do not leave this thread again… problem is cursor not me…

  1. Verified the connection to repo42.cursor.sh using curl --http1.1 :
curl --http1.1 -v https://repo42.cursor.sh

The response shows a 404 Not Found error:

< HTTP/1.1 404 Not Found
< Server: awselb/2.0
< Date: Sat, 22 Feb 2025 17:36:20 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 31
< Connection: keep-alive

Questions:

  1. Is the indexing server (repo42.cursor.sh ) currently down?
  2. Has the indexing service endpoint changed? If so, what is the correct one?
  3. Are there any additional troubleshooting steps I should try?
8

No, the server is available for me, it seems the problem is on your side. I mentioned Dan in this thread, he’ll check it.

9

Thanks

10

Hi, some news?

11

Anything update? same bug with ENOTFOUND error, may be a DNS problem? 2025-02-25 18:40:45.488 [info] Handshake start
2025-02-25 18:40:45.490 [error] Error Checking Connection: [unavailable] getaddrinfo ENOTFOUND repo42.cursor.sh
2025-02-25 18:40:45.490 [info] Creating Indexing Repo client: https://repo42.cursor.sh
2025-02-25 18:40:45.490 [info] Creating repo client with backend url: https://repo42.cursor.sh
2025-02-25 18:41:49.495 [warning] Retrying handshake with timeout 128000. Error: [unavailable] getaddrinfo ENOTFOUND repo42.cursor.sh
2025-02-25 18:41:49.495 [error] Handshake failed:

12

Hey, what version are you running here?

13

Hey, do note that a curl on MacOS may show two responses, for me the top one worked, and the one below returned 404!

14

Sequoia beta 15.4

Here the problem persists,

15

Another year… waiting… Windsurd is a nice option…