New

Works behind corporate proxies — HTTP CONNECT and SOCKS5

Computers that reach the internet only through a proxy can still be supported. The agent sends its API calls and the remote-session link through an HTTP or SOCKS5 proxy, with a login if needed.

One command

silux-agent set-proxy http://user:password@proxy:3128 (or socks5://proxy:1080), then restart the service. silux-agent status shows the proxy in use, and set-proxy off turns it off.

Everything goes through it

API calls, heartbeats and the remote-session WebSocket. The session link uses HTTP CONNECT, so TLS stays end to end and the proxy never sees the content.

Standard settings honoured

Without a configured proxy the agent uses SILUX_PROXY, HTTPS_PROXY or ALL_PROXY, and NO_PROXY lists the hosts to reach directly.

Frequently asked questions

Does Silux Connect support SOCKS5 proxies?

Yes, with or without username and password, as well as HTTP proxies with Basic authentication.

Related features

Agent command line

Script your rollout: get the ID, set a password, set a proxy

Unattended access

Unattended access passwords with permission profiles

Connect by ID

Connect by ID and code — the person at the computer decides

See how this compares on the feature matrix, or find Silux Connect in your country and city.