If your network requires a proxy for outbound HTTPS, configure it via the standard .NET environment variables before starting either tool.

Configuration 

  # Linux / macOS
export HTTPS_PROXY=http://proxy.corp.example.com:8080
cloud-share-sender

# Windows (PowerShell)
$env:HTTPS_PROXY = "http://proxy.corp.example.com:8080"
cloud-share-sender

The devtunnel CLI respects system proxy settings on Windows. On Linux/macOS, set HTTPS_PROXY before running cloud-share-sender or cloud-share-receiver.

Authenticated proxies

If your proxy requires credentials, include them in the URL:

  export HTTPS_PROXY=http://username:password@proxy.corp.example.com:8080

⚠️ Warning: Avoid storing proxy credentials in shell profiles or scripts. Prefer environment-specific secrets management.

Proxy bypass

If only specific hosts should bypass the proxy, use NO_PROXY:

  export NO_PROXY=localhost,127.0.0.1
export HTTPS_PROXY=http://proxy.corp.example.com:8080
cloud-share-sender

Troubleshooting proxy issues

If the sender fails to create a tunnel behind a proxy:

  1. Verify the proxy allows WebSocket/HTTPS to *.devtunnels.ms
  2. Some proxies block WebSocket upgrades — check with your network administrator
  3. Test direct connectivity: curl -x http://proxy:8080 -I https://global.rel.tunnels.api.visualstudio.com
  4. Run with verbose logging: cloud-share-sender --log verbose