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.
4,467,821
Community Members
- Community
- Products
- Jira
- Jira Software
- Questions
- in VSCode: Error clongin repository (check log for more)
Installed Jira for VScode. First repository to clone I get
Error cloning repository (check log for details). There is no log file in the current folder.
1 answer
hi, have you dealt with the problem yet? I come across the same problem when I want to clone a repository.
You must be a registered user to add a comment. If you’ve already registered, sign in. Otherwise, register and sign in.
- Comment
Suggest an answer
Still have a question?
Get fast answers from people who know.
Was this helpful?
Thanks!
Atlassian Community Events
- FAQ
- Community Guidelines
- About
- Privacy policy
- Terms of use
- © 2023 Atlassian
HTTPS cloning errors
There are a few common errors when using HTTPS with Git. These errors usually indicate you have an old version of Git, or you don’t have access to the repository.
Here’s an example of an HTTPS error you might receive:
> error: The requested URL returned error: 401 while accessing
> https://github.com/USER/REPO.git/info/refs?service=git-receive-pack
> fatal: HTTP request failed> Error: The requested URL returned error: 403 while accessing
> https://github.com/USER/REPO.git/info/refs
> fatal: HTTP request failed> Error: https://github.com/USER/REPO.git/info/refs not found: did you run git
> update-server-info on the server?Check your Git version
There’s no minimum Git version necessary to interact with GitHub, but we’ve found version 1.7.10 to be a comfortable stable version that’s available on many platforms. You can always download the latest version on the Git website.
Ensure the remote is correct
The repository you’re trying to fetch must exist on GitHub.com, and the URL is case-sensitive.
You can find the URL of the local repository by opening the command line and
typing git remote -v:
$ git remote -v
# View existing remotes
> origin https://github.com/ghost/reactivecocoa.git (fetch)
> origin https://github.com/ghost/reactivecocoa.git (push)
$ git remote set-url origin https://github.com/ghost/ReactiveCocoa.git
# Change the 'origin' remote's URL
$ git remote -v
# Verify new remote URL
> origin https://github.com/ghost/ReactiveCocoa.git (fetch)
> origin https://github.com/ghost/ReactiveCocoa.git (push)Alternatively, you can change the URL through our
GitHub Desktop application.
Provide an access token
To access GitHub, you must authenticate with a personal access token instead of your password. For more information, see «Creating a personal access token.»
If you are accessing an organization that uses SAML SSO and you are using a personal access token (classic), you must also authorize your personal access token to access the organization before you authenticate. For more information, see «About authentication with SAML single sign-on» and «Authorizing a personal access token for use with SAML single sign-on.»
Check your permissions
When prompted for a username and password, make sure you use an account that has access to the repository.
Tip: If you don’t want to enter your credentials every time you interact with the remote repository, you can turn on credential caching. If you are already using credential caching, please make sure that your computer has the correct credentials cached. Incorrect or out of date credentials will cause authentication to fail.
Use SSH instead
If you’ve previously set up SSH keys, you can use the SSH clone URL instead of HTTPS. For more information, see «About remote repositories.»
Error: Repository not found
If you see this error when cloning a repository, it means that the repository does not exist or you do not have permission to access it. There are a few solutions to this error, depending on the cause.
Check your spelling
Typos happen, and repository names are case-sensitive. If you try to clone git@github.com:user/repo.git, but the repository is really named User/Repo you will receive this error.
To avoid this error, when cloning, always copy and paste the clone URL from the repository’s page. For more information, see «Cloning a repository.»
To update the remote on an existing repository, see «Managing remote repositories».
Checking your permissions
If you are trying to clone a private repository but do not have permission to view the repository, you will receive this error.
Make sure that you have access to the repository in one of these ways:
- The owner of the repository
- A collaborator on the repository
- A member of a team that has access to the repository (if the repository belongs to an organization)
Check your SSH access
In rare circumstances, you may not have the proper SSH access to a repository.
You should ensure that the SSH key you are using is attached to your personal account on GitHub. You can check this by typing
the following into the command line:
$ ssh -T git@github.com
> Hi USERNAME! You've successfully authenticated, but GitHub does not
> provide shell access.If the repository belongs to an organization and you’re using an SSH key generated by an OAuth App, OAuth App access may have been restricted by an organization owner. For more information, see «About OAuth App access restrictions.»
For more information, see Adding a new SSH key to your GitHub account.
Check that the repository really exists
If all else fails, make sure that the repository really exists on GitHub.com!
If you’re trying to push to a repository that doesn’t exist, you’ll get this error.
Error: Remote HEAD refers to nonexistent ref, unable to checkout
This error occurs if the default branch of a repository has been deleted on GitHub.com.
Detecting this error is simple; Git will warn you when you try to clone the repository:
$ git clone https://github.com/USER/REPO.git
# Clone a repo
> Cloning into 'repo'...
> remote: Counting objects: 66179, done.
> remote: Compressing objects: 100% (15587/15587), done.
> remote: Total 66179 (delta 46985), reused 65596 (delta 46402)
> Receiving objects: 100% (66179/66179), 51.66 MiB | 667 KiB/s, done.
> Resolving deltas: 100% (46985/46985), done.
> warning: remote HEAD refers to nonexistent ref, unable to checkout.To fix the error, you’ll need to be an administrator of the repository on GitHub.com.
You’ll want to change the default branch of the repository.
After that, you can get a list of all the available branches from the command line:
$ git branch -a
# Lists ALL the branches
> remotes/origin/awesome
> remotes/origin/more-work
> remotes/origin/new-mainThen, you can just switch to your new branch:
$ git checkout new-main
# Create and checkout a tracking branch
> Branch new-main set up to track remote branch new-main from origin.
> Switched to a new branch 'new-main'#497: cannot get client for: Jira
Authentication
bug
major
new
4
2020-10-15
3 hours ago
#756: Error on Pull Request creation and browsing
Bitbucket
bug
major
new
13
2022-08-22
10 hours ago
#803: Error fetching pull request details from Bitbucket
Bitbucket
bug
major
new
1
2023-01-24
2023-02-07
#538: Create branch as a local branch during «Start work»
Bitbucket
bug
major
new
2
2020-12-17
2023-02-07
#706: Jira multiple cloud
Authentication
bug
critical
new
14
2022-03-23
2023-02-06
#798: plugin does not parse correctly bitbucket repositories with a dot in the name and returns 404 errors when trying to connect through API
Bitbucket
bug
major
new
9
2023-01-19
2023-02-04
#769: An option to have file open in same pane when selecting «Edit this File»
Bitbucket
proposal
minor
new
2022-10-04
2023-02-03
#778: Error Fetching Pull Request Details BB Server/DC
Bitbucket
bug
minor
new
2022-11-16
2023-02-03
#811: While merging a Pull Request showing «Merging in source branch» instead of «Merging from Source Branch»
Bitbucket
bug
major
new
2023-02-01
2023-02-01
#801: pipeline don’t update anymore in vscode
Bitbucket
bug
major
new
2023-01-23
2023-02-01
#794: Updated comments show as [Object object] in bitbucket
Bitbucket
bug
major
new
1
2023-01-09
2023-01-31
#802: Jira and Bitbucket extension for VS Code — No more local Git repository detection
Misc
bug
major
new
3
2023-01-23
2023-01-31
#810: problem with repository who have a point
bug
major
new
2023-01-31
2023-01-31
#809: Multiple ssh keys for the same account
Bitbucket
bug
major
new
2023-01-31
2023-01-31
#808: default and allowed-values not part of pipeline schema
bug
trivial
new
2023-01-27
2023-01-27
#807: authentication error adding custom BitBucket site to Atlassian for VSCode
Authentication
bug
major
new
1
2023-01-27
2023-01-27
#806: «Create Jira Issue» has hidden requirement for Ext Issue Link. It should not require this field to be filled out
Jira
bug
major
new
2023-01-26
2023-01-26
#797: cannot get client for: Jira — Jira is disabled!
Jira
bug
minor
new
3
2023-01-18
2023-01-26
#21: Can not login into Bitbucket Cloud from VSCode
bug
major
resolved
9
2019-03-08
2023-01-25
#805: Invalid credentials
Authentication
bug
major
new
2023-01-24
2023-01-24
#804: Invalid credentials
Authentication
bug
major
new
2023-01-24
2023-01-24
#800: Bitbucket Pipelines Schema incorrectly throws error for configured parallel step
Misc
bug
minor
new
1
2023-01-22
2023-01-22
#799: Only show files with comments
Bitbucket
enhancement
major
new
2023-01-20
2023-01-20
#786: Cannot read properties of undefined (reading ‘uiType’)
Jira
bug
critical
new
3
2022-11-22
2023-01-20
#783: Cannot read properties of undefined (reading ‘getBitbucketCloudRepositories’)
bug
major
new
2022-11-18
2023-01-19
Slide 1
Most trusted JOB oriented professional program
DevOps Certified Professional (DCP)
Take your first step into the world of DevOps with this course, which will help you to learn about the methodologies and tools used to develop, deploy, and operate high-quality software.
Slide 2
DevOps to DevSecOps – Learn the evolution
DevSecOps Certified Professional (DSOCP)
Learn to automate security into a fast-paced DevOps environment using various open-source tools and scripts.
Slide 2
Get certified in the new tech skill to rule the industry
Site Reliability Engineering (SRE) Certified Professional
A method of measuring and achieving reliability through engineering and operations work – developed by Google to manage services.
Slide 2
Master in DevOps Engineering (MDE)
Get enrolled for the most advanced and only course in the WORLD which can make you an expert and proficient Architect in DevOps, DevSecOps and Site Reliability Engineering (SRE) principles together.
Slide 2
Gain expertise and certified yourself
Azure DevOps Solutions Expert
Learn about the DevOps services available on Azure and how you can use them to make your workflow more efficient.
Slide 3
AWS Certified DevOps Professional
Learn about the DevOps services offered by AWS and how you can use them to make your workflow more efficient.
rajeshkumar created the topic: ERROR: Error cloning remote repo ‘origin’
Error
Started by user anonymous
Building in workspace D:toolsjenkinsjobsMatrix-Fast-javaworkspace
Cloning the remote Git repository
Cloning repository github.com/scmgalaxy/helloworld-java-ant.git
> git.exe init D:toolsjenkinsjobsMatrix-Fast-javaworkspace # timeout=10
ERROR: Error cloning remote repo ‘origin’
ERROR: Error cloning remote repo ‘origin’
Finished: FAILURE
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
rajeshkumar replied the topic: ERROR: Error cloning remote repo ‘origin’
Solution 1: check if git is installed or not. Also git should be set in PATH
Solution 2: Go to http://localhost:8080/configure and Set the correct git executable path
see attached image as well….
How to Install git in Ubantu?
sudo apt-get install git
How to Install git in CentOS
yum install git
How to Install git in CentOS
git-scm.com/download/win && Set git executables in PATH
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
rajeshkumar replied the topic: ERROR: Error cloning remote repo ‘origin’
You can also install git automatically by selecting the checkbox as shown in pic
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
- Author
- Recent Posts
Mentor for DevOps — DevSecOps — SRE — Cloud — Container & Micorservices at Cotocus
Join my following certification courses…
— DevOps Certified Professionals (DCP)
— Site Reliability Engineering Certified Professionals (SRECP)
— Master in DevOps Engineering (MDE)
— DevSecOps Certified Professionals (DSOCP)
URL — https://www.devopsschool.com/certification/
My Linkedin — https://www.linkedin.com/in/rajeshkumarin
My Email — contact@DevOpsSchool.com
I’ve been running into this issue every time I run a repo init -u https://source.codeaurora.org/quic/le/le/manifest.git -b [branch] -m [manifest] command.
>>
>> repo 1.12.16
stderr:
>> gpg: Signature made Thu 01 May 2014 01:34:18 PM PDT using RSA key ID 692B382C
>> gpg: Can't check signature: public key not found
>> error: could not verify the tag 'v1.12.16'
fatal: cloning the git-repo repository failed, will remove '.repo/repo'
Then I installed the repo package via sudo apt-get install repo which seems to install the repo in /usr/bin dir so upon running $/usr/bin/repo init -u https://source.codeaurora.org/quic/le/le/manifest.git -b [branch] -m [manifest] , I now see:
repo: error: "git" failed with exit status 1
stderr:
>> gpg: Signature made Thu 22 June 2012 01:14:15 PM PDT using RSA key ID 692B382C
>> gpg: Can't check signature: public key not found
>> error: could not verify the tag 'v1.12.16'
fatal: cloning the git-repo repository failed, will remove '.repo/repo'
I tried this approach to no avail.