Proxy configuration

Route device and workload traffic through an HTTP or HTTPS forward proxy.

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.

Configure the proxy from the dashboard

To go through this section, you need:

access to the SPEKTRA Edge dashboard
an active project
a device provisioned under the project
the name and the port number of the proxy server

Go to the Device overview page of the target device under your project by clicking the name of the device on the Project overview page.

Clicking the device name on the Project overview page. — Clicking the device name on the *Project overview* page.

Open the Update device details page by clicking the Edit detail option of the device menu option.

Click the Edit detail option of the device menu option.

Configure the proxy server in the HTTP and/or HTTPS proxy server section of the Update device details page.

You can configure the device to bypass the proxy servers for the particular communication, e.g. the node local communication in the example below.

HTTPS proxy servers

Most of the container registries require the HTTPS connection to access and retrieve images.

Please consult the IT department on the access policies for the container registries and the internet.

Save the page and you are good to go. The device goes through the proxy server for the HTTP and HTTPS traffic.

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

Configuration reference — the proxy settings and which interfaces they apply to.
Image settings — setting a proxy before a device first boots.

Next steps

Review connectivity & ports to confirm what the device must reach through (or around) the proxy.