Fixing "Permission denied" when connecting via SSH/SFTP

If you try to connect to your site over SSH or SFTP and see an error like Permission denied (publickey,password), it almost always means the password on your SSH user is out of date — not a problem with the server or your account. This commonly happens after a site is first set up or rebuilt. The fix takes a few seconds.

Quick checklist

• Your username is case-sensitive and has no typos — copy it exactly as shown in your control panel.
• Password login is enabled for your site's SSH user, so you do not need to set up an SSH key to get in (you can add one later if you prefer).
• The password just needs to be current — generate a fresh one and use that.

Generate a new SSH/SFTP password

1. Log in to your control panel and open the SSH/FTP section for your site.
2. Under SSH User, click Generate new password.
3. Copy the new password (save it somewhere safe — treat it like any other credential).

You'll find Generate new password directly under the SSH User heading, next to the password field.

Connect with the new password

Run your usual command and enter the new password when prompted:

ssh [siteuser]@yoursite-com.transpark.tech

You should connect right away and be able to deploy.

Still stuck?

Double-check you're using the exact username and the newly generated password (old saved passwords won't work after regenerating). If it still fails, reply to your support ticket and we'll take a look — your access is never blocked for a simple login error.

Prefer key-based login?

You can set up a passwordless SSH key instead — see SSH access and terminal commands.