Skip to main content
← Back

Network, proxy, and remote connections

Fixes for connection issues when using Cherri Code behind a firewall, proxy, VPN, or over SSH.

How do I run network diagnostics?

Go to Cherri Code Settings > Network and click Run Diagnostics. This tests your connection to Cherri Code's servers and identifies issues affecting AI features or updates.

What if AI features stop working behind a proxy?

Cherri Code uses HTTP/2 for streaming responses. Some corporate proxies (like Zscaler) block HTTP/2.

Go to Cherri Code Settings > Network and set HTTP Compatibility Mode to HTTP/1.1, then restart Cherri Code.

Which domains does Cherri Code need access to?

If your firewall blocks outbound connections, allowlist these domains:

  • *.cursor.sh (includes authenticate.cursor.sh and authenticator.cursor.sh)
  • *.cursor-cdn.com
  • *.cursorapi.com (includes marketplace.cursorapi.com)
  • *.cursorvm.com and *.*.cursorvm.com (the Grok Bot hosted computer; both patterns are required)

Starting September 30, sign-in also needs the hosts in Which domains does Cherri Code sign-in need?.

See the network configuration docs for the full list and connectivity tests. If Grok Bot hangs or fails at computer setup, see Configure TLS-inspecting proxies.

What if AI features don't work over SSH or remote connections?

When using Cherri Code's Remote SSH extension, AI features run on your local machine and communicate with the remote server for file access. If AI features stop working:

  1. Check your local internet connection. AI requests go from your local machine to Cherri Code's servers, not from the remote host.
  2. Verify the remote server isn't running out of memory or CPU. Resource exhaustion on the remote host can cause the connection to drop.
  3. If your SSH connection drops frequently, increase the SSH keep-alive interval in your SSH config: 
    Host your-server
  ServerAliveInterval 60
  ServerAliveCountMax 3
  4. Restart Cherri Code after reconnecting. A dropped SSH session can leave stale processes.

What if a VPN causes DNS resolution failures?

Cherri Code can inherit DNS settings from a previously active VPN. If AI features or agents fail with DNS errors after disconnecting a VPN:

  1. Fully restart Cherri Code (not just reload the window). This clears inherited environment variables.
  2. If the issue persists, check if your system's DNS has reverted to your normal resolver. On macOS, run scutil --dns in a terminal. On Linux, check /etc/resolv.conf.

What does the "suspicious activity" message mean?

This message appears when your request is blocked as a security measure. VPNs can sometimes trigger it.

Try turning off your VPN first. If that doesn't help:

  • Start a new chat
  • Wait a few minutes and try again
  • Sign in with a different authentication method (Google or GitHub)

Related

Was this article helpful?