Connectivity
Your Paseo app connects to the daemon running on your computer or server. You can connect through the Paseo relay or directly with Tailscale.
Paseo relay
The relay works without Tailscale, port forwarding, or network configuration. Traffic is end-to-end encrypted.
Relay is disabled until you enable it.
Enable relay from Paseo Desktop
- Open Settings → your host → Pair a device.
- Select Enable relay.
- Scan the QR code with Paseo on your phone, or copy the pairing link and paste it into the phone app.
Enable relay from the CLI
Run:
paseo daemon pair
Confirm when prompted. Paseo prints a QR code and pairing link. Scan the QR code with Paseo on your phone, or choose Paste pairing link in the phone app.
Tailscale
Install Tailscale on the daemon machine and your phone. Sign in to the same tailnet on both devices.
1. Find the daemon machine's Tailscale IP
Run this on the daemon machine:
tailscale ip -4
Copy the address it prints. The example below uses 100.101.102.103.
2. Configure the daemon
Open ~/.paseo/config.json and set daemon.listen to the Tailscale IP:
{
"$schema": "https://paseo.sh/schemas/paseo.config.v1.json",
"version": 1,
"daemon": {
"listen": "100.101.102.103:6767"
}
}
Keep the other settings already in the file. If it has a daemon object, add listen inside that object.
To restrict access with a password, see Password authentication.
Restart the daemon:
paseo daemon restart
If Paseo Desktop manages the daemon, use Settings → your host → Overview → Restart daemon.
3. Connect the phone app
- Connect Tailscale on your phone.
- Open Paseo and go to Settings → Add host → Direct connection.
- Enter the Tailscale IP in Host.
- Enter
6767in Port. - Leave Use SSL off and select Connect.
If the host was already paired through the relay, Paseo adds the direct connection to the same host.
Troubleshooting
- Connection timed out: Check that Tailscale is connected on both devices and that you used the daemon machine's Tailscale IP.
- Connection refused: Run
paseo daemon statusand confirm the daemon is running on the configured IP and port. - Config change has no effect: Restart the daemon after editing
config.json.