Skip to content

Proxy Configuration

If a machine is behind a corporate firewall that requires outbound connections to go through a proxy, Tunnel Whisperer can route its traffic through a SOCKS5 or HTTP proxy. The setting works in all three roles — server and client tunnels use it for the Xray transport, and relay-mode operations (provisioning, relay SSH, enrollment) honor it too.

Supported Protocols

  • socks5://[user:pass@]host:port
  • http://[user:pass@]host:port

Setting a Proxy

CLI

tw proxy set socks5://proxy.corp.example.com:1080
tw proxy set http://user:pass@proxy.corp.example.com:8080

Dashboard

Go to Config → Proxy → enter the URL → Save.

Clearing a Proxy

CLI

tw proxy clear

Dashboard

Go to Config → Proxy → Clear.

Viewing the Current Proxy

tw proxy

  Proxy: socks5://proxy.corp.example.com:1080

When It Takes Effect

Proxy changes are saved to config.yaml and take effect on the next server start or client reconnect. If a server or client is currently running, the dashboard shows a "Configuration has changed" notification prompting a restart/reconnect.

How It Works

The proxy is applied to Xray's outbound transport settings. All VLESS+XHTTP+TLS traffic to the relay is routed through the specified proxy. The proxy sees only encrypted TLS traffic to your relay domain on port 443.