CodeRabbit-hosted domains
For CodeRabbit-hosted services, the environment running CodeRabbit CLI must allow outbound TCP traffic on port 443. No inbound firewall rule is required. Allow the domain names below instead of fixed IP addresses because the addresses behind these services can change.These requirements cover outbound traffic from the environment running the CLI. CodeRabbit IP addresses for connecting to private Git provider instances cover traffic in the opposite direction and do not replace this domain list.
For a standard US setup, allow
cli.coderabbit.ai, app.coderabbit.ai, and ide.coderabbit.ai. For a standard EU setup, allow cli.coderabbit.ai, app.eu.coderabbit.ai, and ide.eu.coderabbit.ai. Run cr auth status to confirm the active region.
In CLI 0.9.1 or later, reviews for organizations in the US region connect to wss://cli.coderabbit.ai/ws and switch to ide.coderabbit.ai only after four failed connection attempts. If only ide.coderabbit.ai is allowed, reviews still run but each one starts about 40 seconds later. Organizations in the EU region connect to ide.eu.coderabbit.ai.
Optional and command-specific access
Some CLI features contact additional services. Allow only the entries needed for your workflow.
GitHub can redirect release downloads to its asset delivery domains. Follow GitHubâs current network guidance rather than relying on one fixed asset hostname.
Default-branch detection can contact the repositoryâs configured origin. If the origin is unavailable from the restricted environment, pass
--base <branch> to avoid that lookup.
Route reviews through a proxy
In CLI 0.9.1 or later, the review WebSocket connection uses the standard proxy environment variables. Thewss:// review connection goes through HTTPS_PROXY, or through ALL_PROXY when HTTPS_PROXY is not set. Lowercase names, such as https_proxy, also work. Hosts listed in NO_PROXY connect directly, and loopback addresses, such as localhost, always connect directly.
http:// or https://. With any other scheme, such as socks5://, the CLI canât open the review connection, and the review fails with con_err: webSocket connection failed after its connection retries. The error does not include the proxy URL or its credentials. TLS certificate checks for the CodeRabbit connection stay on through the proxy.
Proxies that add the API key
Some managed environments, such as sandboxed agent runtimes, give the CLI a placeholder API key and use a proxy that replaces it with the real key in request headers. By default, a review authenticated with an Agentic API key sends the key in the WebSocket handshake header and again inside the WebSocket connection, where such a proxy canât replace it. SetCODERABBIT_API_KEY_HEADER_ONLY=1 so that API-key reviews authenticate with the handshake header only:
Configure Claude Code cloud environments
Claude Code cloud environments use the network policy attached to the selected environment. To run CodeRabbit from an environment with restricted access:- Edit the selected Claude Code cloud environment.
- Set Network access to Custom and retain Claudeâs default allowed domains.
- Add the applicable CodeRabbit domains from the table above, one domain per line.
- Save the environment and start a new cloud session so the updated policy applies.
Authenticate cloud and headless sessions
Browser-based authentication does not require a public inbound firewall rule. Fresh cloud sessions do not inherit CodeRabbit authentication from your local computer. Use an Agentic API key only when the runtime can inject it securely, and follow the Headless CLI integration guide.Self-hosted CodeRabbit
For a self-hosted CodeRabbit deployment, allow the hostname, protocol, and port configured for your instance. The CLI uses HTTPS for authentication and API requests and WSS for the review connection. You might still needcli.coderabbit.ai if you install or update the CLI from CodeRabbitâs distribution service. See Use with self-hosted CodeRabbit for configuration steps.
Troubleshooting
Runcr doctor from the same restricted environment as one connectivity smoke test, then retry the exact command or hostname that failed.
cr doctor is a connectivity smoke test. A passing report does not replace retrying the original command and does not prove that an authenticated review can complete through every network intermediary.
Whatâs next
Headless CLI integration
Authenticate non-interactively with an Agentic API key
Use with self-hosted CodeRabbit
Connect the CLI to your organizationâs self-hosted CodeRabbit instance
CLI Command Reference
Review CLI commands, options, and diagnostics