• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue sftp backup extension - delete known_hosts?

Martin_Sauer

Regular Pleskian
Server operating system version
Red Hat Enterprise Linux release 8.7 (Ootpa)
Plesk version and microupdate number
Plesk Obsidian Version 18.0.51.1
Plesk Obsidian Version 18.0.51.1
OS Red Hat Enterprise Linux release 8.7 (Ootpa)
Extension SFTP backup Storage Extension

Since the switch to a new backup-Server the sftp-backup no longer works:
Transport error: Extension transport: ext://sftp-backup/server/: Failed to list the directory "" at host.domain.TLD: unable to make SSH connection: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

Presumably ssh does not work due to the known_hosts entry. Because the server fingerprint changed with the switch to the new server.

Where can I delete the current known hosts for the sftp-backup account?
 
Yes I can.

Keep in mind, it is pubkey exchange. And all that changed is the remote sftp-Storage-server, so a new host-key. Everything else is the same.
 
If a key does not match when doing SSH connections, the system prompts you to accept a new key. If you SSH or sftp to the target as @GwenDragon said and the key does not match, you should have seen such a prompt. Have you?
 
If a key does not match when doing SSH connections, the system prompts you to accept a new key. If you SSH or sftp to the target as @GwenDragon said and the key does not match, you should have seen such a prompt. Have you?
It is the sftp storage for backup.

The only thing that changed is the host key of the target server, which hosts the sftp storage. But: all that is automatic.

So my assumption is: there is a known_hosts file, which has the old server key.Which account, where is the file? So I can delete the old known_hosts key.
 
Additionally clicking "Backup" in Tools&Settings now takes forever to load.

Once it loads, screen fills with yellow warnings
1682588132660.png
 
Error message on once again confirmation of ssh-storage:

Error: Failed to create the directory "/../../../storage" at sftpstorage.foo.bar: unable to make SSH connection: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain

And yes:
1. ssh key is entered correctly
2. yes verified complete ssh key on both sides
3. yes it worked before, exactly this way
4. yes the only thing changed is newly installed sftp-server. Yet userID, groupID, directories are all the same.

MY conclusion: there is a "known_hosts" entry in a file or database for the sftp account, which still lists the old server fingerprint. How/where do I delete that?
 
The SSH known_hosts is located in /root/.ssh/known_hosts. I am not aware of a specific sftp known_hosts file.
 
Back
Top