Node Proxies

简体中文 | English

A node proxy discovers and probes a network egress that only a particular node can access. A proxy belongs to one node; it is not a system-wide or Agent-wide proxy.

Add a Proxy

Open the node's Public IPs tab and select Manage proxies in the upper right. The dialog keeps proxy creation, editing, enabling, disabling, and deletion together instead of mixing proxy configuration into the public-IP list.

HTTP, HTTPS, and SOCKS5 proxies are supported. After a new proxy is saved or an existing proxy changes, the Agent checks whether it provides a usable IPv4, IPv6, or dual-stack public egress. Results automatically join the node's current public-IP set; no probe target is created manually.

Disabling a proxy stops using it for discovery and probes while retaining the configuration. Enabling it again checks its public egresses again.

Credentials and Scope

The Center manages usernames and passwords. Passwords are encrypted in config.db, delivered only to the owning node's Agent, and never returned by the API or web interface. Leaving a password blank while editing preserves the current value; only an explicit clear action removes it.

The proxy path constrains only egresses found through that proxy. Center access to GitHub, Agent access to the Center, and the node's default direct discovery paths do not automatically use it.

Dynamic Proxies

When a dynamic proxy egress changes, the new public IP appears as a new IP identity and the previous address becomes historical. If the new value appeared before, IPChronicle reconnects its existing reports. When the node setting to probe newly discovered public IPs is enabled, an established proxy path finding a new address triggers one complete probe for that address.

The interface reports proxy unavailability, address-family check failures, and pending deletion explicitly. Failure for one family describes that check only; it is not presented as proof that the node permanently lacks that family.