Configuring an outbound proxy on the edge

Some networks require all outbound HTTPS and WebSocket traffic to pass through a corporate forward proxy. The edge honors the standard HTTPS_PROXY environment variable so it can reach the logiccloud cloud through your existing proxy infrastructure.

When to configure a proxy

Configure a proxy if any of the following is true on the network where the edge device runs:

• Outbound HTTPS to the public internet is blocked except through a named proxy.
• WebSocket traffic to the logiccloud cloud fails to establish even though the device has network connectivity.
• Your IT policy requires all device traffic to be inspected by a corporate proxy.

Setting the proxy

HTTPS_PROXY is a container environment variable — it is passed to the edge container at run time. It is not a key in the install script’s configuration file (/etc/logiccloud/setup.conf), which only stores container-runtime settings.

1. Inject the variable where the container is started, using the mechanism for your runtime:

   • Docker / Podman: add -e HTTPS_PROXY=http://proxy.example.com:3128 to the run command.
   • Compose: add it under the service’s environment: block.
   • LXC: add lxc.environment = HTTPS_PROXY=http://proxy.example.com:3128 to the container config.

   You can also set HTTP_PROXY and NO_PROXY the same way.

2. Restart the edge container so it picks up the new environment.

3. Open the portal and confirm the device reappears as Online.

When HTTPS_PROXY is unset, the edge connects directly. There is no need to set this variable on networks with open outbound HTTPS.

The edge does not currently validate the proxy URL up front. If the URL is mistyped or the proxy is unreachable, the device will simply appear Offline in the portal until the value is corrected and the container is restarted.