Forum » Support and Bug Reports »

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.

Options
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)

Options

Topic review

martin

Re: Explicit FTPS with Automation

Please show your code and include a session log file.

To generate log file, set Session.SessionLogPath. 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.
Shaun_Transnet

Explicit FTPS with Automation

Hi

When using the Automation library and trying to connect to an Explicit FTPS server, it looks like the Automation Library is not sending the AUTH TLS command before sending the USERNAME command. Explicit FTPS connection work successfully when using the GUI for both versions tested on.

WinSCP version(automation) - 5.5.6 and 5.6.2(Beta)
Windows OS: Windows 7 / 2008R2
Error: WinSCP.SessionRemoteException: Connection failed. ---> WinSCP.SessionRemoteException: Authentication failed.
Connection failed.
Have to use explicit SSL/TLS before logging on.
--- End of inner exception stack trace ---
at WinSCP.SessionLogReader.Read(LogReadFlags flags)
at WinSCP.SessionElementLogReader.Read(LogReadFlags flags)
at WinSCP.CustomLogReader.WaitForNonEmptyElementAndCreateLogReader(String localName, LogReadFlags flags)
at WinSCP.Session.Open(SessionOptions sessionOptions)

Regards

Documentation

Support

Associations

Follow Us