Not using private key file

Report · Jul 15, 2022

This concerns Dreamweaver v 23.1 on Windows 10. I just installed Windows latest update yesterday. A description of the problem is below. To replicate-

-set up a remote server using SFTP

-use private key authentication

-enter the correct user name

-enter the correct password

-select the correct private key file

-attempt to put files to the server or to connect to the server

Expected result is a connection to the server (has worked for years using same info). Actual result is an FTP error "cannot make connection to the host. Your login or password is incorrect. Please check your connection information".

Starting today, after updating to the newest version of Dreamweaver, on Windows 10, I am getting an FTP error when I try to connect by SFTP to my remote web server. It tells me that my password and login are incorrect. This is not the case. My login credentials and my private key are correct. My private key is stored on my E drive. It is a .pem key that has worked for years. I have tried the ppk version of my key on FileZilla, and it works.

I think that Dreamweaver is not picking up the file. Below is the bottom portion of my SFTP log file. My private key is on my E drive. It's locaction is E:\************.pem (with the wildcards representing the actual file name). Notice how my log file seems to only pick up my E drive, and not the rest of the file path.

fopen ~/.ssh/known_hosts: No such file or directory
fopen ~/.ssh/known_hosts2: No such file or directory
fopen /etc/ssh/ssh_known_hosts: No such file or directory
fopen /etc/ssh/ssh_known_hosts2: No such file or directory
Could not create directory '~/.ssh' (No such file or directory).
Failed to add the host to the list of known hosts (~/.ssh/known_hosts).
send packet: type 21
set_newkeys: mode 1
rekey out after 134217728 blocks
SSH2_MSG_NEWKEYS sent
expecting SSH2_MSG_NEWKEYS
receive packet: type 21
SSH2_MSG_NEWKEYS received
set_newkeys: mode 0
rekey in after 134217728 blocks
Will attempt key: E explicit
done
send packet: type 5
receive packet: type 7
SSH2_MSG_EXT_INFO received
server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
receive packet: type 6
service_accept: ssh-userauth
SSH2_MSG_SERVICE_ACCEPT received
send packet: type 50
receive packet: type 51
Authentications that can continue: publickey
start over, passed a different list publickey
preferred publickey,password
authmethod_lookup publickey
remaining preferred: password
authmethod_is_enabled publickey
Next authentication method: publickey
Trying private key: E
we did not send a packet, disable method
No more authentication methods to try.

According to the log file, my server is running OpenSSH 7.4 and my local OpenSSH is version 8.8.

Report · Sep 04, 2022

Same experience. Downgrading to 21.2 is only thing that I've been able to do (MacOS 12.5.1). Connecting to a Digital Ocean Droplet that's had a stable SFTP connection for 3+ years. Latest FileZilla and Cyberduck continue to connect. Changing SFTP config and prefs as mentioned in this and other threads did not change outcomes. I don't manage the Droplet, so have limited server management/update solutions, including generating new keys. Would love to hear if anyone else has found a workaround. I understand the updated security protocols but this feels buggy to me.

Report · Sep 12, 2022

Hi,

Can you please confirm if you have enabled the required preference of "Use SFTP Legacy Algorithms From Config File" to TRUE as mentioned in this SFTP connection troubleshooting KB article, and see if the SFTP server connection is successful. If the issue is observed even after enabling the preference and previously suggested config file changes, we can have a remote connect session at your convenient time for further debugging the issue on your machine as the connection issue seems to be specific to particular SFTP server configuration.

Have a pleasant day!

Thanks,

Nayan

Dreamweaver Team

Report · Sep 12, 2022

Hi,

Yes, I tried all of the proposed solution but it didn't work. I don't get any of the messages from the KB article, I get this message

This is installed on a Windows Server 2016 and it was updated to the latest version.

What's interesting is that I did a fresh install on a MacOS and installed the latest version of Dreamweaver and it connected successfuly with the exact same details for SFTP connection.

Report · Sep 13, 2022

Success! Using the KB Article Nayan referenced, my Preferences file did not include the line "use sftp legacy algorithms from config file" when I originally found this thread and the KB Article. This may have been due to a previous series of reverting/updating combos during troubleshooting or just plain oversight. I did not try to add the line at the time.

