SSH Access

How It Works

SSH (Secure Shell) is a client-server protocol that creates an encrypted session between your computer (the SSH client) and the hosting server (the SSH daemon, commonly OpenSSH). You connect using a username and the server address, then authenticate with either a password or, more securely, an SSH key pair. With key-based authentication, your private key stays on your device while the server stores the matching public key in an authorized keys file, allowing logins without sending a reusable password over the network.

After authentication, SSH provides a terminal session where you can execute commands, edit configuration files, manage processes, and inspect logs. Many hosting environments also enable related tools over SSH, such as SCP and SFTP for file transfers, and port forwarding (tunneling) to securely access internal services like databases or admin panels. Access can be restricted by user permissions, shell type, firewall rules, and server-side policies such as disabling root login or requiring multi-factor authentication.

Why It Matters for Web Hosting

SSH access often separates basic hosting from plans designed for developers and administrators. It affects how you deploy code (Git pulls, CI scripts), manage dependencies (Composer, npm), schedule tasks (cron), and troubleshoot performance or errors (log inspection, process checks). When comparing hosting plans, confirm whether SSH is included, whether key-based auth is supported, what users and directories you can access, and whether you can run the tools your stack requires.

Common Use Cases

• Deploying applications via Git, rsync, or scripted releases
• Managing files and permissions when a control panel is insufficient
• Running framework and dependency tools (Composer, npm, Python venv)
• Troubleshooting by reading logs and monitoring processes (top, ps, journalctl)
• Setting up cron jobs and maintenance scripts
• Securely transferring files using SFTP/SCP and creating SSH tunnels

SSH Access vs SFTP Access

SFTP access focuses on secure file transfer and directory management, usually through a graphical client, while SSH access provides an interactive command-line shell for executing server commands. Both use SSH encryption, but SSH access typically enables broader administration (deployments, package installs, service control) depending on permissions. If you only need uploads and downloads, SFTP may be enough; if you need automation and server-side tooling, SSH is the requirement.