Skip to main content
cajanson
Participant
Mar 27, 2017 8:26 PM UTC
Answered

SFTP/SSH using Public Key File not working

I have a public/private key pair which I can connect to using the command line (linux subsystem in Windows 10) but when I try to create a server connection using Private Key File: and enter the username, point to the identity file (private key) and enter the passphrase, the FTP connection fails saying invalid username and password (as if it's trying to still send UN/PW creds). 

I tail the logs on the server and am seeing the same information that the connection is closed due to invalid username and password (which it shouldn't be doing since this is an SSH key connection).  I've tried just regular open SSH keys and ppk formated keys with no joy.

Has anyone else had this issue?   Does this side of the Authentication settings in Site Setup even work?

This topic is closed to new replies. Start a new post to keep the conversation going.
mahakk20912952
mahakk20912952Correct answer
Adobe Employee
May 29, 2018 8:35 AM UTC

Hi All,

Dreamweaver does not support .ppk file. Please convert the .ppk file into .pem file using putty generator and try it out.

It should solve the problem.

Thanks,

Mahak Kudyar

Adobe Dreamweaver

10 replies

mahakk20912952
Adobe Employee
mahakk20912952Correct answer
Adobe Employee
May 29, 2018 8:35 AM UTC

Hi All,

Dreamweaver does not support .ppk file. Please convert the .ppk file into .pem file using putty generator and try it out.

It should solve the problem.

Thanks,

Mahak Kudyar

Adobe Dreamweaver

Translate
Participant
May 28, 2018 9:29 PM UTC

I use PuttyGen Convert to generate my key pair, and then export a PPK version of the key that works in FileZilla but not in Dreamweaver, and then from PuttyGen export an OpenSSH version of the key that works fine in Dreamweaver. So you can create keys for both in PuttyGen, and then put the public key generated from PuttyGen on the server you are connecting to.

Translate
Jonathan Joosten
Inspiring
Jul 3, 2018 3:03 PM UTC

I use PuttyGen Convert to generate my key pair, and then export a PPK version of the key that works in FileZilla but not in Dreamweaver, and then from PuttyGen export an OpenSSH version of the key that works fine in Dreamweaver. So you can create keys for both in PuttyGen, and then put the public key generated from PuttyGen on the server you are connecting to.

this did the trickfor me. No need to download any other software.

Translate
4cruzeta
Participant
Aug 21, 2017 10:58 AM UTC

Using the original .pem key did the trick for me:

I am using Dreamweaver CC 2017.5

Hope it can help.

4cruzeta

Translate
DerMaddin
Participant
Apr 16, 2017 11:16 AM UTC

I had the same issue.

Got it solved by using keys that were generated with ssh-keygen.

I have used the one which is shipped with GIT bash (https://git-scm.com/downloads).

Before that, I was trying to use keys (every available type) that were generated with puttygen.exe (they were working with Putty and FileZilla) and I got the same errors.

Translate
michaelc71532042
Participant
Apr 13, 2017 11:49 PM UTC

I am having this same issue. I'm using DW 2017.

I've generated an RSA key file.
I've tested the RSA key file using WinSCP--it works just fine with WinSCP.

When I set this up in the DW site manager and test, DW tells me there's something wrong with the username and password---but, I'm not using a password.

I'd sure like to know how to get this fixed.

Translate
Nancy OShea
Community Expert
Community Expert
Mar 27, 2017 9:34 PM UTC

Depends on the type of Key.  ED25519 is not yet supported in DW.   See related discussion below.

Dreamweaver SFTP with ED25519 Key

Nancy

Translate
Nancy O'Shea— Product User & Community Expert
cajanson
cajansonAuthor
Participant
Mar 28, 2017 1:32 AM UTC

Nancy,

No it's not ED25519.  Just a straight rsa key generated with

ssh-keygen -t rsa -C "email@domain.com"

But your link, and specifically the text "Dw does not yet support ed25519Key as this support was added to OpenSSL 1.1.0 and OpenSSL 1.0.2h in Aug 2016.", got me thinking that maybe I need to spec -t rsa1 to make the key a little more backward compatible (-t rsa defaults to rsa protocol v2 while -t rsa1 uses v1).  Tried that and still no joy.

My DW rev is 2017.0.1 so if you have any other ideas, I appreciate the consideration.

Thanks,

Craig

Translate