How to Connect to a VPS Using Termux

Prepare Termux

Update packages and install OpenSSH before connecting. Keep your private key on your own device and never paste it into public chats, forms, or provider support messages.

• Install the OpenSSH package.
• Confirm the VPS public IP or hostname.
• Have the correct SSH username ready.
• Use a private key that belongs to you.

Create an SSH key if you do not have one

Generate a modern SSH key locally, keep the private half in Termux, and add only the public key to the VPS or provider console. A public key can be shared for server authorization; the private key must remain secret.

Connect with SSH

Use the standard SSH command with your username and server address. On the first connection, SSH shows a host fingerprint. Compare it with a trusted provider or server source before accepting when possible.

• Default Linux usernames vary by image.
• Port 22 is common but can be changed.
• A timeout usually points to network, firewall, address, or server-state problems rather than an SSH password issue.

Protect your private key

Restrict file permissions so other local processes cannot read the key. Use a passphrase when practical and do not copy private keys into cloud notes or public repositories.

First steps after login

Update the operating system, create a non-root workflow when appropriate, review firewall rules, and confirm time, disk, memory, and network settings before installing production software.

• Apply security updates
• Confirm disk and memory
• Review SSH and firewall configuration
• Install only required services

Common connection problems

Permission denied usually means the username, key, or server authorization is wrong. Connection refused suggests no SSH service is listening at that address and port. A timeout often means the route or firewall is blocking the connection.