Troubleshooting

Connecting

Message	What it means, and what to do
… did not respond (timed out)	Nothing answered at that address and port. Check the host name and port, that the server is on, and that your network (or a firewall) lets you reach it.
cannot connect to …	The server could not be reached; the reason follows (for example "connection refused": nothing listens on that port; check the port and the protocol).
login failed: wrong user name, key or password	The server refused who you said you are. Check the user name (it is case-sensitive) and the password; on some servers the account must also be allowed to use SSH or FTP.
the server did not accept the SSH key	Your key is not on the server's list for that account, or the wrong key was offered. Enter the password instead, or ask for your public key to be added.
the key file … needs its passphrase	The private key is protected; enter its passphrase when asked.
WARNING: the host key of … has changed	See Host keys. Do not ignore it: ask the server's administrator first.
the server's certificate is not trusted	An FTPS server's certificate could not be checked. If its fingerprint is the one your host gives, trust it.
the server does not offer TLS encryption	The FTP server cannot encrypt. Only if you accept plain FTP (see FTP and FTPS), choose the encryption the message names.
the server's file transfer (SFTP) service failed	SSH works, but the server does not offer SFTP for this account. Ask the administrator, or try FTP if it has it.

Copying

Message	What it means, and what to do
Permission denied	The server does not let your account read that file or write in that folder. Pick another folder, or ask for access.
no such file or folder	It was moved or deleted since the list was shown. Click Refresh.
… is already in …, or cannot go inside itself	A file or folder was dropped where it already is, or a folder into one of its own folders.
the copy's checksum differs from the original's	The copy is not identical (see Checking copies). Retry the transfer; if it keeps happening, the disk or the server may have a problem.
not verified	The copy is complete, but could not be checked; its tooltip says why (often: the server cannot compute checksums).
Not started: "…" is using the same files	Another unfinished transfer writes the same files. Retry once it has finished.

Slow servers

Folders open quickly even while files are copied: transfers use a second connection of their own.
A slow server can make checking copies slow too, when they are read back: choose Server checksums only under the site's Advanced.
Some servers allow only a few connections at once: lower Files at once for that site.

The log

ShuttleSCP writes what it does to a log file: Tools › Open Log File opens it. For more detail, raise Tools › Log Level, try again, and look at the newest lines. The log never contains your passwords.

If something looks wrong in ShuttleSCP itself, please report it on GitHub, with the version (Help › About) and the lines from the log around the problem.