Overview

When using the FTP or SFTP connector in Skyvia, you may encounter various errors due to connection misconfiguration or server access issues. Below are the most common errors, their likely causes, and steps to resolve them.

1. Invalid Private Key (SFTP)

Skyvia requires OpenSSH-format private keys for SFTP connections. If you see this error, make sure your key is properly converted. To convert a private key using the PuTTY Key Generator:

1. Open PuTTY Key Generator.
2. Go to File → Load private key and select your key.
3. Navigate to Conversions → Export OpenSSH key and save the file.
4. Use the newly generated key in your Skyvia SFTP connection.

2. No such file

This error typically occurs due to incomplete IP whitelisting on your server. Even if the Skyvia website can connect, the runtime environment may be blocked.

Make sure all Skyvia IP addresses are whitelisted on your FTP/SFTP server:

• 40.118.246.204
• 13.86.253.112
• 52.190.252.0

3. No such host is known

This usually indicates that Skyvia cannot resolve your FTP/SFTP server's hostname.

1. Check that your server's DNS name is correct and publicly accessible.
2. Whitelist all three Skyvia IP addresses listed above.

For more context, see the SmartFTP article on this error.

4. Permission Denied / Access Denied

This error occurs when the FTP/SFTP user lacks access rights to the specified folder or file.

1. Verify user permissions on the server.
2. Ensure the file path is correct.
3. Confirm all Skyvia IPs are whitelisted (see list above).

5. Timed out trying to read data from the socket stream

This error can happen if ports are blocked by your server or firewall.

1. Ensure the server is accessible on standard ports: 21 for FTP, 22 for SFTP.
2. Check firewall rules and server network settings.

For more about possible causes of timeout issues, see FTP Read Timed Out troubleshooting guide.

Useful Links

• FTP Connection Setup in Skyvia
• SFTP Connection Setup in Skyvia