Skip to documentation
Interneting.orgDocs
Interneting.orgDocs

Documentation

SFTP problems

Resolve key-file, username and authentication errors in SFTP clients.

Client reaches SSH but authentication fails

If the log says Authenticating with public key followed by Authentication failed, the network connection and SSH host key are already working. Check the Site identity and key pair:

  • Use the exact SFTP username shown by Control.
  • Use Key file authentication, not password login.
  • Select the private id_ed25519 file in the client.
  • Make sure the matching id_ed25519.pub key is the one stored in Control.

On Windows PowerShell, compare the local public-key fingerprint with the fingerprint shown in Control:

ssh-keygen -lf "$env:USERPROFILE\.ssh\id_ed25519.pub" -E sha256

FileZilla cannot see the key

If the file picker is filtered to PPK files, switch it to All files and select id_ed25519. Convert to PPK with PuTTYgen only when your local FileZilla/PuTTY setup requires it.

Control reports access state that needs repair

Open the Site and use Reconcile. Control rechecks its managed SFTP access state and repairs supported drift. Wait for that operation to complete, then reconnect.

If authentication still fails after the username and fingerprint both match, keep the failed client log and review the Site's current Attention/Convergence state before replacing keys unnecessarily.