Proxy configuration
If your devices reach the internet through a forward proxy, configure the proxy so that both the device’s connection to the SPEKTRA Edge platform and your workloads’ traffic are routed correctly.
What you can set
Proxy configuration consists of the standard proxy settings:
| Setting | Meaning |
|---|---|
http_proxy |
Proxy URL for plain HTTP traffic. |
https_proxy |
Proxy URL for HTTPS traffic. |
no_proxy |
Hosts and networks that should bypass the proxy (comma-separated). |
In addition, you can specify which network interfaces the device should use to reach the platform through the proxy, so control-plane traffic uses the intended path.
Where to set it
You can configure the proxy:
- at image creation, so devices use the proxy from first boot, or
- from the dashboard for a device that is already online.
The proxy applies both to the device’s own communication with the platform and to container workloads running on the device.
Fallback behavior
The device determines the best route to the platform and will fall back to a direct connection when the proxy is not usable, so a proxy outage does not necessarily take a device offline. If you require that all traffic traverse the proxy, ensure direct egress is blocked at the network level rather than relying on device configuration.
no_proxy recommendations
Add to no_proxy any destinations that must not go through the proxy, such as:
- on-site services the device talks to directly (local registries, local APIs)
- link-local and private ranges used on the device’s LAN
Next steps
- Review connectivity & ports to confirm what the device must reach through (or around) the proxy.