Thanks Harald.
Your post was very helpful - I was coming across the same issue where our
Windows Jenkins host could not connect to our Linux slaves.
"ssh -o HostKeyAlgorithms=ssh-rsa ..." fixed our issue
It seems that our Jenkins server (2.46.3) doesn't like me using
ecdsa-sha2-nistp256
I logged in to the Master server in a command line shell and sudo'd (sudo
-su ) to the user running the Jenkins war file. I ran the ssh command
to connect to each of the Jenkins Agent machines and had no issue
connecting. I did this with both the machine name and the fully qualified
domain
I logged in to the Master server and sudo (sudo -su ) to the user
running the Jenkins war file. I ran the ssh command to connect to each of
the Jenkins Agent machines and had no issue connecting. I did this with
both the machine name and the fully qualified domain name (e.g. machine1,
and
Thank you! I added this workaround
to https://issues.jenkins-ci.org/browse/JENKINS-42959
On Friday, March 24, 2017 at 1:31:34 AM UTC-7, Harald Wellmann wrote:
>
> Yes, I can ssh both ways. The problem seems to be that the SSH lib used by
> Jenkins does not support newer ciphers like
Can you ssh from master to slave and back as the jenkins user? If not look
at you ssh setup. SSH is picky about the permissions of all the files under
~/.ssh.
On Thursday, March 23, 2017 at 12:45:33 PM UTC-4, Harald Wellmann wrote:
>
> After upgrading to SSH Slave Plugin 1.15 on Jenkins
After upgrading to SSH Slave Plugin 1.15 on Jenkins 2.32.3, I'm
getting warnings
about missing SSH key verification which I'm trying to fix.
I've configured Known hosts file verification strategy, I've manually ssh'ed
from my master to my slave, and I've checked there's an entry in my
