Post a reply

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


OK, case closed. I leaned two things today:

1. I had to use "ftpes://..." and not "ftp://..." to define the protocol as I had been doing. Something my Host failed to inform me about, and I only discovered it when trying out the "Session/Generate session Url" from the WinSCP GUI. I had tried "ftps://..." but that failed. I would never have guessed in a million years that it should be "ftpes".


2. If the Certificate is unauthorised then I have to use the "-certificate" parameter on the "open" command, not the "/certificate" parm.

TLS is kicking in and it's all working nicely now. Thanks for looking.


FTPS upload works but log says it used standard FTP

I have finally got my first WinSCP script to work using the FTPS protocol. The upload to my website works fine but the log appears to be telling me that standard FTP was used for the transfer:
. 2020-08-29 16:05:21.752 FTPS: None [Client certificate: No]

. 2020-08-29 16:05:21.752 FTP: Passive: Yes [Force IP: Auto]; MLSD: Auto [List all: Auto]; HOST: Auto

Here's my BAT file:
"C:\Program Files (x86)\WinSCP\"/certificate=(certificate) /explicit /ini=nul /script=C:\winscp.txt /log=C:\winscplog.txt

and the script:
open ftp://(username):(pword)@(ftp server)
put (path to local file) public_html/wp-content/uploads/

The Certificate was copied and pasted from its source so it is correct and there are no error messages given. I really need encrypted transfer and my Host does not permit SFTP, so I'd be grateful if some kind person could tell me what I'm doing wrong here.