Can't connect to server using Filezilla.

My configuration for Filezilla are:

Protocol: SFTP Host: my ip address Port: 22 Logon type: Key file User: root

I try to connect to server and receive this error:

Status: Connecting to <my ip address>… Response: fzSftp started, protocol_version=8 Command: keyfile <my ppk file> Command: open “root@<my ip address>” 22 Error: Connection timed out after 20 seconds of inactivity Error: Could not connect to server

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Thanks! Port is blocked on my PC. Now I’ll try to understand why.

Hello there!

Based on the provided information, it is my opinion that one or more of these is true:

  1. The server’s networking is down.
  2. The SSH service is listening on a different port (not 22).
  3. The server’s firewall has the SSH port blocked for inbound traffic.
  4. The client computer has SSH port blocked for outbound traffic.
  5. Something like fail2ban on the server blocked your IP for a period of time after a few failed logins.

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). Let’s break those possibilities down a bit.

+1. Ping the droplet, see if you get a response. While firewall can block ping too, I doubt you’ve done anything to block ICMP packets. It’s just not common behavior.

If this fails, refer to

+2. Log in via web console and run this:

netstat -tulpn

Do you see SSH? Is it on port 22? If not, try using the other port. If it is, move on. If it’s on another port and still fails the same, move on as well.

+3. Open the port. Let’s assume 22 from this point forward, though use your findings in #2 to inform otherwise.

iptables -I INPUT -p tcp --dport 22 -j ACCEPT
ufw allow 22/tcp

At least one of those works, worst case scenario one fails.

+4. Try disabling any firewall software on your computer.

+5. Try overriding something like fail2ban.

iptables -I INPUT -s -j ACCEPT

Hope that helps :)