Try disabling any firewall software on your computer. Things seem to work nicely with limited ports, but when I perform actions that cause very. Response: 425 Cant open data connection.Error: Failed to retrieve directory listing. Response: 150 Opening data channel for directory list. iptables -I INPUT -p tcp -dport 22 -j ACCEPTĪt least one of those works, worst case scenario one fails. I have been obtaining errors like below because I did not specify enough ports for the active FTP connections. Let’s assume 22 from this point forward, though use your findings in #2 to inform otherwise. If it’s on another port and still fails the same, move on as well. Log in via web console and run this: netstat -tulpnĭo you see SSH? Is it on port 22? If not, try using the other port. While firewall can block ping too, I doubt you’ve done anything to block ICMP packets. Ping the droplet, see if you get a response. Let’s break those possibilities down a bit. I can’t say for sure which or which combination, but the timeout provides a clear indication that it is not directly based on login at that stage (though #5 would imply that it was in previous errors). Something like fail2ban on the server blocked your IP for a period of time after a few failed logins. Open the site manager to add a new website connection.

The client computer has SSH port blocked for outbound traffic.The server’s firewall has the SSH port blocked for inbound traffic.The SSH service is listening on a different port (not 22).Based on the provided information, it is my opinion that one or more of these is true:

Filezilla port connections