Did this article resolve your question/issue?



2850 Could not connect to SSHFTP server: The current connection has timeout.

« Go Back


Title2850 Could not connect to SSHFTP server: The current connection has timeout.
URL Name2850-Could-not-connect-to-SSHFTP-server-The-current-connection-has-timeout
Article Number000155508
EnvironmentProduct: MOVEit Automation(Central)
Version: All
Platform: All
Question/Problem Description
When setting up an SFTP Host connection or running a task that uses a particular SFTP Host connection, why do I get an error like: 2850 Could not connect to SSHFTP server: The current connection has timeout? 
Steps to Reproduce1) Log in to Automation Web Admin (or the old standard console) as a user that has the ability to create or edit hosts.
2) Input the IP/Hostname, username, password or credential key, and the port number.
3) Test the connection.
Clarifying Information
This is functionally a general timeout error that indicates the attempted connection to the SFTP host was not successful. Usually this indicates that there is a network issue blocking the connection, and most often this means that the firewalls on the servers are not set up to allow the connection between the two hosts over the specified port number. In SFTP connections, the standard port is 22, so if you are creating a specified port connection for SFTP that is not using 22, then you will want to make sure the alternative port is configured correctly in the firewall. 
Error MessageError signing on to host: 2850 Could not connect to SSHFTP server: The current connection has timeout
Defect/Enhancement NumberN/A
The cause of this is a network or firewall issue related to the proper ports accepting connections from your Automation host. 
Work with the network or firewall team to open and configure the intended ports correctly. 
1) Use a different port, like the standard port 22, to connect over SFTP. 
2) Use a different protocol to connect. 
3) Investigate on the remote SFTP host if there are any signals of the attempt to connect from the Automation host. Typically, the Windows Event Viewer logs may show more information about the connection attempt. 
When investigating these timeout issues, one of the core questions is if the connection attempt is recorded on the server somewhere. This will indicate if connection is stopping in the network somewhere, or if there is some sign from the server regarding why it is not responding. Using a Trascert or a Wireshark packet capture can provide more information about what devices exist between the two hosts that could be interrupting the connection. 
Last Modified Date5/4/2020 5:33 PM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.