Couldn't Agree A Key Exchange Algorithm
May 29, 2018 - That's not the latest version of PuTTY. ECDH key exchange (including Curve25519) has been supported since 0.68 (February 2017), and the.
Hello Jens,I guess your SSHd-Service does not provide the needed cipher to get the PRTG-SSH-Sensor started properly. To determine what cipher is missed, take a look at the dmesg-output on the monitored system while the PRTG-SSH-Sensor tries to connect:. On the Linux-console you should use the dmesg-command e.g. ' dmesg grep sshd' (further information with ' man dmesg').
Please search for lines similar to:sshd1914: ID 800047 auth.crit fatal: Client and server could not agree on a common cipher: client 'blowfish-cbc,cast128-cbc,aes128-cbc,3des-cbc', server 'aes128-ctr,aes192-ctr,aes256-ctr,arcfour128,arcfour256,arcfour'.
If ssh -T git@github.com gives you the: Hi! You've successfully authenticated, but GitHubdoes not provide shell access.message, that means your ssh setup is working.
If you get a: FATAL ERROR: Couldn't agree a key exchange algorithm.that means your ssh setup isn't working. Clearly there's a contradiction here, and the most likely culprit is that you have two different ssh commands installed: one that you are using, which works, and another that Git is using, which doesn't.to has a lot of upvotes. I avoid Windows, so I have no idea whether this will help. (I don't even know if you're on Windows since you have not mentioned it.)Note that,. Since then, In all cases it's important to figure out which ssh Git is running, and make sure it runs one that actually works. See for a description of all the option variables and what they do.
Couldn't Agree A Key Exchange Algorithm Sourcetree
The link here goes to a web page that may not match your own Git version, so consider running git -help git to read that version, if your Git is very old.