Can't use forward-agent ssh in pipelines?

With the new SSH Keys Pipeline settings, i can easily get ssh access to my server from pipelines. Which is great.

I use to deploy my JS code to my server. It logs into my server (which works because of the ssh keys), then pulls the git code from bitbucket, which doesn't work because it has no access. Sad panda :(

pm2 supports forward-agent, and this works from my local machine. I added the Pipelines ssh-key to my project, so it gets read access. Still no luck. Whe i debug the ssh connection to bitbucket, I can see


debug1: Authentications that can continue: publickey

debug1: Next authentication method: publickey

debug1: Trying private key: /home/appuser/.ssh/id_rsa


etc. which is my server user.

Whilst running this locally, my server will return my local id and get a successfull connection with it.

So i can only imagine, forward-agent is not working. Any ideas?

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

695 views 5 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you