Configuring an outbound proxy on the edge

Some customer networks require all outbound HTTPS and WebSocket traffic to pass through a corporate forward proxy. The edge honours the standard HTTPS_PROXY environment variable so it can reach the logiccloud cluster 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 cluster 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

1. Locate the environment file used to start the edge container on the device.

2. Add the following line, replacing the URL with your proxy:

   HTTPS_PROXY=http://proxy.example.com:3128

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

4. 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.