Configure the Proxy
This article refers to Platform v3.0.0. The current Platform version is v3.2.0.
Overview
A proxy sits between the edge node and the external network and can be used to enforce security, caching, or organizational policy. Barbara Panel lets you enable, configure, and disable a proxy per node from the Proxy segment of the Networking card.
For a generic introduction to proxies, see Proxy server (Wikipedia).
Proxy controls
The Proxy segment of the Networking card shows the configured URL and interface, and exposes ON and OFF buttons to enable or disable the proxy.

Proxy segment in the Networking card
Before enabling a proxy on a node:
- Make sure the proxy settings are correct for your network.
- Make sure the proxy server itself is reachable.
- If you lose connectivity after enabling, the proxy configuration is the first place to check.
Enable the proxy
- On the Networking card, click the ON button on the Proxy segment. The proxy popup opens.
- Fill in the configuration:
- URL ** — protocol, address, and port of the proxy server.
- USER (optional) — username for authentication.
- PASSWORD (optional) — password for the user above.
The only supported proxy protocols are HTTP and Socks5.

Proxy configuration popup
- Click ENABLE. A confirmation warns you that the node needs to reboot for the change to take effect.

Proxy enable reboot confirmation
Until the node reboots, the proxy status shows OFF with a Pending reboot to be enabled warning.

Proxy pending reboot
Once the node reboots, the proxy status becomes ON.

Proxy ON after reboot
Disable the proxy
- On the Networking card, click the OFF button on the Proxy segment. A confirmation warns you that the node needs to reboot for the change to take effect.

Proxy disable reboot confirmation
- Until the node reboots, the proxy status still shows ON with a Pending reboot to be disabled warning.
- Once the node reboots, the proxy status becomes OFF.

Proxy OFF after reboot
Summary
A proxy on an edge node is configured from the Proxy segment of the Networking card: only HTTP and Socks5 are supported, the URL is the only mandatory field, and every change to the enabled state requires a node reboot to take effect.