TechFixSignal
Cursor

Cursor Agent Connection Failed Please Try Again

When Cursor Agent shows Connection failed. Please try again, or contact support if the issue persists, set HTTP Compatibility Mode to HTTP/1.1 and fully quit.

Reviewed by TechFixSignal EditorialSee how this guide is verified

Last checked
Sep 6, 2026
Applies to
Windows, Mac, Desktop
Fix status
Community Confirmed
Fastest useful check

Quick answer

Match the Agent or Chat banner Connection failed. Please try again, or contact support if the issue persists, often with a Request ID. Open Cursor Settings → Network, run Diagnostics, set HTTP Compatibility Mode to HTTP/1.1, then fully quit and relaunch Cursor (not Reload Window). If it continues, enable Disable HTTP/2 in App Settings, or test a mobile hotspot with VPN off. This is a transport-path failure, not a usage-limit wait and not Unable to reach the model provider.

On this page

What we're seeing

  • The exact banner is Connection failed. Please try again, or contact support if the issue persists, often with a Request ID.
  • Independent June–July 2026 first-hand reports on the Cursor forum quote that sentence while using Agent or Chat.
  • Cursor staff replies in those threads describe a transport-layer drop: the request never reaches Cursor servers, or streaming is cut by a proxy, VPN, or SSL inspection path that mishandles HTTP/2.
  • A different banner such as Unable to reach the model provider, Model not available for your region, or a usage-limit message is a different fingerprint.
  • Retrying the same prompt may succeed once and fail again. That pattern still points at the network path, not a broken project.

Start here

Try these first

Fix 1

Confirm the Connection failed banner

Community Confirmed

Match the exact sentence before changing network settings. Nearby Cursor errors share the word connection but need different leftovers.

  1. Read the Agent or Chat error. This guide is for Connection failed. Please try again, or contact support if the issue persists, usually with a Request ID.
  2. If the title is Unable to reach the model provider, or the detail says the provider is temporary, stop here. That is a different fingerprint.
  3. If the only message is a usage or rate limit, stop here. Waiting out a quota is not this leftover.
  4. Note whether you are on VPN, a corporate proxy, SSL inspection, or a restricted work network.

Applies to Windows, Mac, Desktop

Fix 2

Run Diagnostics and switch to HTTP/1.1

Community Confirmed

Cursor staff on June and July 2026 Connection failed threads tell people to run Network Diagnostics and set HTTP Compatibility Mode to HTTP/1.1, then fully quit and relaunch. Forum first-hand reports treat that as the first try-today leftover for proxy and VPN paths.

  1. Open Cursor Settings → Network.
  2. Run Diagnostics and note which checks fail.
  3. Set HTTP Compatibility Mode to HTTP/1.1.
  4. Fully quit Cursor and relaunch it. Do not rely on Reload Window alone.
  5. Retry the same Agent or Chat action once.

Applies to Windows, Mac, Desktop

Fix 3

Enable Disable HTTP/2 in App Settings

Community Confirmed

When Compatibility Mode alone is not enough, staff point to a separate App Settings toggle named Disable HTTP/2. Some threads also use the settings key cursor.general.disableHttp2 set to true.

  1. Open App Settings with Ctrl+, on Windows, or Cmd+, on Mac.
  2. Search for HTTP/2 and turn on Disable HTTP/2.
  3. If the toggle is missing, add cursor.general.disableHttp2 set to true in settings.json, then save.
  4. Fully quit and relaunch Cursor, then retry Agent.

Applies to Windows, Mac, Desktop

Fix 4

Isolate VPN, proxy, and network path

Community Confirmed

Staff replies for this banner say corporate proxies, VPNs, and SSL inspection products can block bidirectional streaming even when ordinary browsing works. A phone hotspot comparison is the clean A/B test.

  1. Temporarily turn off VPN or pause SSL-inspecting antivirus for one test.
  2. Try the same Agent prompt on a phone hotspot.
  3. If the hotspot works and the office network fails, ask the network admin to allow Cursor endpoints such as *.cursor.sh, *.cursor.com, *.cursorapi.com, and *.cursor-cdn.com.
  4. Keep the Request ID from a failing attempt if you contact Cursor support.

Applies to Windows, Mac, Desktop

Device notes

Windows
Corporate Windows images with Zscaler-style SSL inspection are a common path for this banner. Prefer a full quit after HTTP/1.1, not Reload Window.
Mac
Use Cmd+, for App Settings when enabling Disable HTTP/2. A hotspot A/B still applies on macOS.
Desktop
Agent and Chat both use streaming transport. A clean Network Diagnostics result does not rule out a streaming-only proxy block. The same leftovers apply on Linux desktop builds of Cursor.

Official information

Checked on 6 September 2026, Cursor staff replies on forum threads that quote Connection failed. Please try again, or contact support if the issue persists describe a transport-layer failure and recommend Network Diagnostics, HTTP Compatibility Mode HTTP/1.1 with a full relaunch, and separately Disable HTTP/2 in App Settings. Those leftovers come from staff guidance on first-hand June–July 2026 reports, not from a dedicated Help Center article that names this exact sentence.

Sources

Keep troubleshooting

Related problems