SSH

SSH (Secure Shell) is an encrypted terminal session into a server. On hosting it is used for file work, Git, Composer, WP-CLI, cron, logs, and emergency fixes — a stronger tool than FTP/SFTP alone.

Budget shared plans sometimes disable SSH; VPS environments almost always depend on it as the main admin door. With shell access, one bad command can be expensive, so safe habits matter as much as skill.

A Simple Analogy

If cPanel is the car dashboard, SSH is the key plus the hood latch: deeper access, easier to break things if you are careless. Great when you must look under the hood — not required for every short drive.

Common SSH Tasks

• Config files, permissions, and error logs
• git pull, Node/PHP CLI, WP-CLI, Composer
• Inspect inodes, processes, and disk usage
• Run cron or maintenance scripts
• Tunnels and advanced debugging

Typical Connection Flow

1. Enable SSH in the panel if your plan allows it
2. Gather user, host, and port (22 or custom)
3. Authenticate with a password or, better, an SSH key
4. Example: ssh user@hostname -p 22

On Windows use Windows Terminal, PowerShell, or a client such as PuTTY. Keep private keys offline from git repos.

What to Watch For

• Avoid daily root logins on VPS when a sudo user will do
• Prefer keys; disable password login once keys work; add fail2ban/firewall
• On shared hosting, a wrong rm -rf can wreck the account — check paths twice
• SFTP over SSH beats plain FTP for secrecy in transit
• Restrict SSH by IP when your network allows it

FAQ