How to get SSH access and connect

Request SSH access

SSH is switched off by default on shared hosting accounts. Request it through Support › Open Ticket at portal.webway.host, or by emailing support@webway.host.

Include:

• The hosting service or domain
• Why you need SSH
• Your public IP address
• Whether you intend to use command-line SSH, SFTP or both

Webway will confirm whether SSH can be enabled and give you the hostname, port and username to use.

Create an SSH key

On macOS, Linux or Windows (PowerShell), run:

ssh-keygen -t ed25519 -C "your-email@example.co.za"

Choose a secure passphrase when prompted. This creates a private key, which must stay secret, and a public key ending in .pub, which can be shared.

Never send the private key to Webway or anyone else.

Display the public key with:

cat ~/.ssh/id_ed25519.pub

Copy the complete line when Webway asks for it.

Connect to the server

Use the details supplied by Webway:

ssh -p PORT USERNAME@SERVER-HOSTNAME

Replace PORT, USERNAME and SERVER-HOSTNAME with the details you were given. Don't assume the port is 22.

If your key is stored somewhere else:

ssh -i /path/to/private-key -p PORT USERNAME@SERVER-HOSTNAME

Use SFTP

SFTP uses the same SSH service and credentials. In an SFTP client such as FileZilla, choose SFTP as the protocol and enter the hostname, port and username supplied, with your SSH key. SFTP is not the same as FTP over TLS.

Shared-hosting restrictions

SSH access doesn't give you root access, sudo, permission to install system packages or change server-wide settings, or support for permanent background processes.

If the connection fails

Check that:

• Webway confirmed SSH was enabled.
• The hostname, port and username are correct.
• The correct private key is selected.
• Your public key was supplied completely.
• Your key file is readable only by your user.
• Your network allows the port.

Repeated failed logins can cause the server firewall to block your public IP. Customers can't view or remove firewall blocks. See My website works for others but not for me.

Still stuck?

Open a support ticket and include:

• Your hosting service or domain
• Your public IP address
• The hostname and port used
• Your SSH username
• The exact error message
• The date and time of the attempt
• Whether SFTP fails as well

Never include your private key or password.