How can we help?

1. Tap Quick Connect (▶) in the top bar, or Hosts → + to save the server for later.
2. Enter Host / IP, Port (usually 22), and Username, then choose Authentication.
3. On a saved host, tap the terminal icon for SSH, or the upload and download icons for files.

1. Identities → + → Generate keypair (Ed25519 is a good default).
2. Tap Install Key To Host on the key and choose the host. It uses the host's password once.
3. Edit the host: set Authentication to Identity and pick the Identity key.

1. Connect as usual. When the server asks a question such as a verification code, SSHPeaches shows it in a dialog.
2. Type the code from your authenticator app and tap Continue. The saved password is still sent for the password question.

1. Copy the config file to your phone.
2. Hosts → Import hosts (top bar) → OpenSSH config, then pick the file and review the import.
3. Hosts and LocalForward entries are imported. IdentityFile keys aren't, so add them in Identities.

1. Use the extra keys under the terminal. Ctrl and Alt apply to the next key you press, so Ctrl then c sends Ctrl-C.
2. Tap Fn for F1–F12. Back returns to the main keys.
3. Keyboard Editor changes which keys are on the two main rows: shortcuts such as Ctrl-R and Shift-Tab, symbols, Paste, or your own text.

1. Turn on Settings → Terminal → Use built-in keyboard.
2. SSHPeaches then shows its own full keyboard under the extra keys, with letters, numbers, symbols, and no autocorrect.
3. Tap the keyboard key or press Back to hide it; tap the terminal to bring it back. Hardware keyboards keep working.

1. Long-press the terminal to select text, drag the handles, then tap Copy.
2. Long-press again and tap Paste to paste. You can also add a Paste key in the Keyboard Editor.

1. Drag up or down on the terminal to scroll through earlier output.
2. In a session, ⋮ → Find searches the output.
3. Pinch the terminal to zoom, or turn on Settings → Terminal → Use volume buttons to adjust font size.

• Swipe for arrow keys: while it's checked, swiping on the terminal sends arrow keys, handy in editors and shell history.
• Insert password: types this host's saved password, after asking you first.
• Change theme: switches colors for this session only.
• Find, Snippets (run a saved command), and Reset (sends reset to fix a garbled screen).

1. Snippets → + to save a command. The editor highlights shell syntax.
2. In a session, ⋮ → Snippets runs one in the terminal.
3. A host's Startup snippet runs every time you connect to it.

1. Theme Editor creates and edits terminal themes: colors, font, and font size.
2. Pick a host's Terminal profile to give it its own theme.
3. In a session, ⋮ → Change theme switches only that session.

1. Ctrl+K opens Quick Connect, F1 opens Help, and Alt+1 to Alt+8 jump between screens.
2. Ctrl+/ shows the full list.

1. Turn on Settings → Background Sessions → Run shells in background.
2. Background connection timeout sets how long sessions stay open while you're away.
3. A notification shows while sessions run. Tap it to return to the session.
4. If long transfers stop with the screen off, allow SSHPeaches to ignore battery optimization in Android settings.

1. SSH terminals reconnect on their own and keep the screen. This is Settings → Background Sessions → Reconnect automatically.
2. The shell itself restarts on the server, so turn on Attach to tmux in the host's settings to land back in the same shell.
3. Mosh sessions and the file browser don't reconnect; open them again.

1. Open the host with the upload or download icon to get the file browser. Tap the path above the list to jump to a parent folder.
2. Select a file, then the ⋮ actions menu: Edit opens small text files in an editor that saves back to the server; Permissions changes who can read, write, or run it.
3. A download that fails partway picks up where it stopped when you download the same file again.

1. Port Forwards → +. Local port is the port on your phone. Destination host and Destination port are as the server sees them, often localhost and the service's port.
2. Set Associated host and leave Enable now on. The forward starts when you connect to that host.
3. While connected, open localhost and the Local port on your phone, for example http://localhost:8080.
4. Only local forwarding (-L) is supported.

1. On the old phone: Settings → Export, then choose Wi-Fi (both phones on the same network), QR code, File, or Share (Bluetooth, Quick Share, email).
2. Turn on Include passwords and private keys to bring secrets too, and set an Export passphrase.
3. On the new phone: Settings → Import and choose the same method. For Wi-Fi, scan the code the old phone shows. A shared file opens SSHPeaches when you tap it.

1. There is no PIN recovery. Your saved passwords and keys are encrypted with it.
2. If biometric unlock is on, unlock with your fingerprint instead.
3. Otherwise the only way back in is Android Settings → Apps → SSHPeaches → Storage → Clear storage, which deletes all hosts, keys, and passwords. Keep an export as a backup.

No. They're encrypted on your phone and only sent to the servers you connect to, as part of logging in. There's no account and no cloud copy. See the privacy policy for what diagnostics include and how to turn them off.

• Check the spelling of the host name.
• Names that only work on your home or office network (such as .local or .lan names) won't work elsewhere. Use the IP address, or join that network or its VPN first.
• Check that your phone is online.

• The SSH server isn't running, or it listens on a different port. The usual port is 22.
• On the server, check it with sudo systemctl status ssh (on some systems: sshd).
• A firewall on the server may be blocking the port.

• Addresses like 192.168.x.x and 10.x.x.x are private. They only work on the same network, or through a VPN such as Tailscale or WireGuard, not over mobile data.
• Check that the server is switched on and the address and port are right.
• A firewall or router may be blocking the port. Home servers also need port forwarding on the router.

• The network dropped or changed, for example from Wi-Fi to mobile data. Tap Retry; terminals usually reconnect on their own.
• If this keeps happening while the app is in the background, turn on Settings → Background Sessions → Run shells in background.

• SSHPeaches stopped before logging in because the server's host key wasn't accepted.
• If the server was reinstalled or its keys were regenerated, edit the host, tap Clear stored host key, connect again, and check the fingerprint.
• If nothing changed on the server, don't connect. Someone may be intercepting the connection.

• Check the username. It is case-sensitive.
• Many servers turn off password logins. Use a key instead: Identities → + → Generate keypair, then Install Key To Host, then set the host's Authentication to Identity.
• Servers often block logging in as root. Log in as a normal user.

• The public key must be in ~/.ssh/authorized_keys for your user on the server. Identities → Install Key To Host adds it, using the host's password once.
• Check the username and that the host uses the right Identity key.
• On the server, ~/.ssh must be mode 700 and authorized_keys mode 600, or SSH ignores them.

• Install mosh on the server, for example sudo apt install mosh.
• If mosh-server isn't on the PATH, set its full path in Settings → Advanced settings → Mosh server command.
• Mosh also needs UDP ports 60000–61000 open on the server's firewall.

• Check your shell's startup files (.bashrc, .zshrc, .profile) for an exit or a command that fails.
• Try a host with Attach to tmux turned off, then look at the connection log for the last message.