Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,506
Community Members
 
Community Events
168
Community Groups

Permission denied for SSH on Pipelines

Hi there,

I followed this guideline to create a new SSH key for my repo:

https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html

I created it in the repo settings (also added the server to the known hosts) and added the public key on the remote server.

 

Now, I want to access my remote server in a Bitbucket Pipeline via:

ssh -T user@XX.XX.XX.XX rm testfile

But I stuck on that:

Permission denied, please try again.
Permission denied, please try again.
Permission denied (publickey,password).

 

Where is the fault that I cannot access my remote server to execute the command?

 

Thanks a lot

3 answers

1 accepted

1 vote
Answer accepted

Hi Max,

Can you try do a quick check that the connection works:

$ ssh -qT user@downhost exit
$ echo $?
// Should be 0

Your user may not have permission to modify files, so it'll be good to remove that factor first. If you get a 0, then double check the permissions of the user you're SSH'ing as.

If not, you can also double check you have whitelisted the necessary Pipelines IP's.

Thanks,

Phil

Hi Philip,

Im having this same issue, i ran the commands you stated and i got a 0, but i still get the permission denied error. Please any suggestions what might be wrong?

@Olusiji David,

Can you try run this instead. I forgot there's an edge case with the way error codes work.

$ ssh -qT user@downhost exit; echo $?

Thanks

Hi Philip,

Where exactly is this command to be executed? In the bitbucket-pipelines.yml file or on the  remote computer? Do I have to customize user@downhost or leave it in the command?

$ ssh -qT user@downhost exit
$ echo $?
// Should be 0

 

When I run this on the remote computer I get a value of 255. What should I do afterwards?

Sorry for the many questions, but I am still a beginner in the field.

Thanks,

Sebastian 

I struggled with this for a day and followed all the comments without it working.

The one thing that eventually worked for me was letting bitbucket create the private and public keys and using those instead of the ones I created myself. 

I then added the public key (as it says ) to the server's `~/.ssh/authorized_keys` file (as a new line) 

It all then worked.

Thank you, helped me a lot!

Like Mark Drew likes this

Thank you! Works for me!

Like Mark Drew likes this

Also worked for me too

Like Mark Drew likes this

Hello.. how do i let bitbucket create the ssh. i not that good with Atlassian products

@John Kabiu 

On the repository -> Repository Settings -> Scroll to Pipelines / SSH keys -> Generate

I was almost struggling for a couple of hours to transfer files through scp.. Finally, I could solve the issue based on Mark's response. Thanks.

Points to note:

1) I didn't remove my existing public key which I used to login

2) I generated one more key pair using the ssh key generator provided by bitbucket and appended that key to the authorized_keys under ~./ssh directory. So, now bitbucket pipelines will be using the keypair that was generated by using bitbucket cloud rather than the earlier key that I had provided.

3) Permissions I had set: 700 for .ssh dir and 600 for authorized_keys under .ssh directory

Like Mark Drew likes this

Hello team

I keep getting the same error, but with a GitHub repo, while running npm install https://shero.d.pr/l6fHt7

I have created the bitbucket keys but am not sure where to upload these on Github.

For me, the problem was at the target server. I needed to set `chmod 0775 ~/.ssh` so the server started accepting the SSH auth for the user.

user beware: this locked me out of my server

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,495 views 3 10
Read article

Atlassian Community Events