SPB Git

Repository Public

proxies.md 8.7 KB 193 lines markdown

1<!-- source: https://docs.x.ai/grok-bot/proxies (from https://docs.x.ai/llms-full.txt, retrieved 2026-09-19T05:28:55Z) -->2#### Manage and protect34# Configure TLS-inspecting proxies56The Grok Bot desktop app connects from each member's device to two places:7Cursor's API at `*.cursor.sh` for chat, sign-in, and approvals, and the8member's hosted computer at a nested `*.*.cursorvm.com` hostname for computer9setup, screen, and shell. Secure web gateways that inspect TLS often let the10first through and break the second. The desktop app then hangs or errors during11computer setup; in some setups chat keeps working while the computer never12connects. Zscaler is the most common example, and this page uses it for13specifics; the same steps apply to any gateway that re-signs TLS or buffers14responses. This page is for the IT team that runs your gateway. The shared15domain list and streaming tests live on16[Enterprise network configuration](https://cursor.com/docs/enterprise/network-configuration);17this page covers what Grok Bot adds.1819This page is about the path from a member's device to Cursor. It does not20change where the hosted computer itself may connect; that is the21[network policy](/grok-bot/security#network-policy). Reaching services on your22private network from the computer is covered in23[Connect to private networks](/grok-bot/private-networks).2425## Symptoms2627* **Computer setup hangs or fails.** The app never finishes connecting to the28  computer. Chat may keep working, since it can reach `api2.cursor.sh`, or29  stall along with it; either way, the computer link needs `cursorvm.com`.30* **It works on a hotspot or a personal device** and fails on the corporate31  network or with the gateway client running.32* **It works in the office and fails at home.** The exceptions were applied to33  the office location only. See34  [apply to every profile](#apply-to-every-profile-including-off-network).35* **Sign-in or chat stall too.** TLS inspection or response buffering is still36  active on `cursor.sh`.3738## Allow these domain patterns3940Allow all of these on the gateway and in any DNS filtering. Prefer the41wildcards over enumerating hostnames; computer hostnames are generated per42computer.4344| Pattern | Used for |45| --- | --- |46| `*.cursor.sh` | Chat, sign-in, approvals, and the rest of the Cursor API |47| `*.cursor-cdn.com` | Static assets |48| `*.cursorapi.com` | Extension marketplace and related APIs |49| `*.cursorvm.com` | The hosted computer and its control plane |50| `*.*.cursorvm.com` | The same, one level deeper. Required. |51| `cursor.com`, `downloads.cursor.com` | Installing and updating the desktop app |5253Add both `cursorvm.com` patterns. Computer hostnames have two labels below54`cursorvm.com`, in the form `<computer>.<cluster>.cursorvm.com`, and a55single-level wildcard matches only one. A gateway configured with56`*.cursorvm.com` alone looks correct and still leaves the computer unreachable.57This is the usual cause of computer setup failing on a network where58`cursor.sh` is already allowed.5960## Exempt the same domains from TLS inspection and buffering6162Allowing the traffic is not enough. On every domain above:6364* **Bypass TLS (SSL) inspection.** When the gateway re-signs the connection65  with its own certificate, the computer setup handshake fails even though the66  hostname is allowed. Cursor's connections are already encrypted end to end.67* **Turn off response buffering.** Chat and the computer link stream. A gateway68  that holds responses until they complete leaves the app waiting on output69  that never arrives.7071If your policy requires inspecting all traffic, the gateway must meet the72requirements under73[SSL inspection and DLP](https://cursor.com/docs/enterprise/network-configuration#ssl-inspection-and-dlp):74HTTP/2 or Cursor's HTTP/1.1 fallback, Server-Sent Events passthrough without75buffering, and long-lived connections without forced timeouts.7677## Apply to every profile, including off-network7879Zscaler Client Connector keeps running when a device leaves the office, and it80applies an off-network profile of its own. Exceptions added to the office81location or to a single policy do not follow the device home. Apply the allow82rules, the TLS inspection exemption, and any DNS exception to every location,83profile, and policy group that Grok Bot members fall under, including roaming84and off-network. Other gateways with separate on- and off-network policies need85the same treatment.8687The tell: Grok Bot works from the office and fails from home on the same88laptop, with the gateway client still running.8990## Verify from a member's device9192Run these on a member's device with the gateway client running, after IT has93applied the changes.9495### Check who issues the certificate9697```bash98curl -v https://api2.cursor.sh |& grep -C1 issuer:99```100101The issuer should be **Amazon RSA**. If it names Zscaler or your gateway102vendor, TLS inspection is still active on `cursor.sh` for this device's103profile.104105### Check that computer hostnames resolve106107```bash108nslookup test.us9.cursorvm.com109```110111You should get addresses back. If the lookup fails, try112`nslookup test.us9.cursorvm.com 1.1.1.1`. If the public resolver answers and113your default one does not, the block is the device's DNS or gateway profile,114and the nested `*.*.cursorvm.com` exception is missing there.115116### Test streaming117118Run the HTTP/1.1 and HTTP/2 streaming tests under119[Testing proxy connectivity](https://cursor.com/docs/enterprise/network-configuration#testing-proxy-connectivity).120Output should arrive line by line, not all at once.121122### Retry in the app123124Open the Grok Bot desktop app on the same device and connect to the computer.125If it still fails, repeat the checks from that device; a passing hotspot and a126failing corporate network confirms the network is the cause.127128## Scope129130Three controls are easy to confuse:131132| You want to | Use |133| --- | --- |134| Let member devices reach Cursor and their hosted computer through your gateway | This page |135| Limit which destinations the hosted computer may reach | [Network policy](/grok-bot/security#network-policy), Enterprise only |136| Route hosted computer traffic through a member device | [Route traffic through your desktop](/grok-bot/settings-and-notifications#route-traffic-through-your-desktop) |137| Install a networking client on every hosted computer | [Team Setup](/grok-bot/private-networks#install-a-networking-client-with-team-setup), Enterprise only |138139By default, the hosted computer's own traffic leaves from Cursor's140[shared static egress IPs](/grok-bot/security#static-egress-ips) and does not141pass through the gateway on member devices. When a member enables **Route142egress through this desktop**, routed traffic uses that device's network and is143subject to its gateway policy.144145## FAQ146147### We allowlisted \*.cursorvm.com. Why does computer setup still fail?148149Two usual reasons. The nested `*.*.cursorvm.com` pattern is missing, so the150computer's hostname does not match. Or the domain is allowed but still151TLS-inspected, so the gateway's certificate breaks the setup handshake. Add the152nested pattern, exempt both patterns from inspection, then run the153[checks](#verify-from-a-members-device).154155### We allowed cursor.sh. Why does that not cover the computer?156157They use different hostnames. Chat, sign-in, and approvals go to158`api2.cursor.sh`, which most gateways already allow. The computer link goes to159a nested `cursorvm.com` hostname that needs its own allow rule and inspection160exemption. That is also why chat can keep working on some networks while the161computer never connects.162163### It works in the office but not from home. What is different?164165The gateway client is still running at home, with an off-network profile that166did not get the exceptions. Apply them to the roaming and off-network profiles167too.168169### Our policy requires TLS inspection on all traffic.170171Then the gateway has to pass streaming through untouched. The requirements are172under173[SSL inspection and DLP](https://cursor.com/docs/enterprise/network-configuration#ssl-inspection-and-dlp).174Exempting Cursor's domains is the reliable path; Cursor's connections are175encrypted end to end already.176177### Does this list also cover the Cursor editor?178179Yes. It is the same list as180[Enterprise network configuration](https://cursor.com/docs/enterprise/network-configuration#ip-allowlisting).181The editor's chat and Tab features work without the `cursorvm.com` patterns,182which is why a gateway that is fine for the editor can still break Grok Bot.183184## Related pages185186* [Enterprise network configuration](https://cursor.com/docs/enterprise/network-configuration)187* [Grok Bot for teams and enterprises](/grok-bot/teams-and-enterprises)188* [Grok Bot security](/grok-bot/security)189* [Connect to private networks](/grok-bot/private-networks)190* [Network, proxy, and remote connections](https://cursor.com/help/troubleshooting/network)191192Contact your Cursor account team for help with your gateway configuration.193
Files main
Menu

Theme