Jenkins Publish over ssh authentification failed with private key

Question

I can authenticate successfully with putty on the server with my private key and passphrase. But when I try to do it with jenkins publish over SSH plugin (using Test for configuration), I get the following error message:

jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config myconfig. Message [Auth fail]

I entered the same information as in putty:

Hostname : myhostname
Username : myusername
Remote Directory :

Use password authentication, or use a different key Passphrase / Password Path to key : checked
Path to key : mypath
Passphrase : mypasssword
Key:
Port:22
Timeout(ms):300000

If you have any idea ... Thanks for your help.

Jenkins guide on the plugin points out that checking the options "Use password authentication, or use a different key Passphrase / Password Path to key" enables three further fields to supply details to "Path to key", "key" and "Passphrase" ... I dont see passphrase on the info above, have you supplied your password in that box as well? — AltF4_, Mar 17 '14 at 23:32
Sorry I put the passphrase too but I forgot it in my question. In fact I put exactly the same information as in putty. I really do not understand the issue ! — Corinne Kubler, Mar 18 '14 at 18:36
See [this issue](https://github.com/jenkinsci/publish-over-ssh-plugin/issues/247) on GitHub — ZhekaKozlov, Jul 18 '22 at 14:32

score 17 · Accepted Answer · edited Sep 14 '15 at 13:33

17

Looks like you're using keyfile authentication, so you'll get this error from Jenkins if you haven't set the permissions correctly on your .ssh folder and/or ~/.ssh/authorized_keys file.

the .ssh folder should have drwx------ permissions (read/write/execute owner only)
the authorized_keys file should have -rw------- permissions (read/write owner only)

To fix it:

chmod 700 ~/.ssh
chmod 600 ~/.ssh/authorized_keys

edited Sep 14 '15 at 13:33

Community

1
1

answered Mar 26 '14 at 15:19

inanutshellus

9,683
9
53
71

4

I'm having this error `jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to connect session for config [deploy-server]. Message [Auth fail]]` Any other thing I need to take care? I have jenkins user in deploy server I can `ssh` to that through putty. – The_ehT Jan 14 '19 at 17:10
In my system, the permissions were correct, but the issue was still there. I was using private key for authentication, this solved it : `cat id_rsa.pub >> authorized_keys` – lycanthrope10100 Jun 09 '21 at 07:49

score 6 · Answer 2 · answered Jul 23 '15 at 13:59

6

I ran into the same issue today and it turned out i was accidentally supplying the path to the public key instead of the private one.

So the "path to key" should be something like

.ssh/id_rsa

instead of

.ssh/id_rsa.pub

answered Jul 23 '15 at 13:59

Rinda

326
2
5

Aaaaah, same mistake here. Thanks! – sbrattla Jun 12 '18 at 19:38
@Rinda where do you supply this and is this answer still valid today? – shan Jul 28 '20 at 13:50
how can i know the path of the private key if i'm using a jenkins docker image ? – Youssef Boudaya Apr 21 '21 at 11:32
Please I have a question and I'm quite new to Jenkins configuration part. Is the private key the one for the AWS EC2 instance which can be found when you log into the instance over SSH? Or this is the private key on your computer. For example I am a Mac user – Emmanuel Spencer Egbuniwe Mar 07 '23 at 16:49

score 3 · Answer 3 · edited Aug 02 '16 at 11:59

Because your linux login need password, the answer is :

 1. Passphrase: your passphrase
 2. path to key: your private key path
 3. key : blank
 4. Disable exec : un-check

SSH Servers

1. Name: remote_user@remotehost.com
 2. hostname: remotehost.com
 3. Username: remote_user
 4. Remote Directory: empty

Advanced --

5. check the box "use passsword authentication, or use a different key"
    `important`

 6. Passphrase / Password: your linux login password`important`

 7. path to key: blank

 8. key:blank

 9. port: 22

 10. Timeout(ms): 300000

'Test Configuration' success

Thank you very much. It helped me a lot. – Pramod Jan 16 '17 at 13:50 — Pramod, Jan 16 '17 at 13:50

Joey Coleman · Answer 4 · 2014-05-06T06:02:15.890

2

Check that the public key is in the .ssh/authorized_keys file on the target server, even if the target server is the same as the jenkins server. I had what is probably the same problem, and it turned out that I needed this, even though ssh localhost worked fine.

(Addendum: also check that the jenkins server has the target server in its .ssh/known_hosts file, as that can affect this as well.)

edited May 06 '14 at 06:02

answered May 05 '14 at 19:50

Joey Coleman

479
9
16

`.ssh/known_hosts` created issue in my case. removing fingerprint from `known_host` solved the problem – anand Jul 14 '17 at 17:04

score 1 · Answer 5 · answered Mar 17 '14 at 23:40

I think as it says this is a authentication issue:

Use password authentication, or use a different key Selecting this option will produce 3 more configuration boxes that mirror the options available for the Jenkins SSH Key.

Passphrase / Password If either Path to key or Key are configured then this is the passphrase to use with the encrypted key. If no key is configured then this is the password that will be used for password authentication.

Path to key See description above.

Key See description above.

Disable exec This option will remove the ability to execute commands using this configuration.

LINK HERE

Thanks for your answer but I did put exactly the same information as in putty but it does not work in jenkins — Corinne Kubler, Mar 18 '14 at 18:37

score 1 · Answer 6 · answered Jul 18 '14 at 10:08

I am facing same issue , the following steps work for me:- ( i am using jenkins 1.57)

Go to http:///jenkins/manage
1. Configure System
2. Browse to Publish over SSH section
  - Passphrase: blank
  - path to key: blank
  - key : blank
  - Disable exec : un-check
  - SSH Servers -- Name: remote_user@remotehost.com -- hostname: remotehost.com -- Username: remote_user -- Remote Directory: empty -- Advanced -- check the box "use passsword authentication, or use a different key" -- port: 22 -- Timeout(ms): 300000 -- 'Test Configuration'

success

score 0 · Answer 7 · answered Nov 07 '18 at 08:44

0

Try restarting ssh of remote server

        /etc/init.d/sshd restart

answered Nov 07 '18 at 08:44

Supun Dharmarathne

1,138
1
10
19

score 0 · Answer 8 · answered Jun 27 '20 at 03:31

0

Don't do any ssh-keygen. Just enter the pem key details under key field, Add SSH server details: Name, Hostname and Username as ec2-user. Click test connection and it works.

answered Jun 27 '20 at 03:31

lalith

1

score 0 · Answer 9 · answered Jun 27 '20 at 03:46

Sometimes the SSH connection would fail, if the destination server doesnt have enough disk space to perform PUT operation

{ERROR: Exception when publishing, exception message [Failure]}

Make sure to verify the destination server has enough disk space.

In case of Linux, you can use 'df -kh /directoryname' to check the disk space

score 0 · Answer 10 · answered Aug 24 '20 at 22:39

0

Just copy jenkins-user's id_rsa.pub to the end of ~/.ssh/authorized_keys on remote host.

answered Aug 24 '20 at 22:39

artemiuz

444
5
7

score 0 · Answer 11 · answered Dec 25 '21 at 02:01

0

I was having the same exact issue today and thought I would share what worked for me

Normally when I would SSH into my ec2 instance AWS likes the username to be

ubuntu@[ip address/url]

Jenkins likes it to be just the username so remove the rest

ubuntu

answered Dec 25 '21 at 02:01

Cesar Bielich

4,754
9
39
81

KoKon · Answer 12 · 2022-06-15T04:08:14.687

0

If you use RSA key, and see string like this in your private key:

    -----BEGIN RSA PRIVATE KEY-----
***************************************

-----END RSA PRIVATE KEY-----

You need edit config file sshd on remote machine:

sudo vim /etc/ssh/sshd_config

add in this file stoke:

HostKeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa

edited Jun 15 '22 at 04:08

answered Jun 15 '22 at 04:06

KoKon

1
1

score 0 · Answer 13 · answered Jun 25 '22 at 01:04

I have the same problem，I am on windows, the solution:

open the openssh debug model, no can see the error detail, detail click
- Stop the sshd service
- Type 'sshd -d' in PowerShell

no if you connect again ,you can see the error detail, my error is

userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms [preauth]

we can add PubkeyAcceptedKeyTypes=+ssh-rsa in server sshd_config file, detail click
now test success, if still has error like Failed to connect SFTP channel and debug is
```
debug1: subsystem: cannot stat sftp-server.exe: No such file or directory
```
this because the openssh no in windows system path. detail click

Jenkins Publish over ssh authentification failed with private key

13 Answers13

Linked