search

h3imdall / ftp-remote-edit

Edit files on ftp servers with Atom editor and without a workspace.
MIT License
178 stars 27 forks source link

"All configured authentication methods failed" #362

Open Josdansd opened 4 years ago

Josdansd commented 4 years ago

This problem keeps showing up whenever I try to connect to any SFTP server, and all the settings, passwords, or authentications methods are correct, I even connect with the same details on another ftp client.

I read some similar bugs around and tried the solutions on there by searching for the ".ftpconfig" file, but couldn't find it anywhere neither.

Some help would be really appreciated, I really need this package to work, it used to be fine and worked pretty well until today.

mariok90 commented 4 years ago

I am having the same issue. However, the solutions you found regarding editing the ".ftpconfig" file is related to another similiarly called package "Remote Ftp".

Josdansd commented 4 years ago

Thanks, I see, that's why I didn't found that file then.

Have you found any workaround to this?

mariok90 commented 4 years ago

I did the same mistake and looked for that file until I realized it is another package. Unfortunately, I was not able to find a workaround. So if someone can help it would be really appreciated. :)

morxw commented 4 years ago

Same here, i was also looking for that file but couldn't find it anywhere, but still kept looking for any "server configuration". Seems like they are encrypted until you enter your password. So i really don't know how to manipulate my configuration other than using the "edit server" window provided by the plugin. On some sftp clients connection works and on some it doesn't, kinda strange...

geejaytee commented 4 years ago

I'm having this on Win10: I have a private key configured for MobaXterm and for WSL (Ubuntu 18.10) (where it works to connect over SSH perfectly), but for some reason, trying to use it with ftp-remote-edit gives this message.

geejaytee commented 4 years ago

Is the maintainer actually looking at these issues? This has been open for four months

geejaytee commented 4 years ago

To update the issue I'm having: I've set up a Windows PowerShell key (which works under PowerShell for SSH), and tried that, assuming there was a (client-side) username mismatch, but I still get this error.

And I've imported the keys into Pageant (PuTTY) and tried connecting with ssh-agent instead and still the error.