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


New Message with Development version of WinSCP

I'm now getting a different "message" than before with the development version of WinSCP that you supplied:

. 2020-04-20 17:34:45.607 Copying finished: Transferred: 257,814, Elapsed: 0:00:00, CPS: 7,032,687/s

> 2020-04-20 17:34:45.607 Script: close
. 2020-04-20 17:34:45.607 Closing connection.
. 2020-04-20 17:34:45.607 Sending special code: 1
. 2020-04-20 17:34:45.623 Main session channel closed
. 2020-04-20 17:34:45.623 All channels closed

The "Special Code" still triggers my system to think something is wrong, and that the upload did not proceed as expected. I've attached another private copy of the log file for your review.

What's next?

Re: "Remote side unexpectedly closed network connection"

Thanks for the response. The link I received was to download what I believe is a "debug" version of WingFTP...and not WinSCP. Is that what you intended to send me?

Re: Remote side unexpectedly closed network connection

Thanks for your report.
I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.

Remote side unexpectedly closed network connection

I'm having the same type of issue as was described in this post, right down to the version of WinSCP that I started encountering the error with which persists today into the latest version:

I unfortunately, don't have the luxury of downgrading WinSCP however to address the issue, and am wondering if a solution was found, which didn't get added to the post above, because I see no updates to the article since 2020-03-27.

I've attached a WinSCP Log File that I generated (set to private), which includes the error described in the subject of this post. In my environment, we are using the latest version of WinSCP (v5.17.3 build 10325) to connect to the latest version of WingFTP Server (6.2.9) =>

For your awareness, I've also opened a "case" with the vendor for WingFTP Server to report this issue, which you may be able to reference here for additional information:

Let me know what other information you might benefit from having!