Connection Error after upgrade to Cursor 2.3.34

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After upgrading Cursor to the latest version this morning, cursor chats agent/debug/plan/ask started to return connection error

Steps to Reproduce

  1. upgrade to 2.3.34
  2. ask message in chat with either plan/agent/debug/ask mode turned on

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

compose-1

For AI issues: add Request ID with privacy disabled

Request ID: 73526eae-f8f1-4bd1-ac9c-9130f37c4c68

Additional Information

This is what i see in Cursor → Settings → Network → Run Diagnostics

API:
[2026-01-12T09:45:50.087Z] Start
[2026-01-12T09:45:50.163Z] Error: ConnectError: [internal] 1219773148544:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

Ping:
[2026-01-12T09:45:50.093Z] Sending ping 1
[2026-01-12T09:45:50.170Z] Error: ConnectError: [internal] 1219773148544:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

Chat:
[2026-01-12T09:45:50.100Z] Starting stream
[2026-01-12T09:45:50.174Z] Error: ConnectError: [internal] 1219773148544:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

Agent:
[2026-01-12T09:45:50.108Z] Starting stream
[2026-01-12T09:45:50.108Z] Pushing first message
[2026-01-12T09:45:50.179Z] Error: ConnectError: [internal] 1219773148544:error:10000410:SSL routines:OPENSSL_internal:SSLV3_ALERT_HANDSHAKE_FAILURE:../../third_party/boringssl/src/ssl/tls_record.cc:486:SSL alert number 40

Does this stop you from using Cursor

Yes - Cursor is unusable

6 posts were merged into an existing topic: [Known Issue] HTTP/2 Connection Failures for Users in Ukraine (SSLV3_ALERT_HANDSHAKE_FAILURE)