Cursor IDE
Every version after 2.0.11 fails to connect. I have tried both HTTP 2 and 1.1.
Start up Cursor, go to the Network settings page and run network diagnostics.
Linux
Version: 2.0.75
Yes - Cursor is unusable
deanrie
November 13, 2025, 5:49pm
2
Hey., thanks for the report. The screenshot shows ETIMEDOUT errors across all services, which usually points to network-level blocking. Since version 2.0.11 worked fine, let’s troubleshoot:
Please try:
Test direct connectivity from terminal:curl -v https://api2.cursor.sh
Switch DNS to Google/Cloudflare:
This fixed the same issue for another Linux user
Add 8.8.8.8 or 1.1.1.1 to your DNS settings
Restart Cursor after changing
Check firewall:sudo ufw statussudo ufw disable
Are you using a VPN or on a restricted network (university/office)?
Additional info needed:
Results from the curl test above
Any firewall or VPN active?
Can you share network diagnostics from the working 2.0.11 version for comparison?
If this doesn’t help, I’ll escalate as a version-specific regression. Let me know what you find.
@deanrie could you please escalate? also getting the exact same issue with the same version. was working fine ~5 minutes ago and just now getting this connection issue
~ curl -v https://api2.cursor.sh
Host api2.cursor.sh:443 was resolved.
IPv6: (none)
IPv4: 107.23.36.197, 18.211.167.29, 35.171.120.255, 54.82.132.247, 44.194.108.110, 98.86.16.109, 54.85.35.23, 52.202.147.75
Trying 107.23.36.197:443…
ALPN: curl offers h2,http/1.1
TLSv1.3 (OUT), TLS handshake, Client hello (1):
SSL Trust Anchors:
CAfile: /etc/ssl/certs/ca-certificates.crt
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.3 (IN), TLS change cipher, Change cipher spec (1):
TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
TLSv1.3 (IN), TLS handshake, Certificate (11):
TLSv1.3 (IN), TLS handshake, CERT verify (15):
TLSv1.3 (IN), TLS handshake, Finished (20):
TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
TLSv1.3 (OUT), TLS handshake, Finished (20):
SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256 / x25519 / RSASSA-PSS
ALPN: server accepted h2
Server certificate:
subject: CN=api2.cursor.sh
start date: Nov 12 00:00:00 2025 GMT
expire date: Dec 11 23:59:59 2026 GMT
issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
Certificate level 0: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
Certificate level 2: Public key type RSA (2048/112 Bits/secBits), signed using sha256WithRSAEncryption
subjectAltName: “api2.cursor.sh” matches cert’s “api2.cursor.sh”
SSL certificate verified via OpenSSL.
Established connection to api2.cursor.sh (107.23.36.197 port 443) from 10.32.197.235 port 42402
using HTTP/2
[HTTP/2] [1] OPENED stream for https://api2.cursor.sh/
[HTTP/2] [1] [:method: GET]
[HTTP/2] [1] [:scheme: https]
[HTTP/2] [1] [:authority: api2.cursor.sh]
[HTTP/2] [1] [:path: /]
[HTTP/2] [1] [user-agent: curl/8.17.0]
[HTTP/2] [1] [accept: /]
GET / HTTP/2Host: api2.cursor.shUser-Agent: curl/8.17.0Accept: /
Request completely sent off
TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):< HTTP/2 200< date: Thu, 13 Nov 2025 18:03:23 GMT< content-type: text/plain< content-length: 136< vary: Origin< access-control-allow-credentials: true< access-control-expose-headers: Grpc-Status, Grpc-Message, Grpc-Status-Details-Bin, Content-Encoding, Connect-Content-Encoding, traceparent, backend-traceparent, x-amzn-trace-id, x-request-id<
Connection #0 to host api2.cursor.sh:443 left intactWelcome to Cursor. From 20251113-155553-main-bf6e8936cdfbb39773f7502c891d3eb3f5ea0fcb (mb5lzc5z7sikipotl0is2e) in 0.00558000011369586ms..
No change.
~ sudo ufw status
Status: inactive
No VPN or restricted network.
Version 2.0.11 network diagnostic logs
