Troubleshooting

Start with the operation that failed and the exact error message, then find the message below.

On this page

I cannot connect

Compare the connection form with the details from your provider. Check the protocol as well as the address and port. If the server requires a VPN or access from an approved network, connect from that network first.

Message or symptom What to check next
Server not found Recheck the hostname for typing errors and confirm it with the provider.
Connection refused Check the protocol and port. Ask whether the file transfer service is running and allows your connection.
Server is not responding Check your network or VPN and the server's availability. A timeout alone does not identify which side is at fault.
Incorrect username or password Check the account and authentication method. For SFTP, confirm whether the account requires a key.
Invalid WebDAV address Use the full HTTP or HTTPS URL supplied by the provider, including its folder path.

For form instructions, see Connect to a server. For key files, passphrases and SSH errors, see SFTP troubleshooting. For TLS errors, see FTPS troubleshooting. For WebDAV URLs, HTTP sign-in and authentication methods, see WebDAV troubleshooting. If FTP or FTPS signs in but does not list files, check the data-connection mode.

The server identity is not trusted

A certificate error or changed SSH host key is a reason to verify the server's identity with its administrator. Ask whether the server was replaced or its certificate or key was changed, and get the expected certificate or key from them some other way than this connection, such as by phone or from their website. Do not disable verification just to dismiss the message.

FTPeach refuses a changed SSH host key. For a first connection, follow Connecting safely before accepting the key.

My transfer did not finish

Find the file's row in Transfers and read the error. Then check the relevant condition before retrying:

Problem Next action
Connection lost Reconnect the pane to the same server and account, then use Retry.
Permission denied Confirm the destination folder and ask the administrator whether this account may write or replace files there.
Not enough free space Check free space or quota at the destination. A server administrator may need to check a remote quota.
Source changed during upload Finish saving the source file, then upload it again.
File open in another program Close the program holding the file and try again.

If Pause is unavailable for a WebDAV upload, this is expected: that upload cannot continue a partly sent file. A stopped upload starts over when retried. See pause and resume behavior before deciding to stop a large job.

I cannot move files to the other server

Move works within your computer or one server connection. To transfer files between your computer and a server, or between two servers, use Copy instead. Verify the destination before deciding whether to delete the originals.

My edit is not on the server

Saving in the editor changes the edit copy on your computer. Check that you approved its upload in FTPeach and that the upload succeeded. If the app closed before you finished, look at the recovered edits it offers on startup. Follow Editing remote files to finish the work.

Saved passwords do not work on a new computer

Check how the passwords were moved. A portable copy without a master password keeps passwords tied to the original computer. For a separate installation, use export and import with saved passwords. If an import was done without passwords, you will need the server credentials or the password-protected export. Windows Hello must be enabled on the new computer separately.

I cannot unlock saved passwords

Check whether the prompt wants the FTPeach master password, a server password or an export file password. If Windows Hello fails, try the master password. For a forgotten password, read recovery and reset before deleting anything: resetting the vault loses its stored secrets.

Ask for help

Open View > Log to show the log panel. To find your FTPeach version, open Help > About and note the version beside the application name.

The Log panel filtered to a Permission denied error.The Log panel filtered to a Permission denied error.

Use the log's search field to find the relevant message. This example filters for "Permission denied".

Use Copy log to clipboard or Save log to file in the log toolbar to collect the relevant lines. Check the copied or saved text before sharing it; the privacy precautions below apply to logs and screenshots too.

For account details, permissions, quota or server identity, contact your server administrator or hosting provider. If the problem appears to be in FTPeach, report an issue with:

  • Your FTPeach version and Windows version.
  • The protocol and operation, such as uploading a folder over SFTP.
  • The steps to reproduce it, the expected result and the exact error text.
  • Whether it happens every time, and whether a small test file behaves the same.

Remove passwords, private keys and private server or file details from anything you share. Never attach a vault, a settings export containing secrets, or a private key to a public issue. Report security vulnerabilities through the security policy.

Read this page on GitHub

Swipe to explore the enlarged image.