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


Re: Let the user know if the local proxy command could not be found

Thanks for your feedback. I'll look into it.

Let the user know if the local proxy command could not be found

It would have saved me some time today if WinSCP could have told me that it could not find plink.exe in my PATH when I tried connect to a site using a proxy. Could WinSCP check that the program being used as the "Local proxy command" exists and warn the user if it does not (either in the GUI or in the logs)?

Currently I just get a log like this if I use a proxy command that doesn't exist:
. 2022-07-25 19:25:49.569 Starting local proxy command: foo.exe -agent -nc
. 2022-07-25 19:25:49.582 We claim version: SSH-2.0-WinSCP_release_5.21
. 2022-07-25 19:25:49.582 Connected to
. 2022-07-25 19:25:49.582 Waiting for the server to continue with the initialization
. 2022-07-25 19:25:49.582 Looking for incoming data
. 2022-07-25 19:25:49.582 Looking for network events
. 2022-07-25 19:25:49.583 Remote side unexpectedly closed network connection
. 2022-07-25 19:25:49.583 Using non-standard protocol or port, tunnel or proxy, will not knock FTP port.
* 2022-07-25 19:25:49.625 (EFatal) Server unexpectedly closed network connection.