A host will not connect
When a connection fails, Warpeer shows Connection Error with the endpoint, a summary, suggestions and the technical details. Open Vaults, then Logs, for the full history. Common causes:
- Wrong address or port. Check that you can reach the server from the device's network. Servers on a private network need a VPN such as Tailscale on the device.
- Authentication failed. Check the username and the Keychain credential on the host, or tap Change Credential to pick another one. For key sign-in, the public key must be in
~/.ssh/authorized_keyson the server, and an encrypted key needs its passphrase. - SSH 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.
A session disconnects in the background
Warpeer keeps connected terminals alive with a foreground service and an ongoing notification. If notifications are turned off for Warpeer, or a battery saver stops background apps, Android may close the connection. Allow notifications for Warpeer in Android Settings. Your tmux or Herdr session keeps running on the server; return to Warpeer and tap Reconnect. See Sessions and tabs.
Features missing compared with iPhone
The Android build does not list tmux or Herdr sessions, coding agents, git status or live host metrics yet, and has no file previews, voice input or image attachments. These are not connection problems. Your terminal works without them.
Send feedback
Open Settings, then Help & Feedback, and tap Copy Diagnostics. It copies only the app and Android versions, never hosts, commands, passwords, credentials or terminal output. Paste it into an email to [email protected] with a description of what happened.