Networking
Connection Proxies
Reusable SOCKS5 and HTTP CONNECT profiles for machines that need to connect through a proxy.
When a machine can only be reached through a proxy — a corporate egress, a tunnel endpoint — save the proxy once as a profile and attach it wherever it is needed. Proxies are part of Premium.
Create a profile
A profile has:
- Type — SOCKS5 (default port 1080) or HTTP CONNECT (default port 8080).
- Host and Port.
- Authentication — None or Username Password. Credentials are stored in the device Keychain, like every secret in SwiftServer.
Attach it
- Per machine — the Connection Proxy section in the machine editor. Every connection to that machine (terminal, SFTP, Docker, monitoring, forwarding) then goes through the proxy.
- Per forwarding rule — a port forwarding rule's Proxy picker overrides the machine's setting for just that rule; the default is Machine Default.
Note on Mosh
Mosh bootstraps over SSH through the proxy, but its UDP session connects directly — machines behind a proxy need a directly reachable UDP Host configured for Mosh.