Repository navigation
Troubleshooting
Check the protocol and port first. SFTP normally uses port 22. Explicit FTPS normally uses port 21. Implicit FTPS normally uses port 990.
For command-line use, exit code 3 means that TideFTP could not connect. Check DNS, the firewall, the port, and the SFTP host key. An unknown SFTP host key also produces exit code 3.
Add the host to ~/.ssh/known_hosts with OpenSSH:
ssh user@files.example.comConfirm the displayed fingerprint through a trusted channel before accepting it. You can also use --known-hosts FILE to select another host-key file.
Exit code 4 means that the server rejected the credentials.
- For SFTP, check the SSH agent, key permissions,
--identity,TIDEFTP_SFTP_PASSWORD, and the saved keyring entry. - For FTP or FTPS, check
TIDEFTP_FTP_PASSWORD,--password-stdin, or the saved keyring entry. - Enter the username exactly as the server requires it. Some hosting systems require a full email-style username.
Use --ftps-ca FILE to trust the server's private certificate authority. Do not use --ftps-insecure for a production connection.
If uploads larger than 16 KB fail or arrive corrupted, keep the default TLS 1.2 limit. Remove --ftps-allow-tls13 if you enabled it.
TideFTP does not overwrite an existing destination by default. In the app, choose a conflict action when prompted or set a conflict policy. On the command line, pass --force only when replacement is intended.
sync deletes only when you pass --delete, all copies succeed, and the source contains at least one entry. If an empty source is intentional, add --allow-empty-source after checking the paths with --dry-run.
Wait for automatic reconnect. Resolve the recovery panel when the connection returns. TideFTP resumes a small partial file only after matching it against the source. Retry other items from the Failed tab with R.
For command-line transfers, set --retries N. Add -c to get or put, or add --resume to sync, to continue a partial file left by an earlier run.
TideFTP starts with defaults but disables saving when config.toml contains invalid TOML. This prevents the app from replacing profiles in the damaged file. Fix or restore the file, then restart TideFTP.
Include the TideFTP version, protocol, operating system, exact error, and steps that reproduce the problem. Remove hostnames, usernames, and credentials. Open an issue in the TideFTP repository.
This page describes source revision b1fb600.