Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: Cannot Store Fingerprint

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Cannot Store Fingerprint


I configured WinSCP to connect to a local S3 bucket.
The local server does not have a valid certificate and so this message comes up.

The server's certificate is not known. You have no guarantee that the server is the computer you think it is.
Server's certificate details [...]
Fingerprint (SHA-1): 12:34:56...
Summary: Certificate was not issued for this server. You might be connecting to a server that is pretending to be "someone".
If you trust this certificate, press Yes. To connect without storing certificate, press No. To abandon the connection press Cancel.

I press yes and the message comes up again. It comes up on each remote operation at least once.

What can I do to prevent WinSCP from showing this message?