Why Does the SFTP Integration Hang and Eventually Timeout Despite Correct Credentials and Standard Workflow?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi - Is there any reason why the SFTP integration will just hang and eventually timeout? Credentials are correct, can SFTP in through terminal and other sources. Workflow is the out of the box version…simply just tries to connect with no additional things

2

Hi Mike,

Is your FTP server accessible to only specific IP addresses? If so you can either open up it’s rules to all AWS us-east-1 IPs, or make use of a VPC for a static outbound IP address from your workflows to your FTP server:

3

it’s accessible to all IPs but I’ll double check. Any other reason?

4

are there any other reasons why an SFTP connection could time out besides a blocked IP address?

5

Apart from a blocked IP address, there could be several other reasons for an SFTP connection to time out, such as: 1. Network issues between your Pipedream workflow and the SFTP server. 2. The SFTP server might be experiencing high load or performance issues. 3. Incorrect configuration or settings on the SFTP server. 4. Firewall or security settings on the SFTP server that might be causing the connection to drop. To troubleshoot the issue, you can check the server logs for any errors or warnings, and ensure that the server settings are configured correctly. If the issue persists, you might want to contact your SFTP server administrator for further assistance.

6

that automation is insanely cool. Thanks and @U02SX7ETBFB

7

You’re welcome! I’m glad you find it helpful. If you have any more questions or need assistance, feel free to ask.