Troubleshooting

“The server’s key has changed”

BlazeSCP refuses to connect when a known server presents a different host key. This can mean someone is intercepting the connection, but usually means the server was reinstalled or its keys were rotated. Check with the server’s owner, then delete the line the warning names from known_hosts and connect again.

“The server rejected the credentials”

Check the username: SFTP uses your system account, not your email address.
For key authentication, make sure the server has your public key in ~/.ssh/authorized_keys and you selected the matching private key.
If you use a two-factor code, BlazeSCP asks for it after the password. A wrong code shows The server didn’t accept that answer; click Try Again for a fresh prompt.

“Requires FTP with TLS”

The server doesn’t allow unencrypted logins. Edit the server and change the protocol to FTP with TLS.

FTP listings hang or fail

The server’s passive mode may be blocked by a firewall. If you can’t fix that on the server, try Active mode in the server settings (it needs your computer to accept incoming connections, so it often fails behind a home router).

No PQC tag on an SFTP server

The server runs an OpenSSH older than 8.5, or post-quantum key exchange is turned off in its configuration. The connection is still encrypted with classical SSH. See Post-quantum SSH.

Verification only checks the size

SHA-256 verification needs both sides to compute hashes. Many hosting accounts are SFTP-only, with no shell, and FTP, WebDAV and S3 can’t hash files on the server, so for those only the size is compared.

A transfer says “interrupted”

BlazeSCP was closed or updated while the job was running. Connect to the server and press resume on the job: it continues where it stopped.

Linux: no saved passwords

BlazeSCP stores passwords through the Secret Service. Make sure GNOME Keyring or KWallet is running and unlocked; on minimal desktops, install gnome-keyring.