Routes

Expose only the apps you approve.

Routes are named paths under the VPS relay. The phone opens the VPS tunnel IP, and the Home Agent proxies the request to a Tater service or any local app target you choose.

Default

Home Agent and Tunnel UI

The built-in tunnel route is available at the base relay path after the phone is connected to WireGuard.

http://10.88.0.1:4174/relay/
Named route

Main Tater app

Add a route named tater to the Home Agent UI and point it at the local Tater app port.

http://10.88.0.1:4174/relay/tater/
LAN target

Another local service

Targets can also be another LAN machine if the Home Agent machine can reach it, for example an Emby host.

http://10.88.0.1:4174/relay/emby/
Route settings

Use the simple UI first, advanced switches only when an app needs them.

Target URL

The local URL the Home Agent can reach, such as http://127.0.0.1:8501 or http://10.4.20.204:8096.

Required

WebSockets

Enable for apps that keep live UI state over WebSockets, streaming, or long-lived browser sessions.

Advanced

Host header

Use only when an app expects its own public host or rejects the relay host.

Advanced
Tater mascot with mobile QR setup
Once the phone VPN is on, every route uses the 10.88.0.1 VPS tunnel address.
Examples

Route names become clean URLs.

Access route examples
Route name: tater
Local target: http://127.0.0.1:8501
Use: http://10.88.0.1:4174/relay/tater/

Route name: emby
Local target: http://10.4.20.204:8096
Use: http://10.88.0.1:4174/relay/emby/