Articles on: Develop
This article is also available in:

How do I connect to my Faaaster site with SSH or SFTP?

The site's Access tab, SSH / SFTP section, shows your connection credentials directly: the Host and your SSH Login, each with a copy button, then the Password row. This is the information to use in your SSH or SFTP client.


Prerequisite — to authenticate, you need either a public SSH key in your profile (your avatar menu, top right → My profile, Public SSH Key section) or an SFTP password generated by Faaaster (see below).


Get your access details


  1. Open the site, Access tab.
  2. In the SSH / SFTP section, copy the Host and the SSH Login with their copy buttons.


The SSH / SFTP section of the Access tab: the Host and the SSH Login, each with its copy button.

  1. Enter the information in your client (Terminal, FileZilla, Cyberduck…).


The Access tab: the VS Code extension (1) and the Adminer SQL client (2), next to the SSH/SFTP access.


Add your SSH key


In your Profile:


  • Generate SSH Key — Faaaster creates a key pair and downloads the private key for you;
  • Set custom SSH Key — you paste your own public key.


The interface explains that this key lets you "easily connect to all your sites through SSH or SFTP": it applies to all of your sites, not just one.


Use an SFTP password


If your client doesn't handle keys, or if you'd rather use a password:


  1. In the site's Access tab, Password row, click Generate a password. You can also do it from your Profile, SFTP password section.
  2. If your account is protected by two-factor authentication, confirm your Faaaster password (or your GitHub identity), then the code from your app.
  3. Save the password shown right away, in your password manager or your SFTP client. From the Access tab, the site's host and login are shown with it.
  4. Tick I have saved this password somewhere safe, then click Done: the window doesn't close before that.


⚠️ The password is only shown once. Faaaster doesn't keep it in clear text and can't give it back to you. Lost it? Click Regenerate: a new password replaces the old one.


This password is the same for all your sites and comes in addition to your SSH key, which keeps working. To go back to the key only, click Remove in the SFTP password section of your profile.


Connection settings


Field

Value

Host

ssh.faaaster.cloud

Login

The SSH Login shown in the Access tab, in the form xxxxxxxx__inst12345: copy it in full

Port

No site-specific port: keep the default SSH port (22)

Authentication

Your SSH key or your SFTP password


If the SSH Login shows "—", your access isn't ready yet: generate a password or save your SSH key in your profile, then come back to the Access tab.


Using a login in the old xxxxxxxx@inst12345-0 form? It is still accepted: nothing to change in a client you've already set up.


From the command line, connecting takes a single line:


ssh [email protected]


With a key that isn't the default one on your computer — for example the private key downloaded from Faaaster —, add -i path/to/key. Without a key, the terminal asks for the password.


For SFTP, enter the same host and the same login in FileZilla, Cyberduck or Transmit, with the default port, then your key or your SFTP password.


An SSH key loaded on your computer comes before the password. If your client knows your key (SSH agent, key set in its settings), it tries it first: the connection then succeeds with the key, without using the password.


To test the password alone, without the key:


sftp -o PubkeyAuthentication=no [email protected]


The host is the same for all your sites. It's the login that changes from one site to the next: its inst… part identifies the site.


"The server's identity has changed": what to do


If your client shows a warning that the key (or fingerprint) of ssh.faaaster.cloud has changed, this is expected: we upgraded our SSH server. It only affects computers that had already connected before; a first-time connection triggers nothing, and your SSH key and login stay the same.


  • Graphical client (FileZilla, Cyberduck, Transmit…): a dialog offers to accept the new key. Click Yes / Trust / OK — that's all.
  • Terminal / command line: the connection is blocked by a WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! message. Forget the old key, then reconnect:


ssh-keygen -R ssh.faaaster.cloud


On reconnecting, answer yes to save the new key.


To check you are accepting our server, its official fingerprint is SHA256:DnMk0PJasNBrmTaA20hbEisr8z0iC1tU0vlzRZNZC+M.


👉 How do I use WP-CLI? · How do I work from VS Code?

Updated on: 11/09/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!