Skippr Docs

Appearance

Common SFTP Source Setup Mistakes ​

May 2026

SFTP source setup usually fails because teams verify SSH access in one context but do not translate that access into the exact remote path and auth mode Skippr will use.

Short Answer ​

The most common SFTP source mistakes are using the wrong auth method, pointing remote_path at the wrong directory or glob, and assuming the SSH user can list the same files an interactive shell can. Skippr expects a host, username, and either password or private key path, plus the remote file path or glob that defines what gets downloaded.

Those details matter because SFTP access is path-specific in practice. A private key may be valid, but the configured user still may not have permission to list /data/exports/2026/. A remote path like /data/*.json may also be too narrow if files are partitioned deeper, which creates the familiar symptom of a healthy connection that returns no files.

Why Teams Struggle with This ​

SFTP setups often inherit tribal knowledge from ad hoc file transfers. Skippr needs something more explicit: a specific host and port, a specific auth method, and a remote path that the SSH user can genuinely read in automated runs.

  • Password and private-key auth are both supported, but teams often wire one while assuming the other is active.
  • The configured SSH user must be able to list and read the selected remote path, not just log in.
  • A remote path or glob that worked in a manual shell session may still be wrong for the actual automated directory layout.
  • Port and host assumptions frequently differ between internal bastion-based access and the endpoint Skippr should connect to directly.

How Skippr Handles It ​

Skippr keeps the SFTP connector simple enough that setup reviews can be concrete. You can inspect the exact host, port, username, auth mode, and remote path, then test whether those choices match how the source files are really organized.

The docs also recommend key-based auth for long-lived pipelines and support environment interpolation for passwords when password auth is unavoidable, which keeps long-running SFTP sources less fragile and easier to rotate.

  • Support for password or private-key authentication depending on the source environment.
  • Explicit remote_path configuration for file or glob-based source scope.
  • A connector contract centered on SSH reachability and remote read permissions.
  • Secret handling that supports environment interpolation instead of committed passwords.

What the First Useful Version Looks Like ​

A good first version is one host, one user, and one narrow remote path that you know contains a small set of readable files.

After that, widen the glob only when you have confirmed the SSH user sees the same directory structure during automated runs that you saw in manual testing.