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: FTPS - Certificate not trusted

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.

FTPS - Certificate not trusted


We have replaced the certificate of our FTP server to one which is signed by a public CA (previously it was signed by our own CA). Since then WinSCP moans that it does not trust the certificate any longer. While trying to track down the problem, we found that the point here is, that the client where WinSCP is running is disconnected from the internet. The difference with regards to our old certificate seems to be that the new certificate has a OSCP entry.

We also tried other FTP clients which also work if disconnected from the internet. However all clients seems to rely on the Windows certificate store, so there must be something different in the way this is handle within the application.

Is there any way to make WinSCP also work in disconnected environments with FTPS.

Thanks and best regards