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

Guest

Re: Getting error "Host is not communicating for more than 15 seconds. Still Waiting..."

Hi Martin, thanks for the reply. As mentioned by you previously, please find the attached log.
Note: This log was generated when the user tried to login with the 6.5.1 version and faced the connection issue. We couldn't fetch the logs for successful connection as this issue is experienced by our business user-clients with higher versions, and they have either using older WinSCP versions or have switched to FileZilla.
martin

Re: Getting error "Host is not communicating for more than 15 seconds. Still Waiting..."

Please attach a full session log file showing the problem (using the latest version of WinSCP) and well as log from the previous version of WinSCP that still works with your server.

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

Getting error "Host is not communicating for more than 15 seconds. Still Waiting..."

We are unable to connect to SFTP server available in our application, since the time WinSCP tool got updated to 6.5.1 version.

Error message:
Host is not communicating for more than 15 seconds. Still Waiting...

Moreover, the connection is not closed in this case. Instead, it tries to reconnect and it completely queues up the user-connection requests, due to which all threads/sessions gets exhausted and it ultimately prevents all the users from connecting to that SFTP server.

However, we are able to successfully connect to the same SFTP hostname using FileZilla tool.

Way to reproduce:

  1. Open a WinSCP session and try login to SFTP hostname.
  2. The session runs into a timeout.
  3. WinSCP unsuccessfully attempts to auto-connect to the hostname despite of timeout error.

Our expectation:

  1. To be able to connect to SFTP server of our application through upcoming version of WinSCP, without timeout or any other error.
  2. In case of Timeout error, the session should be automatically closed and WinSCP shouldn't retry to connect to that hostname.

Version in which this issue is seen: 6.5.1

Please find attached the snapshot of the error attached to this ticket.

Documentation

Support

Associations

Follow Us