Problem with Nodes

Using Jenkins Ask a question
1

Hi,
If it’s possible- I have a question:
I put these details:

Remote root directory- /home/ubuntu
Labels- slaves
Usage - Use this Node as much as possible
Launch method- Launch agents via SSH
Host- 168.63.26.228
Credentials- ubuntu(the SSH for the slave Node)
Host Key Verification Strategy- Non verifying Verification Strategy/ Known hosts file verification Strategy
Availability- Keep this agent online as much as possible

The Host- is a azure VM I did and I succeed connect to it (with the public IP via ssh)
when I click on Save button and look on the log- I got this error:

SSHLauncher{host='168.63.26.228', port=22, credentialsId='b68ccc5b-290c-4b68-b6c9-8499867417a8', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=60, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.KnownHostsFileKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}
[03/07/22 07:22:53] [SSH] Opening SSH connection to 168.63.26.228:22.
Connection refused (Connection refused)
SSH Connection failed with IOException: "Connection refused (Connection refused)", retrying in 15 seconds. There are 10 more retries left.
Connection refused (Connection refused)
SSH Connection failed with IOException: "Connection refused (Connection refused)", retrying in 15 seconds. There are 9 more retries left.

If anyone will know what the problem is - it’ll help me a lot,
thanks,
Rachel

2

I’m surprised that you say it is configured as non-verifying strategy / known hosts strategy but then the output reports that you’re using known hosts verification strategy. On my system, non-verifying strategy is different from known hosts strategy. As a temporary attempt, try the non-verifying host strategy rather than the known hosts strategy.

Since the agent appears to be static, I recommend you ultimately should select the “Manually provided key strategy” and then use the command

$ cat /etc/ssh/ssh_host_ed25519_key.pub

to list the value to assign as the host key for that Jenkins agent. That will assure that you are connecting to exactly the computer you expect.