Ken Yau (Customer) asked a question.
I unfortunately do not have a solution but am also getting this error with some but not all ssh authentication. Did you ever find a resoution?
These algorithms were in my file but i just deleted them and readded them by copy/pasting and was able to connect. ssh-algos.txt file located at: C:\Users\<username>\AppData\Roaming\Ipswitch\WS_FTP
//Below is the response i got from progress support
Can you please go through the below article and see if it helps to resolve the issue.
https://community.progress.com/s/article/Supported-SSH-Algo-s
It looks like the below are missing in the ssh-algos.text file.
You can change the order if needed and see if it helps
===ssh-shk
ssh-rsa
ssh-dss
rsa-sha2-512
rsa-sha2-256
Hi Evan,
Thanks for replying to my post. We reverted back to the previous VM snapshot to get the keys working with version 12.7. I'll give this workaround a try on our next upgrade attempt.
We encountered the same issue. Initially, we tried resolving it by updating the ssh-algos.txt file, but that alone didn't fix the problem. Subsequently, I created a new site and managed to connect to it successfully. After establishing this new connection, the old sites also started working properly.
@Ken Yau (Customer) If you are receiving the below errors then it does not seem to be an issue with SSH HOST Key.
Invalid public key algo name
server rejected public key
Failed SSH User Authentication
*************************************
I would re-create the site connection with the SSH Keypair and check if that remediates the issue.
If it still persists then i would check if there are other Site connections that are failing in similar way.
If the issue is restricted to just 1 site and SFTP HOST then i would try to connect using Username/password instead of Username/SSH key combination. That would isolate if the issue is with the Key or something else is blocking the connection.
If the connection is successful using username/password then you can create a SSH key using WSFTP PRO and use it while sharing the pub key part to the Client. You can export only the pub key from WSFTP PRO.
Your client can also generate a new SSH key pair and share the PUB+PVT key with you to integrate with WSFTP PRO and align it with the site connection for trial/testing.
@Samik Chakraborty (Progress Software Development)
We have done all these things. We changed the keys, we created keys with WSFTP PRO or putty kegen, but nothing did help.
And we alos have this problem with 1 of a lot of connections with ssh keys. Also only in Version 12.9. With Version 12.8 all connections run.
We had the same issue and traced it down to the key type. Using an RSA key to connect to a DSA server failed. Using the same key to connect to an RSA server worked. If you have the option to create a new test key, try making sure it matches the server configuration.
@Rainer Schilli (Volksbank eG) The SSH algos.txt file in WSFTP Professional vers 12.9 supports both SSH-RSA, SSH-DSS, rsa-sha2-512
rsa-sha2-256 host key algos.
If the server that PRO is connecting to supports any of the above then connection should establish. If NO, then you can check with Client what SSH HOST key they support and accordingly you can modify the HOST key positions in the SSH-Algos.txt file and check.
If the issue with some other algos then we need to check with client and re-position the algos
Hope that it wont affect other connections. If it does then you have to strip off the changes.
We are having the same issue since the upgrade. We were asked to do the same thing.
The solution above fixed the issue with some account but not with all accounts. Changing the prefrence will also resolve the issue for some SFTP connections but not for others. Makesure to check all SSH connections after making the change.
Everything was working fine before upgrading the software from version 12.8 to 12.9.
The issue is with the new client not on the server side.
We have solved the problem.
You should delete the entry "ssh-dss" in the file ssh-algos.txt.
Our file looks like this:
===ssh-shk
ssh-rsa
After this restart the WSFTP Pro 12.9 Client an test the established connections.
I managed to resolve my issue by just deleting "ssh-dss". So our ssh-algos.txt looks like this:
===ssh-shk
rsa-sha2-512
rsa-sha2-256
ssh-rsa
You may have other connections that require "ssh-dss", so try moving it to the bottom of the list.