Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • The response from Filezilla is: "Disconnected: No supported authentication methods available (server sent: publickey) " But I am using the same key that works for my SSH console login (PuTTy on windows btw) Commented Jun 15, 2015 at 11:35
  • 2
    SFTP is NOT FTP over SSH. You don't have to 'allow FTP' anywhere. The fact that Filezilla says "No supported authentication methods available" indicates it's connected to the server fine, and the problem is nothing to do with your firewall. How did you set up Filezilla to use your public key? Commented Jun 15, 2015 at 11:41
  • 1
    Hi and welcome to Unix & Linux. It gets confusing b/c SFTP shares a component of its name with the protocol FTP but beyond that they have nothing to do with each other. SSH is a single protocol that runs on port 22 and it provides the abilities to securely connect in the form of a interactive shell or to transfer files over the same connection. The SSH server on the remote side needs to allow for SFTP connections, so I'd look into the SSH server's logs for insights as to why it's failing in addition to making sure that Filezilla has an appropriate key to connect to the server securely. Commented Jun 15, 2015 at 12:31
  • I'd also take a look and verifying SFTP is setup properly from the server itself, yes you can use the command line sftp tool on the server to connect, which is helpful in verifying things before bringing Filezilla into the mix. digitalocean.com/community/tutorials/…. Commented Jun 15, 2015 at 12:34
  • May help others: I had an issue where I could ssh to my cVPS but sftp suddenly stopped working. I had made changes to my ~/.bashrc that may have precipitated this: commenting out export TERM=xterm-256color and adding export TERM=rxvt-256color. [I did this as 1. resizing splits in Vim was erasing lines, not resizing; 2, better color palette selection in ~/.vimrc] When I tried to connect to my cVPS on the command line, I got the error described here (the accepted answer was the solution): stackoverflow.com/questions/8250379/… Commented Jul 21, 2022 at 4:54