Why Basic PuTTY Usage Is Not Enough
Most users only use 10% of PuTTY's power. But in 2026, relying on basic passwords is dangerous, regardless of your OS.
- RSA is Deprecated: Ubuntu 24.04, Debian 12, and RHEL 9 are dropping old keys. You need ED25519.
- Ports are Closed: You cannot access Proxmox/MySQL ports directly. You need Tunneling.
- Timeouts: Sessions drop during long updates. You need KeepAlives.
This guide turns you from a basic user into a SysAdmin Expert. Compatible with Ubuntu, CentOS, Debian, & AlmaLinux.
Topic 1: The New Standard (ED25519 Keys)
If you see "Server refused our key", it's likely because you are using legacy RSA (ssh-rsa). Let's upgrade to Ed25519 (Faster, Secure, Modern).
- Open PuTTYgen.
- Under "Type of key to generate", select Ed25519 (Do not select RSA).
- Click Generate and move your mouse to create randomness.
- Save the Private Key (.ppk) to your secure folder.
- Copy the "Public key" string from the top box.
Log in to your server and paste the public key. These commands work on Ubuntu, CentOS, and Debian:
mkdir -p ~/.ssh
chmod 700 ~/.ssh
nano ~/.ssh/authorized_keys
# Paste your Public Key here -> Save (Ctrl+O) -> Exit (Ctrl+X)
chmod 600 ~/.ssh/authorized_keys
Your server knows the key, but PuTTY doesn't. You must load the private key file.
- Open PuTTY.
- Go to Connection -> SSH -> Auth -> Credentials.
- Click "Browse" next to 'Private key file for authentication'.
- Select your saved .ppk file.
- Go back to Session, enter IP, and click Save.
Topic 2: The Magic (SSH Tunneling)
The Scenario: You have Proxmox (Port 8006) or MySQL (3306). The firewall blocks these ports (as it should). How do you access them without exposing the server?
The Solution: Local Port Forwarding.
- Open PuTTY and load your session.
- Go to Connection -> SSH -> Tunnels.
- Source Port: Enter
8888 (Your PC port). - Destination: Enter
localhost:8006 (Server's internal port). - Click Add. You should see
L8888 localhost:8006. - Click Open to login. Keep the window open.
Expect a Security Warning
When you open https://localhost:8888 in your browser, you will see a red "Your connection is not private" warning.
This is normal. The Proxmox SSL certificate is for the server's IP, not "localhost". Click Advanced -> Proceed (unsafe) to continue securely.
Topic 3: The Unbreakable Session (KeepAlive)
Hate getting "Network Error: Software caused connection abort"? Fix it permanently.
- Go to Connection panel.
- Seconds between keepalives: Change from
0 to 10. - Check the box: Enable TCP keepalives (SO_KEEPALIVE option).
- Go back to Session ->Save.
Now PuTTY will silently send empty packets to the server, keeping your connection alive even if you go for a coffee break.
Conclusion: Security Matches Value
You don't put a cheap padlock on a bank vault. Similarly, you shouldn't use weak passwords on High-Performance Servers.
Weak Security (RSA)Risk Level: High
- Vulnerable to Attacks
- Ports Exposed to Public
- Unstable Connections
Enterprise SecurityED25519 + Tunnels
- Military-Grade Encryption
- Invisible Hidden Ports
- Rock-Solid Sessions
NVIDIA H100 (Needs ED25519)8x H100 NVLinkRTX 4090 ClusterNVIDIA L40SNVIDIA A100Proxmox / VMware Hosts