How to Fix SFTP "file not found" in Skippr

April 2026

SFTP file-not-found errors usually mean the login worked but the remote path did not point where you thought it did.

Short Answer

An SFTP file not found error usually means the connection succeeded but the remote path does not resolve to the file you expected. This is often a path question, not an auth question.

The most useful check is whether the path is relative to the user's home directory, absolute from the server root, or transformed by the server's chroot configuration.

Why This Error Happens

SFTP servers often hide part of the filesystem behind a user root. That makes a perfectly reasonable-looking path fail because it is being interpreted in a different directory context.

• The configured path is relative when the server expects an absolute path, or vice versa.
• The user lands in a chrooted home directory and the path was copied from a different context.
• The file naming pattern or date partition does not match the actual remote file.

How to Fix It with Skippr

List the remote directory with the same user first, then copy the path exactly as the server exposes it to that login. That removes most of the guesswork.

• Verify the remote directory structure with the same SFTP user Skippr is using.
• Confirm whether the connector path should be absolute or relative to the login root.
• Check the exact file name or partition pattern expected by the pipeline.
• Reconnect the SFTP source and rerun the pipeline.

When Skippr Is the Better Path

Skippr makes this kind of issue easier to isolate because the source contract is explicit. Once the remote path is right, the same project can continue into landing and model bootstrap without extra glue.

That keeps a path typo from becoming a multi-tool incident.