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

Git private key authentication fails with "BEGIN OPENSSH PRIVATE KEY" format

I had troubles setting up a git repository against Gitlab.

The connection test failed with "Cannot decode connection params" while a test checkout provided the following error in the stack trace:

Caused by: unrecognised object: OPENSSH PRIVATE KEY

I found out that i needed to convert my key file to an older format that contains "BEGIN RSA PRIVATE KEY" instead of the "BEGIN OPENSSH PRIVATE KEY" my key file originally contained.

Since the original key file was created as per Gitlab instruction, and worked in many other scenarios (including a local shell git test with the bamboo user), I wonder if my setup is broken somehow? Please note that I use the official Bamboo docker container.

1 answer

0 votes



as workaround you can mount the authentication parameters into docker container :)


Hence you key will work



Gonchik Tsymzhitov

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 9.0 is now available

Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...

311 views 0 7
Read article

Atlassian Community Events