Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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
Community Members
Community Events
Community Groups

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
AUG Leaders

Atlassian Community Events