This is part two of our Git Error Codes series. You can see all the topic in the series below…
- Git Error Codes - Definitions & Solutions (Part 1)
- Git Error Codes - Definitions & Solutions (Part 2) → We’re here
- Git Error Codes - Definitions & Solutions (Part 3)
- Git Error Codes - Definitions & Solutions (Part 4)
The error codes in this topic include:
Can’t connect to any repository: not authorized (this post)
Cannot open git-upload-pack
/api/v1/git/branch java.net.UnknownHostException - “Name or service not known”
Let’s look at the solution for the code Can’t connect to any repository: not authorized
Definition
No permission to commit to Git Repo
Stage
Execution
Root Cause
You entered the wrong Git credentials (wrong username/password)
Solution
- The Git username is not the same as your GitHub username. You need to make sure to check under your profile to make sure it’s correct.
The password needs to be your Personal Access Token. See Managing your personal access tokens - GitHub Enterprise Server 3.4 Docs
Today let’s take a look at the Cannot open git-upload-pack error
Definition
Our TestOps cannot connect to your Gitlab repo due to access permission.
Stage
Integration
Root Cause
You are working under restricted network environment or using Gitlab server (which we has not officially supported yet).
Solution
You can contact your IT team to whitelist the following IP addresses: (if you are under VPN)
- 52.45.203.41
- 52.203.34.201
- 35.172.81.5
and domains from Network security errors | Katalon Docs.
If the issue still remains because you are using Gitlab server, you can try changing the Source Type into Others to see how it works. If you are still having issues, don’t hesitate to Ask the Community to let us know! 
Today we will take a look at the /api/v1/git/branch java.net.UnknownHostException - “Name or service not known” error
Definition
TestOps could not define the repo name through the git URL that you input in.
Stage
Integration
Root Cause
- Incorrect Clone URL.
- As a result of the high security user environment, your git server is incapable of locating or observing remote servers on the internet.
Solution
- Contact your IT department to publish the repository on the internet so TestOps can detect it.
- Follow this guide if you happened to use the incorrect Clone URL.
