> For the complete documentation index, see [llms.txt](https://docs.mobb.ai/mobb-user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobb.ai/mobb-user-docs/common-troubleshooting-scenarios/cli-corporate-proxy.md).

# Mobb CLI - Blocked by corporate proxy

Running the [Mobb CLI](/mobb-user-docs/getting-started/mobb-cli.md) on a network that requires an outbound HTTP(S) proxy.

**Symptoms**

* The CLI hangs or fails with connection/timeout errors on a network that requires an outbound HTTP(S) proxy.

**Likely cause**

The CLI's outbound requests aren't being routed through the corporate proxy.

**Resolution**

1. Set the standard proxy environment variables before running the CLI, for example:

   ```bash
   export HTTPS_PROXY=http://<your-proxy-host>:<port>
   export HTTP_PROXY=http://<your-proxy-host>:<port>
   ```
2. If long-lived connections are dropped by the proxy/firewall, add the `--polling` flag so the CLI uses HTTP polling instead of WebSockets — see the [Mobb CLI Troubleshooting Guide](/mobb-user-docs/getting-started/mobb-cli/troubleshoot.md).
3. Re-run the command and, if it still fails, capture debug output and share it with <support@mobb.ai>.

{% hint style="info" %}
The same proxy considerations apply to the **Mobb Broker** when it runs in a restricted network — see [My broker can't reach the SCM](/mobb-user-docs/common-troubleshooting-scenarios/broker-cannot-reach-scm.md).
{% endhint %}