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

Failed to add an account in Gitlab CE installed in Docker (Qnap/Container Station)


Hello everyone.
I'm in need of hints on how to solve a problem.
Please help me with your knowledge if you can.

Sourcetree version is 3.3.9.

Setting up a connection to has been successful.

Hosting Service: GitLab CE
Preferred Protocol HTTPS

Personal Access Token is acquired.

After a refresh PAT, enter my gitlab-ce username and PAT in the Sourcetree Personal Access Token request pop-up, but I get an error it just says "Authentication failed" and I don't know why in detail.



On Windows Terminal, the ssh connection also succeeds.


$ssh -p 10022 -l git -i C:\Users\.ssh\id_rsa

PTY allocation request failed on channel 0
Welcome to GitLab, @****!
Connection to closed.


This operation has the same result for both standard Windows SSH(OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5) and SSH(OpenSSH_8.2p1, OpenSSL 1.1.1f 31 Mar 2020) installed with Sourcetree.

Do I need a different configuration for connecting to Gitlab CE on Docker than

This POST is translated by Deepl!

1 answer

I got connected. So tired. I was so dumb.

It was a simple thing, but even if the protocol was https authentication, I had to specify the host URL as http://FQDN:10080.
I was convinced that SSL was not working properly.


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events