Teamcity to github List remote refs failed not authorized jgit

Question

Using github for windows on same machine, with same credentials works fine. Can pull/clone.

However teamcity installed as a windows service on the same machine, returns the following error

List remote refs failed: org.eclipse.jgit.errors.TransportException: https://github.com/my-private-repo.git: not authorized

score 28 · Accepted Answer · edited Oct 29 '14 at 11:52

28

In teamcity, in the project VCS Root, if the authentication method is based on ssh public/private key, then the fetch URL should be like git@github.com:.../repository.git. Using https:// in the fetch URL causes the error message:

List remote refs failed: org.eclipse.jgit.errors.TransportException..

to occur.

edited Oct 29 '14 at 11:52

Mark van Lent

12,641
4
30
52

answered Oct 29 '14 at 11:17

user4193783

296
3
3

I tried both ssh and https still the error occurs. `List remote refs failed: org.eclipse.jgit.errors.TransportException: https://gitlab.com/test-everyone/test-devops/test-it-processes.git: authentication not supported` My code is in `gitlab` – Rajat jain Mar 22 '19 at 09:30
1

In my case my repo doesn;t use username/password but username/token for auth. – SidJ Jun 06 '19 at 07:07

score 5 · Answer 2 · answered Jul 07 '19 at 03:34

5

In bitbucket, i resolved this by creating an App Password under settings, and used the app password instead of my bitbucket password

answered Jul 07 '19 at 03:34

sawe

1,141
14
24

bless u...these are the remaining mandatory characters – Red Bottle Mar 10 '22 at 08:24

score 3 · Answer 3 · answered Oct 29 '18 at 14:51

3

Had the same issue and resolved it by creating a Personal Access Token in Github and using it as a password in TeamCity.

answered Oct 29 '18 at 14:51

Fernando Moreira

785
4
16

score 2 · Answer 4 · edited Feb 23 '18 at 13:55

2

In case anyone else has something similar, it was the user credentials in GitHub, but I have not tracked down exactly which setting yet.

Using a different user within TeamCity works, even though I could perform a clone/fetch/pull and ls remote on command line (as the problem user).

edited Feb 23 '18 at 13:55

James Skemp

8,018
9
64
107

answered Apr 09 '14 at 12:33

NimChimpsky

46,453
60
198
311

score 2 · Answer 5 · answered Mar 17 '16 at 16:41

2

Having same error with Stash (=Bitbucket server) and solution was to give the user specified in TeamCity the permissions in Stash to access the repository. Permissions are per-repository.

answered Mar 17 '16 at 16:41

Ricardo stands with Ukraine

4,508
2
42
59

Can confirm this worked for gitlab as well. Error message there was "List remote refs failed: cannot locate repository (repository url)/git-upload-pack not found" – Mark Allen Aug 13 '19 at 22:13

score 1 · Answer 6 · answered Jun 01 '19 at 21:34

You can use SSH KEYS to allow you to access the Azure TFS GIT URL, or you can modify the settings in "Alternative Credentials" by checking "Enable alternate credentials" so you can access the repository by just using a username and password.

First in Azure DevOps go to your project:

Then choose Security in the RHS menu:

Finally choose "Alternate Credentials" in the LHS menu and click the "Enable authentication alternate credentials" where you will then put in your username and password:

Please beware that this is less secure than using the SSH KEYS.

score 1 · Answer 7 · answered Mar 15 '22 at 09:23

To anyone encountering this issue with using Bitbucket.

Since March 2022, you cannot use your personal credentials to connect your apps to bitbucket anymore. You need to create an app password (see here how to do it).

The identifier will not be your email adress but your Bitbucket username.

score 0 · Answer 8 · answered Sep 21 '16 at 17:45

I had the same error for a git server hosted on IIS.

The problem came on the scene after installing 'basic authentication' for the IIS. After that, the new authentication method 'basic authentication' was enabled (seems to be the default) for the git server's website. Disable 'basic authentication' solved the problem.

score 0 · Answer 9 · edited Feb 23 '18 at 18:56

Maybe not that related, but you may come here by the keywords "teamcity, github, list remote refs failed."

For those whose server is behind a proxy, please set the proxy for TeamCity server according to Connection time out: github.com

The main idea is:

To enable TeamCity to use proxy, an environment variable has to be created:

Name: TEAMCITY_SERVER_OPTS

Value: -Dhttp.proxyHost=192.168.0.1 -Dhttp.proxyPort=80 -Dhttps.proxyHost=192.168.0.1 -Dhttps.proxyPort=80

score 0 · Answer 10 · answered May 24 '18 at 18:23

0

Try to make push/get with same credentials with local git client it could provide more details, which could be related to credentials.

This was to me since TeamCity showed same error and these solutions didnt worked.

answered May 24 '18 at 18:23

valentasm

2,137
23
24

score 0 · Answer 11 · answered Dec 21 '20 at 10:09

0

Had the same problem with my Repo in Azure DevOps so I went to Clone then Command line selected HTTPS, Copied the url, Username and password which I used in TeamCity.

answered Dec 21 '20 at 10:09

tmndungu

320
4
17

Teamcity to github List remote refs failed not authorized jgit

11 Answers11