Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Contact Support
GitKraken Status  

TFS – Not authorized exception when Jira works thru proxy

Problem

Technical error reported from the git client:

org.eclipse.jgit.errors.TransportException
http://127.0.0.1:8080/tfs/DefaultCollection/_git/console-app/: not authorized

Attempt to connect to the Git server failed. This may be because of invalid username and password or may be because of a network error.

Diagnosis

The above error is similar to “service=git-upload pack not found” type errors and happens when the credentials being used by the Git Integration app don’t have access to clone the specified Git repositories. There’s the possibility to see the repositories from the TFS API (they are actually listed) but unable to access them via the Git protocol.

Solution

If you are using proxy, configure your Jira with the following parameter format:

Dhttp.proxyHost=<your-proxy-host>
Dhttps.proxyHost=<your-proxy-host>
Dhttp.proxyPort=<your-proxy-port>
Dhttps.proxyPort=<your-proxy-port>
Dhttp.proxyUser=*****
Dhttps.proxyUser=*****
Dhttp.proxyPassword=*****
Dhttps.proxyPassword=*****
Dhttp.nonProxyHosts=*.some.mask|localhost|1.1.1.1<someIP>
Dhttps.nonProxyHosts=*.some.mask|localhost|1.1.1.1<someIP>

Enter <your-git-server-host> to nonProxyHosts entries.

Usually, the nonProxyHosts are the list of servers that the JVM should not send through the proxy. This is because they are in the same data center and a private address.

Wildcards are supported:

-Dhttp.nonProxyHosts=*.git.server.host
-Dhttps.nonProxyHosts=*.git.server.host

Or instead, use pipe and quotes for multiple hosts:

-Dhttp.nonProxyHosts="your.git.server.host1|your.git.server.host2"
-Dhttps.nonProxyHosts="your.git.server.host1|your.git.server.host2"
Contact Us
If you still have a question – reach out to our Support Desk or email us at [email protected].

 

More articles about troubleshooting, workarounds and solutions

Why I am getting the error, “git-upload-pack not permitted”?

Avoid OutOfMemory exceptions by configuring or memory allocation with Jira to accommodate large repositories

Cannot auto-deploy some tracked repositories: Specified origin is incorrect or not supported

Connection Reset when Accessing the Database

“Dangerous use of multiple connections” error on local database

Duplicate entry 0 for key PRIMARY exceptions in log

Error while reindexing – Java heap space / Object too large, rejecting the pack

Error creating git branches and also using NFS

Fix performance issues for nested cloned repositories with enabled Git Service Permissions mode

Fixing reindex issues using Indexing Queue Viewer

Gitolite integration: Why the Git integration app not see the master branch?

Health Check: Database Collation

Indexing error – Too many open files

Installation fails when installing manually

Jira index error: IndexNotFoundException: no segments* file found

Malformed input or input contains unmappable characters

Personal access token failing Azure DevOps integration with Not Authorized error

Problems with shared home on Azure Storage

Pull request index error: org.json.JSONException

Repositories missing from Azure DevOps integration

“Service proxy has been destroyed” exceptions in log

SQLException ‘Incorrect string value’ in merge requests

SSH key file format is invalid

TFS – Not authorized exception when Jira works thru proxy (this page)

Unexpected exception parsing XML document from URL error in log

Why don’t I see the Create Branch or Pull Request features?

Have feedback about this article? Did we miss something? Let us know!
On this page