Remote Access
Operate a remote Hydris node via the built-in proxy
When a remote Hydris node's policy restricts what remote connections may do, the proxy lets you operate it as if you were local — it serves the UI locally and forwards all API requests to the remote, so the remote node sees them as coming from a trusted connection.
Usage
hydris --server host:portThis starts a local HTTP server (default port 8080, override with PORT env var) that serves the UI locally while connected to a remote node. With an SSH tunnel, the remote sees requests arriving on its own localhost and treats them as a trusted connection; with a direct connection, the remote sees the proxy machine's address and its policy applies accordingly.
Tunnel Support
For nodes not directly reachable, the proxy supports SSH and WireGuard tunnels:
| Format | Description |
|---|---|
host:port | Direct connection |
ssh://[user@]host[:port] | SSH tunnel — gRPC is reached at localhost:50051 on the remote |
--wireguard /path/to/wg.conf | WireGuard tunnel — requires --server host:port for the remote address inside the tunnel |
SSH
hydris --server ssh://user@remote-hostOpens an SSH tunnel to the remote host and forwards gRPC traffic through it. The remote Hydris node is expected to listen on localhost:50051 on the remote machine. SSH key authentication is used.
WireGuard
hydris --server 10.0.0.2:50051 --wireguard /path/to/wg.confEstablishes a WireGuard tunnel using the provided config file. The --server address is the remote node's address inside the WireGuard network.