SSH "Permission denied" or "allows sftp connections only

Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Good to know
  5. Still not working?

Every hosting account can use SFTP (file transfer) with its control panel username and password. A command line over SSH is only available when the plan includes shell access. Keys are managed on the SSH Access page.

Symptoms

  • Permission denied (publickey,password).
  • This service allows sftp connections only. and the connection closes.
  • Connection timed out or Connection refused.
  • Your key is refused although you added it to ~/.ssh/authorized_keys yourself.

Causes

Most likely first:

  1. Wrong username or password — the username is the control panel username; the password is the control panel password.
  2. Your plan has no shell access — SFTP only.
  3. The key is not added on the SSH Access page, or your SSH program offers another key.
  4. Your address was banned after several failed attempts.
  5. The account is suspended.
  6. Administrators: root may sign in with keys only.

Fix

Settings to use

Open SSH Access (section Files). Under Connection you see the Server, Port (22), Username and Access: "SSH terminal and SFTP", or "SFTP (file transfer) only — your plan has no terminal access".

ssh [email protected]
sftp [email protected]

1. Username and password

Use the account username (lowercase), not the domain or an email address. The password is the control panel password; after changing it in Password & Language, use the new one. Team member logins cannot be used for SSH or SFTP.

2. SFTP only

This service allows sftp connections only. means your plan has no shell access. Use an SFTP program (FileZilla, WinSCP, Cyberduck) or sftp, or ask your host for a plan with shell access. With shell access, the Terminal page also opens a command line in the browser.

3. Keys

  1. On SSH Access, under Add a public key, enter a Name, paste the Public key (the content of ~/.ssh/id_ed25519.pub on your computer) and click Add key.
  2. Connect with the matching private key, for example ssh -i ~/.ssh/id_ed25519 [email protected].

Supported: ed25519, RSA of 2048 bits or more, and ECDSA. The panel writes ~/.ssh/authorized_keys from this list: keys you add to the file by hand are replaced. Run ssh -v … to see which keys your program offers.

4. Banned after failed attempts

After 6 failed sign-ins within 10 minutes, the address is banned from SSH for an hour, and connections time out. Wait, or ask your host to lift the ban. See My IP is blocked.

5. Suspended account

A suspended account cannot sign in to SSH or SFTP; see the suspension notice from your host.

6. Root on the server (administrators)

If Fix it was used for SSH root logins in the Security Advisor, root signs in with keys only and root's password is refused over SSH by design. Sign in as root with your key, or use your provider's console.

Good to know

  • Your SSH sessions see only your own files and processes, and count towards your account's limits.
  • In SFTP you start in your home folder; the usual /home/username/… paths work.

Still not working?

If the connection times out from every network, ask your host whether SSH uses another port on this server. Send them the output of ssh -v [email protected].

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.