However, after reinstalling 21.3 build 15593 (Mac OS) I now see that line under the [SITE PREFERENCES] heading in my prefs file; I changed the value to TRUE and can now connect to the Digital Ocean Droplet via SFTP as I had before.

Report · Sep 15, 2022

Hi @Cristina25579426utrb,

Can you please try the below steps and confirm if the connection gets successful.

1. Quit Dw

2. Replace the content with the below entries in the config file present within the folder

"/Users/<username>/Library/Application\ Support/Adobe/Dreamweaver 2021/<locale>/Configuration/SFTP/".

HostkeyAlgorithms +ssh-rsa,ssh-dss,rsa-sha2-256,rsa-sha2-512
PubkeyAcceptedAlgorithms +ssh-rsa,ssh-dss,rsa-sha2-256,rsa-sha2-512
PubkeyAcceptedKeyTypes +ssh-rsa,ssh-dss,rsa-sha2-256,rsa-sha2-512
ChallengeResponseAuthentication no
MACs +hmac-sha1

3. Save and close the file

Considering the SFTP connection is dependent on the server's OpenSSH protocol compatability, we have requested for a remote connect session to you via private email twice, but we haven't received any response from your side on our private email. Now, to further investigate the behavior on your machine with your specific server configurations, it would be great to have a remote connect session for debugging the behavior and try resolving the same.

Have a pleasant day!

Thanks,

Nayan

Dreamweaver team

Report · Sep 15, 2022

Hi @4105design,

Thanks for the confirmation. Glad to hear the issue is resolved with the steps in the KB article.

Have a pleasant day!

Regards,

Nayan

Dreamweaver Team

Report · Apr 15, 2023

@Nayan Kankariya , I tried your fix with the Pubkey, etc. entries. My computer runs windows, so the file was located in a different folder. I replaced the old entries with your suggested entries, via copy and paste, saved, and restarted my new machine. It is a Windows 11 machine. I have the exact same problem, except now, I cannot find an error file. I think your suggested entries confuse some other module or modules within the application, and that is why there is no error log file produced.

My issue has absolutely nothing to do with the deprecated protocols, as I have already stated. As of now, I have had this issue on 3 to 4 separate remote servers from 2 different workstations. My first workstation had Windows 10. It produced the log file that I pasted in my first post. I think requests to 3 servers or possibly 4 had this issue, using that machine. Around January of this year, I got a new workstation, which runs Windows 11. The three servers from before were AWS Linux instances, and I manually checked the algs those instances used. I have referenced the version of OpenSSH they were using in this discussion. I now have an AWS Linux 2 instance, and have installed the most recent version of OpenSSH on it. This was many months ago. I get the same error with this server. So now 2 machines have used v 21.3 and both have failed on at least 1 server, and the first machine failed on up to 4 servers. It is the exact same error every time, and reverting to v 21.2 works every time as well.

I think the issue is Dreamweaver not picking up the full file path for my .pem file. See my log file output and my previous posts that describe this issue. What file or files in Dreamweaver's source code executes the sftp request? I could probably find the error myself if I knew where to look.

Report · Apr 16, 2023

@Renaissance501,

Path problems have been previously reported. Use these steps.

1. Export your site definition stettings to STE file from Manage Sites panel.

