SSH Troubleshooting

Discover our Public Cloud offer

Shared Hosting for Everyone, imagined by developers, for developers.

Discovering the Public Cloud


Should connection issues arise, you can always use the ssh -v [user]@ssh-[account] command to get more information.

Replace [user] with your SSH user name and ssh-[account] with your SSH hostname.

An IP blockage occurs after some ten failed attempts to connect to the server.

alwaysdata has connection logs that you may exceptionally request a copy of.

Too many authentication failures

This is an SSH key issue, state the corresponding key. If you cannot find it, connect by password and update the $HOME/.ssh/authorized_keys file.


An account’s SSH server might change from time to time. The new fingerprints are shown in Remote access > SSH.

You have to update the known_hosts file, which is possible via the following command:

$ ssh-keygen -R [hostname]

Input/output error

Error linked to operations at our end. Please wait until these are finished, but you can also contact support for more information.

alwaysdata has connection logs that you may exceptionally request a copy of.


Using a number of SSH users may have undesirable side effects: problems accessing some files, when deleting folders, files that no longer belong to anyone if the owner user has been deleted, etc. Account users belong to the same group. You can:

  • user the chmod command with the relevant file’s owner user to grant the necessary permissions to the group,
  • contact support so that they will change the owner of the relevant files using the chown command.