The SSH client provides a line-oriented console for connecting to servers and network devices from Android. It is convenient for focused checks when a full desktop terminal is unavailable.
How it works
SSH encrypts authentication and command traffic between the phone and server. Network Toolkit supports password and private-key authentication as confirmed by the current application implementation.
How to use it in Network Toolkit
- Confirm the server address, port, and account.
- Choose password or private-key authentication.
- Verify the server identity information presented by the connection.
- Run only the commands required for the troubleshooting task, then close the session.
What information you can see
- Encrypted SSH session output
- Authentication and connection errors
- A line-oriented remote command workflow
Common use cases
- Check a Linux server status
- Inspect logs during an outage
- Restart an authorized service
- Manage a lab device from a phone
Limitations and Android considerations
SSH and SFTP in one place
The SSH client signs in with a password or a private key, with an optional key passphrase. On the same sign-in, the Files (SFTP) view lets you browse folders, download files to the phone and upload files to the server. Downloads open Android's share sheet, so you can save them to Files or send them on.
Host key verification
On the first connection the app shows the server's host key fingerprint and remembers it. Later connections are compared with the saved key; if it changes, you see the old and the new fingerprint before continuing. A changed key is normal after reinstalling a server, but it can also mean a different machine is answering at that address. On the server, ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub prints the fingerprint to compare.
A line console, not a full terminal
The console sends a command and shows its output line by line. That suits commands such as uptime, df -h, systemctl status nginx, journalctl -n 50 or docker ps. Full-screen programs such as top, nano or vim do not display correctly; use top -b -n 1 instead of top, or a desktop terminal for editing.
Common SSH connection errors
| Error | Usual cause |
|---|---|
| Connection refused | No SSH server is running, or it listens on a port other than 22 |
| Timed out | Wrong address, a firewall, or the server is on another network |
| Authentication failed | Wrong user name, password or key, or password login is disabled on the server |
| Host key changed | Server reinstalled or keys regenerated — or another machine at that address; verify before you accept |
Android closes network connections of apps that stay in the background for more than a few seconds on recent versions. The SFTP view reconnects by itself; an interactive shell has to be opened again.
Related network tools
Ping Tool for Android, Port Scanner for Android can help confirm the result from another angle.
Frequently asked questions
Which SSH authentication methods are supported?
The verified implementation includes password and private-key authentication.
Why can ping work while SSH fails?
The SSH port may be closed, filtered, bound to another interface, or the server may reject authentication.
Should I accept a changed host key?
Only after independently confirming why it changed. An unexpected change can indicate a rebuilt server or a security problem.
Can I transfer files over SFTP on Android?
Yes. The Files (SFTP) view uses the same SSH sign-in to browse folders, download files and upload files.
Which SSH sign-in methods are supported?
Password and private-key authentication, with an optional passphrase for the key.

