A host will not connect
When a connection fails, the host shows a red error button in Vaults, then Hosts. Tap it to read the last error, or open Vaults, then Logs, for the full history. Common causes:
- Wrong address or port. Check that you can reach the server from the iPhone's network. Servers on a private network need a VPN such as Tailscale on the iPhone.
- Authentication failed. Check the username and the Keychain credential on the host. For key sign-in, the public key must be in
~/.ssh/authorized_keyson the server, and an encrypted key needs its passphrase. - Host Key Changed. The server presented a different fingerprint from the one you trusted. If you rebuilt or replaced the server, confirm the new fingerprint with its administrator, delete the old entry in Known Hosts and connect again. If you did not expect a change, do not connect.
Sessions, agents or git do not appear
These features rely on the remote helper. Your terminal still works if the helper cannot run, but the extra information is missing. Check that:
- your home directory on the server is writable and allows programs to run;
- the server runs Linux or macOS on x86_64 or ARM64;
- tmux or Herdr is running, if you expect sessions to be listed;
- the current pane is inside a git repository, for git status.
If a newer Warpeer app on another device installed a newer helper, update Warpeer on this iPhone.
A session disconnects in the background
iOS limits how long apps stay active after you leave them. Your tmux or Herdr session keeps running on the server. Return to Warpeer and tap Reconnect, or raise the background time limit and Keep Alive interval in Settings. See Sessions.
Send feedback
Open Settings, then Help & Feedback, and tap Copy Diagnostics. It copies only the app and iOS versions, never hosts, commands, passwords, credentials or terminal output. Paste it into an email to [email protected] with a description of what happened.