2. Open STE with Dreamweaver (it's essentially a text file). Edit path to SSH generated .pem key as required and Save.

3. Go back to Manage Sites and Import newly edited STE file.

That should work. Post back & let us know.

Nancy O'Shea— Product User, Community Expert & Moderator

Report · Apr 16, 2023

The .ste file was correct. It is not the source of the problem. It has something to do with the source code that executes the SFTP request, I am quite certain. That code is not picking up the full path of the .pem key. Earlier today, I started a new AWS Linux 2023 instance. It comes preloaded with OpenSSH 8.7. Below is the error log from the attempt to connect to that server:

entering
Connecting to MYIP [MYIP] port 22.
Connection established.
Local version string SSH-2.0-OpenSSH_8.8
Remote protocol version 2.0, remote software version OpenSSH_8.7
match: OpenSSH_8.7 pat OpenSSH* compat 0x04000000
fd 2 setting O_NONBLOCK
Authenticating to MYIP:22 as 'MY AWS USERNAME'
put_host_port: [MYIP]:22
fopen ~/.ssh/known_hosts: No such file or directory
fopen ~/.ssh/known_hosts2: No such file or directory
fopen /etc/ssh/ssh_known_hosts: No such file or directory
fopen /etc/ssh/ssh_known_hosts2: No such file or directory
no algorithms matched; accept original
send packet: type 20
SSH2_MSG_KEXINIT sent
receive packet: type 20
SSH2_MSG_KEXINIT received
local client KEXINIT proposal
KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
host key algorithms: ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,sk-ssh-ed25519-cert-v01@openssh.com,sk-ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256
ciphers ctos: chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
ciphers stoc: chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
compression ctos: none
compression stoc: none
languages ctos:
languages stoc:
first_kex_follows 0
reserved 0
peer server KEXINIT proposal
KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512
host key algorithms: ecdsa-sha2-nistp256,ssh-ed25519
ciphers ctos: aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes128-gcm@openssh.com,aes128-ctr
ciphers stoc: aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes256-ctr,aes128-gcm@openssh.com,aes128-ctr
MACs ctos: hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512
MACs stoc: hmac-sha2-256-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha2-256,hmac-sha1,umac-128@openssh.com,hmac-sha2-512
compression ctos: none,zlib@openssh.com
compression stoc: none,zlib@openssh.com
languages ctos:
languages stoc:
first_kex_follows 0
reserved 0
kex: algorithm: curve25519-sha256
kex: host key algorithm: ssh-ed25519
kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
send packet: type 30
expecting SSH2_MSG_KEX_ECDH_REPLY
receive packet: type 31
SSH2_MSG_KEX_ECDH_REPLY received
Server host key: ssh-ed25519 SHA256:OD6Eikuxy7iBJcA+ip9dze7c3mMncyo1I62COw7H1Qc
put_host_port: [MYIP]:22
put_host_port: [MYIP]:22
fopen ~/.ssh/known_hosts: No such file or directory
fopen ~/.ssh/known_hosts2: No such file or directory
fopen /etc/ssh/ssh_known_hosts: No such file or directory
fopen /etc/ssh/ssh_known_hosts2: No such file or directory
Could not create directory '~/.ssh' (No such file or directory).
Failed to add the host to the list of known hosts (~/.ssh/known_hosts).
send packet: type 21
set_newkeys: mode 1
rekey out after 134217728 blocks
SSH2_MSG_NEWKEYS sent
expecting SSH2_MSG_NEWKEYS
receive packet: type 21
SSH2_MSG_NEWKEYS received
set_newkeys: mode 0
rekey in after 134217728 blocks
Will attempt key: D explicit
done
send packet: type 5
receive packet: type 7
SSH2_MSG_EXT_INFO received
server-sig-algs=<ssh-ed25519,sk-ssh-ed25519@openssh.com,ssh-rsa,rsa-sha2-256,rsa-sha2-512,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ecdsa-sha2-nistp256@openssh.com,webauthn-sk-ecdsa-sha2-nistp256@openssh.com>
receive packet: type 6
service_accept: ssh-userauth
SSH2_MSG_SERVICE_ACCEPT received
send packet: type 50
receive packet: type 51
Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic
start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic
preferred publickey,password
authmethod_lookup publickey
remaining preferred: password
authmethod_is_enabled publickey
Next authentication method: publickey
Trying private key: D
we did not send a packet, disable method
No more authentication methods to try.

My .pem file is on my D drive on my new computer. You will see that it, once again, only picks up the drive location and not the remaineder of the file path,

Report · Apr 16, 2023

I NEVER use Dreamweaver to connect to AWS. Never, never, ever. 😞

I use Dreamweaver to successfully connect with commercial web hosting services like InMotion, HostLabs, GoDaddy, Bluehost, etc... AWS is an entirely different beast. Use your AWS connection terminal or another S/FTP client that's compatible with AWS.

Nancy O'Shea— Product User, Community Expert & Moderator