Remote access
Experimental. Hauser can publish itself through Tailscale Funnel, so paired phones reach it from anywhere without port forwarding.
How it works
Section titled “How it works”- The image ships a small sidecar (
hauser-tunnel). It joins your tailnet as a userspace node and publishes Hauser ashttps://<hostname>.<tailnet>.ts.net. - Every forwarded request is marked as remote. The Hauser server then requires a device token from pairing. Without a token only health and build info answer.
- The panel and the LAN keep working as before if the sidecar is missing.
Settings → Connections → Services → Remote access:
- Sign in to Tailscale with Google, Apple, Microsoft or GitHub. Open the link or scan the QR code.
- Approve HTTPS certificates and Funnel once in the Tailscale console. Hauser keeps retrying.
- The card shows Active at … with the address.
Own address replaces the tunnel in the pairing code if Hauser is already reachable through your own reverse proxy.
Environment
Section titled “Environment”| Variable | Purpose |
|---|---|
HMI_TUNNEL_BIN |
Path to the sidecar binary. Set in the image. |
HMI_TUNNEL_STATE |
State directory. Default tunnel/ next to config.json. |
HMI_REMOTE_URL |
Your own public address instead of the tunnel. |