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

WayneF

Same here, the problem has been random, in an off and on fashion. I tried logging too, but no issue in last couple of days.
Wayne
cannonball

Wouldn't you know it, but it appears now to work normally with no Lost Connections.

In response to your instructions, I enabled normal logging, ran the copy from local to server, and it went through completely with no Lost Connections. Then I turned off logging, and did the operation again, and again all normal. I don't know how or why it didn't work yesterday and does work today.

I will keep your instructions on logging and if it ever recurs, will post again to WinSCP support with the log. Thanks.
martin

Re: Lost Connection - Timeout detected

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.
cannonball

Hello WayneF - WinSCP 6.1.2

As indicated in the initial post, I was using an older version of WinSCP, and then after these errors, I upgraded to the latest WinSCP 6.1.2. Same error with either version.
WayneF

Re: Lost Connection - Timeout detected

I am having a similar problem, but only in the last week. One afternoon FTP went from working perfectly to a numerous time out problem. Sometimes the file was transferred OK, sometimes not. It seems to have improved a bit, but there is still frequent timeouts. Sometimes it timesout and reconnects within a few seconds of logging in, with zero other action after starting WinSCP.

I asked my host server people about it, and they looked in the log and said this: "Starting at timestamp 17:56:22, the previously-successful logins went to a series of timeout errors. This implies that your FTP client is successfully logging in, then the server doesn't receive a followup packet from your FTP client before the timeout limit is reached. Which FTP client are you using?"

I am using WinSCP 6.1..2, and am wondering if it made some timeout change recently?
cannonball

Too many connections

Here is the error window after 10 reconnect attempts. Will not allow a reconnect till the next day.
cannonball

Lost Connection - Timeout detected

Running WinSCP. Have problem with copying files to remote server. I had an older version which has the problem, so I upgraded to 6.1.2 and still have same problem.
I have a website and am trying to copy a directory of approx. 500 files to it. I use WinSCP, connect to the server, and drag and drop from left to right. The copying starts, but then after some number of files get copied (between 5 and 20), the connection fails saying "Lost Connection - Timeout detected." So I hit the reconnect button. It reconnects and again the same scenario...some files get copied, and then disconnects. Then, after 10 reconnects, I get a window saying "Disconnected from server. Connection failed. Too many connections (10) from this IP." And it will then not allow a reconnect till the next day.
Is this a problem with my system? Or the internet? Or the server? How to tell? ... and how to fix? Note: I have not problem with the browser getting to this website, and any other website.