Skippr Docs

Appearance

How to Fix SFTP "authentication failed" in Skippr ​

April 2026

SFTP authentication failures usually come down to the username, password, private key path, or host access rules.

Short Answer ​

SFTP authentication failed usually means the username, password, or private key path does not match what the server expects. Host-based access rules can also block a valid login.

Check the auth method first, then verify the exact key path or password being used by Skippr.

Why This Error Happens ​

SFTP auth failures are usually plain transport setup problems. The source is reachable, but the server does not accept the credentials or key material you sent.

  • Wrong SFTP username or password.
  • Wrong private key path or unreadable key file.
  • Using the wrong auth method for the server.
  • Host-based access controls that block the machine running Skippr.

How to Fix It with Skippr ​

Validate the same credentials with an SFTP client first. If key-based auth is expected, double-check the private key path and file permissions before reconnecting the source.

  • Confirm whether the server expects password auth or private-key auth.
  • Verify the username and password or private key path.
  • Make sure the key file is readable by the user running Skippr.
  • Check host-based access controls on the SFTP server.
  • Reconnect the SFTP source and retry the run.

When Skippr Is the Better Path ​

Once the transport auth is correct, the rest of the workflow stays simple. Skippr can keep file ingestion and warehouse delivery in the same project.

That is easier to follow than fixing SFTP auth in one script and rebuilding the warehouse path in another.