Permission Denied Sourcetree

If you want to access GitLab via SourceTree, you can connect it with an account profile now. Another method is to connect GitLab by using the clone function with SSH key.

What Will We Learn (Method 1)

The permission denied comment is attached to each individual file. What if I was tremendously wrong? What if this has nothing to do with my user profile having permission to use Git? What if, like the output suggests, it has everything to do with file permissions. Permission denied (publickey). Fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Fatal: Could not read from remote repository. 上記から、SSHの公開鍵認証に失敗していると推測されます。 SourceTreeのメニューで「ツール」→「SSHキーを追加」で鍵を追加したか.

  • Access GitLab with personal access token

What Will We Learn (Method 2)

  • Create SSH key
  • Access GitLab via SourceTree with SSH key
Sourcetree

Method 1: Connect with Remote (Account Profile)

Since SourceTree 3.0, it adds support for additional remote hosting services. They are GitHub Enterprise, Microsoft Visual Studio Team Services, and GitLab (Cloud, CE, EE).

Create Personal Access Token

To connect GitLab with Remote, personal access token is required for authentication. To create personal access token, login GitLab and go to Settings.

After that, select Access Tokens from the sidebar. You will create your personal access token here. Give access token a name. You are able to set an expiry date for your access token. By leaving it blank, access token will never expire. Next check the api and read_user checkbox, it is required for SourceTree to connect to GitLab remotely. Click on Create personal access token to complete the setup.

Next open up your SourceTree, click on Remote and click on Add an account.

Select GitLab as the hosting services, and choose HTTPS as the Preferred Protocol. Click on Refresh Personal Access Token.

You will be prompted to enter the username and password. After entering the username and password then press OK to continue.

Do take note that email address you used to login GitLab is not your username. If you do not know your username. Go to GitLab and click on the top right profile icon. The text after @ is your username. In this example, it would be aword-test.

Furthermore, the password is your personal access token code. It only shows you once you created your personal access token. Make sure save your personal access token code in a safe place.

Then you have completed the steps to connect GitLab with SourceTree. If you connect successfully, you will able to see your repositories in SourceTree.

Sourcetree Permission Denied Publickey

Method 2: Connect with SSH Key

This method is useful for users who are not using SourceTree 3.0 and above.

What is SSH Key

The Secure Shell (SSH) key is based on the principle of Public-key cryptography. It is used as a way of authentication. By generating an SSH key pair, you will get a private key and a public key. You can image public key as a padlock. You can distribute it to any systems on the Internet. Private key is like a key of the padlock. You should keep the private key securely and avoid it from being compromised. To access any system with public key, you need to use the private key to authenticate yourself.

Create SSH Key

To create SSH key, you need to generate your own SSH key with SourceTree. Go to Tools and select Create or Import SSH Keys.

Click on Generate to create SSH Key. Move your mouse cursor within the PuTTY Key Generator continuing to generate the SSH Key.

After SSH Key is generated, type your own Key passphrase for your SSH Key. Key passphrase is like a password to protect your SSH private key. Save your public key and private key for future use.

Add SSH Public Key to GitLab

To add your SSH Key to GitLab, you need to log into you GitLab account. Click on your profile icon on the top right corner, then select Settings. Click on SSH Keys on the side menu.

Copy your public key inside your PuTTY Key Generator, then paste it into GitLab. Click on Add Key to add your SSH Key into the GitLab.

Add SSH Private Key to SourceTree

Permission Denied Sourcetree

To add private key to SourceTree, Click on Tools then click Launch SSH Agent…

You will find SSH Agent named as Pageant on the taskbar. Double click on Pageant.

Sourcetree Permission Denied

Now click on Add Key. Add your private key which have been saved earlier.

Clone Repository to Access GitLab via SourceTree

Go into your projects in your GitLab. Copy the SSH URL.

In SourceTree, click on Clone. Paste the repository URL into Source Path. Click on Clone, you have successfully connected GitLab with SourceTree. Now you are able to pull and push your code to GitLab with SourceTree.

Sourcetree Gitlab Auth Blocker

In Sourcetree, when I select “GitLab.com” (private token auth type is selected by default), I enter my Gitlab username and password (SSH, id_rsa.pub). I cannot change the id_rsa.pub to the recommended ED25519 option.

War thunder f11f op The F11F-1 Tiger is a supersonic carrier-based jet fighter equipped with the Allison J65-W-18 engine. The plane is able to reach Mach 1 speed in level speed, making it one of the fastest planes at its battle rating, but getting it past that speed will require some diving.

Even though the correct user name and password are entered, I get the following error:
“Login error, We couldn’t connect to GitLab with your (username) credentials. Check your username and try the password again.”

I’ve tried connecting via Gitlab CE and also through HTTPS. Nothing seems to work though I can git commit via Terminal.

Sourcetree Permission Denied Pull

Has anyone else encountered this auth issue with GitLab? I was formerly on GitHub and didn’t have any issues with auth. I did enable 2FA if this causes problems with Sourcetree?