To avoid being detected by the thousands of hackers constantly scanning for people like you with an FTP server, we can change the port that FileZilla listens on. Hackers will constantly scan the internet for hosts listening on port 21, the default FTP port. Securing Your FTP ServerĪlong with configuring the user(s) with a strong password, there are a few settings within FileZilla that you can configure to further secure your new FTP server. To give the user further permissions, such as the ability to copy files to this repository, check the boxes beneath ‘Files’ and ‘Directories.’Ĭlick OK once you’re done setting the user permissions. By default, the user we’ve created is able to read files, list directories, and list subdirectories. Now we need to assign the user permissions for this repository. Once you’ve done that, a window like the one below will pop up, use it to select the directory you would like to share as an FTP repository.Ĭlick OK. Try overriding something like fail2ban.Click OK once you’re done entering the account name, and then click on “Add” underneath the “Shared folders” section. Try disabling any firewall software on your computer. iptables -I INPUT -p tcp -dport 22 -j ACCEPTĪt least one of those works, worst case scenario one fails. 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.

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:

Can t connect to filezilla server