I'm getting this error trying to connect to PFSENSE 3.2:
Fatal error: Please make sure your connection settings are valid.
Couldn't agree a key exchange algorithm (available: curve25519-sha256@libssh.org)
When I tried on putty I'd get the same error, but updating to latest version solved the issue with putty, so I'm guessing that since you use putty internally, you need to update putty version, or I'm missing some configuration?
Hello,
Could you tell us what version of PuTTY you updated to to fix this issue? Unfortunately, updating our integration with the latest version of PuTTY isn't as simple as it seems since we modified a lot of code to make it work inside RDM as well as giving it new functionalities.
Regards,
Hubert Mireault
Hello,
I updated to 0.67
Thank you for the information. We will try to update our SSH integration as soon as possible since 0.67 is a stable release.
Regards,
Hubert Mireault
Any update on this, I have the latest version of RDM, and not able to ssh to my pfSense???
Hi,
This is coming soon in beta. It's already implemented internally.
Regards
David Hervieux
Hi,
Thank you very much for the prompt response, How can I get a copy of that Beta version, please?
It should be available next week:
https://remotedesktopmanager.com/Home/ThankYou?f=RDMsetupBeta
Regards
David Hervieux
I downloaded the Beta from the link you have provided, and installed it, and I got the same error message of - Couldn't agree a key exchange algorithm
I tried to take a screenshot, but was not able to, how can I enable taking a screenshot of it? This is critical for us to use this product to ssh to pfSense. I am able to use SecureCRT, but RDM is not working. Please advise!
Like I mentioned, it's not available yet. This will be in a future beta. Perhaps next week. Hubert will notify you when it's available.
Regards
David Hervieux
David,
Thank you, and I apologize if I was under the impression that was a direct link to the beta. I will hold for the release, thank you again.
Good morning, I was prompted to install and update version 12.0.16.0 which I did, and that still throws the same error. Still can not ssh to my pfSense.
Hi,
Indeed it's still not included. Hubert will notify you here when it's available.
Regards
David Hervieux
Thanks!
I am checking back in, I was told, this week, and we are Thursday, any updates?
We will have another beta later today but this will not be included. We still have stability issues with the updated version of Putty. We have two people working on it. By the way, in the meantime you can use Putty in external mode.
Regards
David Hervieux
I appreciate the prompt response, but do we have an ETA on the stability issues and the new roll out?
Hello,
We're currently in our last testing phase for the updated terminal. I'll update you soon on the progress but I'm pretty sure it will be completed this week if we don't encounter any further issues.
Regards,
Hubert Mireault
I can confirm we should have this available for the next version of RDM. If you find any issue with the updated terminal we would appreciate the feedback.
Regards,
Hubert Mireault
Thank you very much. I will look forward for the update when it is rolled out. I will let you know upon testing, thanks!
Just checking back in, you said this week, and no updates were rolled out?
Hi,
Good news. the beta is now available. This is in the version 12.4.1.
We are near feature complete and now we focus on bug fixes for the final release of RDM 12.5
https://remotedesktopmanager.com/Home/Download#beta
Regards
David Hervieux
I installed the beta, and now I get this error. I uninstalled RDM, and re-installed it twice, and still get this message.
Hi,
Is it only when you open the ssh shell? The guys will be able to check this Monday.
Regards
David Hervieux
Yes, only SSH
I have assigned this to our devs. Thank you for your help. This is a huge upgrade. By the way, do you get the same error in 32bit and 64 bit?
Regards
David Hervieux
Hello,
Could you try two things to help us reproduce the issue:
1. Could you try running RDM as administrator if you haven't tried yet and see if the issue still happens
2. Could you export one of your SSH Shell entries without the credentials and send it to us so we can see if it's a particular combination of settings that causes this issue
Regards,
Hubert Mireault