VPS Tutorials
Connect to a Linux VPS from Windows with PowerShell or PuTTY
Prepare four connection details, make your first SSH login from Windows, verify the server fingerprint and understand hidden password input, timeouts and authentication errors.

A Windows computer can connect directly to a Linux VPS. Check for the ssh command in PowerShell, then log in with the server's address, port and account. PuTTY is an alternative if you prefer entering connection details in a form.
This guide covers a first connection: collect the details, log in, confirm success and exit. The destination is a Linux VPS, so you get a text terminal. For a Windows VPS with a graphical desktop, follow the provider's Remote Desktop instructions instead.
Find the VPS activation email or its connection settings in the provider dashboard:
| Detail | Correct value |
|---|---|
| IP address | The server's public IP, not the purchase website; do not add https:// |
| SSH port | Often 22; use the actual value supplied by the provider |
| Username | A server OS account, such as the documented root, ubuntu or one you created |
| Authentication | That account's server password or the SSH key configured when the VPS was created |
Provider, server and administration-panel credentials may be three different sets. Your provider-account email is not automatically an SSH username.
An Ubuntu image does not guarantee the username is ubuntu. Images and setup methods differ; follow this instance's instructions. If only a key was configured, guessing passwords will not usually let you log in.
Search the Start menu for PowerShell, open it and run:
ssh -V
A version beginning with OpenSSH means you can continue. This checks the local client; it has not connected to the server.
If Windows says ssh is not recognized as a command or cmdlet, search Settings for Optional features, open the add-feature interface and install OpenSSH Client. Close and reopen PowerShell, then check again.
Recent Windows 10 releases and Windows 11 support this component, but check whether it is actually installed; see Microsoft's OpenSSH guide. Ordinary SSH connections do not require an administrator PowerShell session. Installing an OS component may require administrator approval.
You need the client to connect outward. OpenSSH Server allows other devices to connect to this Windows computer and is not needed for this task.
203.0.113.10 below is a documentation address, not a server you can use. With the example username root and port 22:
ssh -p 22 [email protected]
Before running it, replace all three values:
22with the actual SSH port.rootwith the server OS username.203.0.113.10with your VPS's public IP.
-p is lowercase and followed by a space; @ separates username and IP. Do not turn the command into a web URL or use the web-panel port. See Microsoft's SSH examples and the OpenSSH command reference.
On first connection, SSH may show a server fingerprint and ask Are you sure you want to continue connecting.
Compare it with the provider's trusted console, the administrator's information or an existing verified record. Only after a match, type the complete yes and press Enter. If you cannot verify it, ask the provider for the host fingerprint.
This step verifies the server, not successful account login. If a previously used machine suddenly shows a changed identity, investigate a reinstall or IP change before removing records. See OpenSSH host-identity verification.
At password:, enter that server user's password and press Enter.
A password prompt normally shows no characters, not even asterisks. Do not paste repeatedly because the screen appears unchanged. If you make a mistake, Ctrl+C cancels the connection so you can start again. Check capitalization and accidental spaces.
If the server allows only keys, use the private key corresponding to its setup. A .pub public-key file alone is insufficient, and changing the provider-account password will not help. Continue with the SSH key login guide if needed, following the server's existing authentication policy.
After login, the terminal normally shows the server's login information and a new prompt. Run whoami to identify the remote user and pwd to see the current directory. Both are read-only.
These commands now run on the VPS. Enter exit to return to the local PowerShell prompt.
If the server requires an initial password change, follow its prompts and store the new password safely. Current and new passwords may both be hidden while typing.
Download from the official PuTTY page. A typical 64-bit Intel or AMD Windows computer uses the x86 64-bit build; choose the appropriate build for Windows on Arm.
For a server permitting password authentication:
- Enter the public IP in Host Name (or IP address).
- Enter the SSH port in Port, for example
22. - Select SSH as the connection type.
- Click Open, verify the first host fingerprint and accept only a match.
- At
login as:, enter the server username and then its password.
PuTTY password input normally remains invisible too. Use whoami and pwd for the same read-only checks, and exit to exit. See the PuTTY getting-started manual.
For key authentication, configure the matching private key in PuTTY as well. Address and port alone cannot replace that authentication. If PowerShell already works, you can continue using it without adding another client.
| Message | Check first |
|---|---|
ssh command missing | OpenSSH Client installation and reopening the terminal |
Connection timed out | VPS state, IP, port, security group, firewall and current network access |
Connection refused | Whether SSH actually listens at the destination; confirm the port and service |
Permission denied | Matching username, password or key, and permitted authentication method |
Permission denied (publickey) | Whether a key is required and the selected user and private key are correct |
Host key verification failed or a changed-identity warning | Server identity and expected reinstall or IP changes before editing saved keys |
A timeout normally happens before password verification, so repeatedly changing passwords is not useful. Authentication failure does not imply a reinstall is necessary; check the user and method first.
If it still fails, record the exact error, time and attempted steps. Use the SSH troubleshooting guide or open a support ticket without including passwords or private keys.
No. Windows can manage Linux over SSH. Choose the server OS according to the software you need; see Windows versus Linux VPSs.
No. A browser opens a web service; SSH opens a server terminal. Their ports, accounts and purposes differ. A missing website does not necessarily prevent an SSH connection.
For your first session, get the details right, verify identity, log in, perform a read-only check and exit. Once access is reliable, proceed with the application's deployment instructions.