Skip to content
New: Laravel Hosting, Node.js Hosting & GitHub DeploysSee the plans →
Products
Solutions
Developers

Guides

How to use SSH on shared hosting

Get a real terminal on your hosting account, run Composer, npm and WP-CLI, and the two connection details people get wrong.

Introduction

SSH is available on every plan, including the entry tier. It gives you a shell in your site’s own container, along with the command line tools a deploy needs. This guide covers adding your key, connecting, and the tools available once you are connected.

Adding Your SSH Key

In the panel, open your site and go to Advanced, then Developer tools. This screen accepts your public key. It does not display your SSH username, so open a ticket and we will send it to you. The username is a short system name such as yoursite1.

If you do not have an SSH key, you may create one using the following command:

ssh-keygen -t ed25519

Accept the defaults, then paste the contents of ~/.ssh/id_ed25519.pub into the panel. The .pub file is the public half of the key and is safe to share. The other file is the private half and should never leave your machine.

Connecting

SSH uses the standard port 22, so no port flag is needed:

ssh your-username@yourdomain.com

There are two details to check when connecting:

  • The username is the short system name we send you. Your panel login and email address will not work.
  • The hostname only works if your domain resolves directly to us. If Cloudflare proxies your domain, its IP is Cloudflare’s, and Cloudflare does not forward SSH. In that case, connect to the server’s IPv4 address, which is shown on your site’s overview page in the panel, under At a glance.

You will land in your site’s home directory, inside its own container. You can see your own files and processes, and nothing belonging to anyone else.

Available Tools

The PHP version on the command line matches the version your site runs, so a script behaves the same in the shell as it does over the web. Composer, Git, WP-CLI for WordPress sites, rsync, and Node.js with npm on sites using the Node runtime are also available:

composer install --no-dev
wp plugin update --all
git pull
npm ci && npm run build

If you use Laravel, the Laravel guide combines these into a full deploy sequence.

Cron Jobs

Cron jobs are managed in the panel. Changes made with crontab -e from the shell will not persist, so you should set up scheduled tasks in the panel instead.

FTP

For one-off file transfers, FTP accounts are also available under Advanced. However, rsync over SSH does the same job faster and resumes when your connection drops.

Keep reading

Other guides

Start building today

Laravel apps with queues and Horizon, WordPress stores, Node.js servers. One container with SSH, deploys from GitHub and people who answer. One bill a year.

Launch my site