Network, Proxy, and VPC Issues

This page helps you resolve network connectivity issues with Qoder CLI CN. For network configuration, see Network, Proxy, and VPC.

Connection timeouts or failures

Confirm the machine can reach the external network and can resolve and connect to the service domains.
On corporate networks or in restricted environments, a proxy is usually required (see below).
For transient network hiccups, retry later; general.retryFetchErrors (on by default) automatically retries certain fetch errors.

Proxy configuration

Configure a proxy via the standard environment variables:

export HTTPS_PROXY="http://proxy.example.com:8080"
export HTTP_PROXY="http://proxy.example.com:8080"
export NO_PROXY="localhost,127.0.0.1,.internal.example.com"

HTTPS_PROXY / HTTP_PROXY: used for HTTPS / HTTP requests respectively.
NO_PROXY: a comma-separated list of hosts that bypass the proxy.
Both cases are recognized (HTTPS_PROXY and https_proxy both work).
Restart Qoder CLI CN after changing environment variables for them to take effect.

For Agent SDK and desktop integrations, an explicit SDK proxy option takes precedence. When it is omitted, integrated qoderclicn uses inherited proxy environment variables if environment proxy discovery is enabled. NO_PROXY / no_proxy controls which destinations bypass the proxy.

DNS resolution issues

If domain resolution misbehaves, adjust the resolution order with the advanced.dnsResolutionOrder setting.
A restart is required after changing it.

Certificate issues

Corporate proxies often perform TLS interception; add the corporate root certificate to the system trust store.
For errors like unable to verify the first certificate, specify additional trusted certificates via an environment variable:
```
export NODE_EXTRA_CA_CERTS=/path/to/corp-root-ca.pem
```
You can also use SSL_CERT_FILE to specify a certificate file path. See the certificate configuration section in Network, Proxy, and VPC.
Confirm the system time is correct — clock skew causes certificate validation failures.

VPC / private deployment

For CN private deployments, specify the instance name via the vpcInstanceName setting; public domains are mapped to the corresponding per-instance private hosts.
A restart is required after changing it.
Confirm network reachability to the private gateway.

Next steps

Network configuration guide: Network, Proxy, and VPC.
Sign-in network issues: Sign-in and Authentication Issues.

​Connection timeouts or failures

​Proxy configuration

​DNS resolution issues

​Certificate issues