Error setting certificate verify locations visual studio

Error setting certificate verify locations — Github

I am having problem accessing github repository through Git Bash.

2 days ago I was able to push/pull the repositories. Then

1) I created an account on gitlab.com

2) I generated ssh key on my local pc following GitLab and SSH keys using git bash on windows

3) After this I did not create/pull/push any repository on gitlab.

Today I make few changes in a code (that is deployed on github), when I try to push that code I get following error

There is no ssl folder in libexec

Also no file/folder changed in Git folder since Jan 2017

It seems like git-bash issue, not sure. Can anyone help ?

6 Answers 6

In my case, on windows, It was not working after setting of name , e mail as well as certificates path for git config. following command run from command prompt fixed this issue.

git config —global http.sslcainfo «C:Program FilesGitusrsslcertsca-bundle.crt»

path of your ca-bundle.crt may vary in your case.

First, creating ssh keys won’t help for an HTTPS url.
Keep those keys, but if you want to use them, you would need to put existing ssh keys to your github account then

Second, regarding the cert error, try to push from a simple CMD, using a simplified PATH as I do here, with said PATH referencing the very latest Git for Windows.
For that, uncompress PortableGit-2.16.1-64-bit.7z.exe anywhere you want.

On openSUSE 15.2 WSL (Windows Subsystem for Linux), I fixed this error by:

/etc/pki/tls/certs/ca-bundle.crt was the certificate file mentioned in the error. I noticed the file was missing. The full error in my case was:

This command, Then your usual git clone «url» thing.

It can cause trouble in future to pull/push the secure repository. So disable at your risk.

For windows i found the same error having cloned successfully using GitHub desktop . When I tried doing a sync using Visual Studio, the error appeared.

My GitHub desktop runs 64 bit, but it has its git folder was placed in the Program (x86) folder (why?) The VS is also a 64 bit application, but has the certicate more naturally in the Program folder.

Solution: I copied content of C:Program Files (x86)Gitmingw32ssl to C:Program FilesGitmingw64ssl

And the Git of VS worked perfect

One of my team member came to my seat with this error and I have identified that git was not installed on the system that’s why he was getting this error.

Although Microsoft does suggest to install Git for Windows but you don’t have to install it for the Visual Studio 2013 or 2017 as the same page ends with:

Visual Studio offers a great out of the box Git experience without any additional tooling. Learn more in our Visual Studio Git tutorial.

Git comes as an optional component for Visual Studio 2019 ,and you need to manually install it to work with Git servers such as Team Foundation Services, GitHub, and BitBucket. You can find more details about this here

Источник

Laravel 5 Socialite — cURL error 77: error setting certificate verify locations

I am using socialite in Laravel 5 to setup facebook login. I followed the instructions carefully until I got stuck with the following error

so I found the this answer to fix it which indeed passed but then I got this error

Any ideas what’s the cause of this error?! and how to fix it?!

24 Answers 24

I got stuck on this problem as well. It turned out that I had the path to my certificate set incorrectly in my php.ini file. Forgot the .txt extension.

What I changed it to:

Hope this helps.

Change setting in php.ini file:

cURL error 77: error setting certificate verify locations: CAfile: C:xamppapachebincurl-ca-bundle.crt CApath: none (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

This works well for me:

1. Download the certificate from: https://curl.haxx.se/ca/cacert.pem
2. Rename the cacert.pem file into curl-ca-bundle.crt
3. Copy the file into path/to/xampp/apache/bin
4. Restart apache

I experienced some issues following instructions in regards to error 77.

On Windows 7, depending on your security settings — the file downloaded may be blocked. See screenshot:

Once I unblocked the file and ensured proper user access rights, I also had to put the file in the following location:

In addition to changing php.ini per the other posts on this issue.

After completing the above steps, restarting Apache via the XAMPP Control Panel, the error was resolved.

Save this certificate (https://curl.haxx.se/ca/cacert.pem) as cacert.pem.txt in C:xamppphp

Then it works fine!

1. Download from (https://curl.haxx.se/ca/cacert.pem)
2. Change the name ‘cacert.pem‘ to ‘curl-ca-bundle.crt‘
   (after that, move it to the path ‘C:xamppapachebin’)
3. In ‘php.ini‘, remove ‘;‘ in the following line: curl.cainfo=»C:xamppapachebincurl-ca-bundle.crt»

That works for me.

Checkout double quote on php.ini file: if you copied and past from the Web maybe you got wrong double quote:

In your php.ini file, you should also update your

with the same cacert.pem link you used in updating your

Have a look at mine before and after

this fixes the cURL 60 error

fixes the cURL 77 error.

NB: Do not forget to restart your server before trying it out.

For those who wish to find their php.ini file, use this command after you cd into your application

You need to replace the existing certificate with the other one here. After that:

• Extract and add it to xamppphpext
• Open xamppphpphp.ini
• Add this line curl.cainfo=’location from the first step’ to the end of the file.
• Restart and it should be working now.

This is the source link.

For windows

I had same problem after i updated php on window 2008. Suddenly all my php codes stopped working. What i did, i opned php.ini then i found a line

and i changed to

curl.cainfo = «C:Program Files (x86)PHPv7.0cacert.pem» (remember to remove ; before curl.cainfo)

and everything went to normal. What you need is to download a cert file cert.pem and place it anywhere on your server and change the line as i did in php.ini

This same problem with me in php version 8.0.3 on windows : Solution was I had to uncomment and set openssl.capath=path of certs in php.ini file.

I already set openssl.cafile so it was not throwing error for that but oepnssl.capath was not set sot error was there.

I read every thread I could find and this one provided the missing piece.

Background: I encountered this issue will trying to get Drupal 8 to check for available updates on a fresh development environment (wamp based).

1. Get a copy of the Certificate data from Mozilla, it can be found here: https://curl.haxx.se/ca/cacert.pem If you want to know more about what this is read this: https://serverfault.com/questions/241046/what-is-the-cacert-pem-and-for-what-to-use-that
2. Save the file as «cacert.pem.txt» not as «cacert.pem» This was the missing piece, thanks LyleK!. I have no clue why but you must have the .txt extension on the end or it does not work.
3. Explicitly add the path to the location of the «cacert.pem.txt» file to your php.ini

If you are using a wamp stack restart it. You should be good to go.

Источник

Unable to pull/push in git repository

I am getting this error when I pull or push my code.

Please guide me to fix this.

23 Answers 23

When using https you will need to supply password or using a certificate. In your case looks like the certificate is not a valid one.

Try fixing it like this by telling git where to find the certificate:

Alternatively, you could disable SSL checks:

Set this in your config to disable it only for the given url and not for all requests

http.sslVerify

Whether to verify the SSL certificate when fetching or pushing over HTTPS.

http.sslCAInfo

File containing the certificates to verify the peer with when fetching or pushing over HTTPS

I once had the same problem. My problem occured after re-installing git for windows. I’m using git for windows 64-bit on windows 10.

I found out that the installer did not install git anymore in C:/Users/[USER_NAME]/AppData/Local/Programs/Git . Instead it installed it under C:Program FilesGit .

Nevertheless the old config file C:ProgramDataGitconfig was not edited by the installer. This file still contains the old path so I edited it manually.

E.g. on my system I used

maybe you will have to use Program Files instead

EDIT

Like DS said in his comment

C:ProgramDataGitconfig needs to be edited as Administrator.

E.g. right click on notepad and select «Run as Administrator» then open the file.

I was also facing this problem in windows and running git using gitbash. I just reinstalled gitbash, And gitbash automatically managed git certificate and its path needed.

In version 2.x of git-bash The path to the .crt has changed to ../Git/mingw64/ssl/certs/ca-bundle.crt. I had to update this manually in git-bash with

Switch off your SSL by running this command

This issue might occur when git client is not able to find trusted CA for ssl. If you are in windows, try reinstalling it from https://gitforwindows.org/.

During the installation, select «Use the native Windows Secure Channel library» option. That option will allow you to use your company’s internal Root CA certificate instead of default ca-bundle.crt

• will solve the problem after that Pop-up window appear to enter your username and password make sure valid .

If your git version is 2.8.1.windows.1,this may help you. First , you need to locate your git home directory,mine is D:SDKGit.Just in the same directory,you can find folder «usr»,open it and goes to sslcerts,you can find the certificate:ca-bundle.crt.

Then open console,execute:
git config —system http.sslcainfo «D:SDKGitusrsslcertscabundle.crt»

This will do the work while moving from GIT 2.x clients to 2.5.x:

Looks like after installing a new version of GIT client, it changes the path it looks for certificates from something like this:

to something like this:

To fix this, just copy the ‘ssl’ folder to the new location and it’ll work like a charm!

Go your git directory and move the mingw64/ssl folder to mingw64/libexec/ssl

This thread is a lot of blind-leading-the-blind answers. I’m just one more blind man here, but I just had the same issue and solved it by following this easy article. As I understand the original question, git is trying to find an SSL cert file in order to use the HTTPS protocol, and failing to find the file. Most of the answers here seem to focus on «well, just disable SSL then,» rather than replacing the file correctly.

This incantation should generate the cert file and put it in the correct location for git on cygwin:

In case you monkeyed with your git config (like I did) and need to set it BACK, this should do it:

Источник

Github: error cloning my private repository

I’m trying to clone my GitHub project using the https-URL, but it fails with an error:

What am I doing wrong?

27 Answers 27

I have seen this on Windows, with msysgit 1.7.2.3. You have to fix the path to bin/curl-ca-bundle.crt. I had to specify the absolute path, using back-slashes:

This will result in changes to [git-install-dir]/etc/gitconfig file, which may be edited directly, too.

I solved the problem installing the Git from: https://git-for-windows.github.io/ Locate the cert file path:

Configure the Git path:

git config —system http.sslcainfo «D:Program FilesGitmingw64sslcertsca-bundle.crt»

If you use MSYS2.

Just install the certificate packages with the following commands:

32 bits

64 bits

If you were using Cygwin, you might install the ca-certificates package with apt-cyg:

Will solve the problem. After that a Pop-up window appears to enter your username and password

SOLVED: I got this error when I installed an update to the Git windows installer. What happened is that I did not install it with administrator rights, so Git was installed in «C:Usersmy_nameAppDataLocalPrograms» instead of «C:program Files». re-installing Git as administrator allowed to put it in C:program Files and everything went fine again !

This worked for me (I’m using Manjaro linux). I run the cmd to view ca-certificates:

But actually i found the certificates at the path:

Then add the config into

/.gitconfig (if not existing, create it):

git config —system http.sslcainfo /bin/curl-ca-bundle.crt

This works. You don’t have to give full path.

I faced this while git pull. For mine edited the global git config file that fixed problem.

Goto your home folder and open .gitconfig file. Usually C:Users.gitconfig

If the file is not there create it

[http]
sslcainfo = E:systoolsgit-1.8.5.2bincurl-ca-bundle.crt

There you have to given your own git installation path. I have used portable version of git here.

Then git clone / pull it will work.

In my win10 case I have two versions of .gitconfig

• the first one is in C:Program FilesGitetc
• the second is in C:Users

indeed makes changes to C:Program FilesGitetc , but git somehow uses config in C:Users

So with notepad I changed the second one .gitconfig and git finally took right configuration and got working.

If you are using the Git command shell that installs with the GitHub for Windows app then this and various other problems can show after an update. Just start the Git Hub windows app and shut it down again. The shell will then work OK again. The problem is that the update does not complete until the windows application is run. Just using the shell on its does not trigger the update to complete.

I’ve seen this on my Github for Windows.

I recommend uninstalling Github for Windows and installing it again.

Before this, I tried several ways with no success, but this solution worked for me!

On Windows using msysgit I had this error and the cause was my additions of our corporate proxy certificates.

If you edit your curl-ca-bundle.crt you have to get sure about your lineendings. In case of the curl-ca-bundle you have to use Linux-Style lineendings.

You can use notepad++ to convert the lineendings to Linux (linefeed).

On a side note, this issue can happen in Windows if the user who is trying to use git is different than the user who installed it. The error may indicate that git cannot access the certificate files. Installing git as the administrator and using @rogertoday’s answer resolved my issue.

I found a good solution for adding/updating the CA certificates on RHEL/CentOS 6 which is the root cause reported issue.

Since they become outdated distros, the cacert authorities in that system has not been updated until executing the command sudo yum update .

Didn’t realize the issue until the GIT_CURL_VERBOSE mode shows the cacert path issue.

I encountered this error after updating to Visual Studio 2019 16.10.2 (from 16.10.0), whereas previously Git was working correctly.

I do not have Git installed separately. (Or, put another way, I only use Git as part of Visual Studio.)

I solved this problem by locating the file «ca-bundle.crt» at «C:Program Files (x86)Microsoft Visual Studio2019ProfessionalCommon7IDECommonExtensionsMicrosoftTeamFoundationTeam ExplorerGitmingw32sslcertsca-bundle.crt» , and then copying it to the folder it was indicating it couldn’t be found at, «C:Program FilesGitmingw64sslcertsca-bundle.crt» .

Do note that I had to create the «mingw64sslcerts» directories, as they did not previously exist.

After copying the file there, Git was able to sync once again immediately without restarting Visual Studio.

Источник

$ git pull origin master
fatal: unable to access 'https://xxxxxxxxxxxxxxx': 
      error setting certificate verify locations:
CAfile: C:/Users/abc/AppData/Local/Programs/Git/usr/bin/curl-ca-bundle.crt
CApath: none

23 ответа

Лучший ответ

$git remote remove origin
$git remote add origin git@github.com:UserName/repo.git

 git config --global http.sslverify "false" 

git config --system http.sslcainfo "C:Program Files (x86)gitbincurl-ca-bundle.crt"

git config --system http.sslverify false

[http]
     sslCAInfo = C:/Programme/Git/mingw64/ssl/certs/ca-bundle.crt

     sslCAInfo = C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt

// Add the certificate to your configuration file
git config --system http.sslcainfo "C:Program Files (x86)gitbincurl-ca-bundle.crt"

// or switch off SSL checks completely by executing:
git config --system http.sslverify false

[http "https://weak.example.com"]
    sslVerify = false

C:Users[USERNAME]AppDataLocalGitHubPortableGit_[portable code]usrsslcerts

// Add the certificate to your configuration file
git config --system http.sslcainfo "[LOCATION_SPECIFIED_ABOVE]/cabundle.crt"

 git config --global http.sslcainfo "/path/to/Git/mingw64/ssl/certs/ca-bundle.crt"

C:Program FilesGitmingw64

C:Program FilesGitmingw64libexec

$ curl -sL http://ca.pdinc.us > /etc/pki/ca-trust/source/anchors/ca.pdinc.us.pem 
&& update-ca-trust

$ git config --global http.sslcainfo "/etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt"

$ which git

Recently I came across an excellent blog post from Jethro Seghers that covered getting started with Office 365 PowerShell Automation. In the post Jethro walks through the process of setting up Visual Studio Code to work with Visual Studio Services. The process uses Git as the broker. The end result is that your scripts can be stored in a secure source repository.

In following the post I learned several lessons that I thought I’d share.

Installing GitHub Desktop

When you install GitHub Desktop it will want you to create a repository when it starts up. I recommend that you cancel the pop-up and select ‘Clone a repository’ from the main screen:

One thing that Visual Studio Services does not make easy is to get the URL for your repository. The URL is displayed when you first create a project but thereafter it is not that obvious to find… The easiest way is to go to the ‘Code’ section in Visual Studio Services and then select the relevant project from the ‘Files’ tab. You can then grab the URL from the browser address bar. (You’ll need the full URL inc. the https:// bit):

You can then use the URL to clone the repository:

If this is the first time that you are using Git then I recommend that you manually create a new folder for all of your work somewhere on your local drive (you can do this with File Explorer – no special tools required). DO NOT use OneDrive. If you do use OneDrive you will get file conflict errors when Git attempts to synchronise the local and source repositories.In the image above, all of my repositories are stored as sub-folders in DocumentsGitHub.  The other aspect is that the cloning process will want to add the repository as a new folder which uses the repository name. You do not need to use the repository name. You can replace it with something shorter or meaningful. In the earlier Visual Studio Services image you can see that I used spaces when creating the project. This might look good in the browser but in reality those spaces are %20’s and they (a) make the folder path longer (b) look amateurish. Remember the cloning process will not work if a folder of the same name is already present.

Validation

You can validate that the set-up is complete by viewing the ‘History’ tab in GitHub Desktop and performing a ‘Fetch’:

You might notice that the ‘Fetch origin’ state is ‘Never fetched’. Tap on the Fetch origin button and after a brief period where the arrows spin the status should change to ‘Last fetched…’:

If this process fails then it is likely that you have authentication challenges.

Authentication error #1

When cloning or fetching the repository you might encounter an error where you need to sign into Visual Studio Services but for one reason or another your credentials are not accepted. I get that a lot as I have a personal Visual Studio account that shares its primary email address with my work account. As a result when I first set up a clone from my work machine I am redirected to use my work sign-in which promptly fails. The temporary work around is to use a Personal Access token. Once you have Visual Studio Code set up you can delete the Personal Access token as the module in Visual Studio Code does a better job with authentication.

Configuring Visual Studio Code

The process is straight forward – install the extensions and locate the local repository. When you identify the local repository the Visual Studio Team Services module will take over. You can use the ‘Open folder…’ option from the Start screen to browse to your local repository:

On selecting the folder you might be asked to sign into Visual Studio Services. If you’ve resorted to using a Personal Access token when setting up GitHub Desktop you should be able to sign in with your usual credentials rather than the token. Once signed in you can delete the personal token. Once authenticated your files will appear in the Explorer view:

The repository can be updated using the controls in the Sources view:

For example the can be used to commit all changes to the source repository. All should be fine and you can start coding but you might encounter another authentication error when undertaking a pull, push or sync requests…

Authentication error #2

If when pushing, pulling or synchronizing your repository an error like this appears:

then as northerners would say you have “trouble at t’mill”. You can see more (unhelpful) detail by viewing the output by selecting ‘Open Git Log’ from the dialogue. The log is also visible from ellipses in the Sources view.

On inspection of the output you’ll probably spot a ‘error setting certificate verify locations’ error.

This error is associated with the SSL certificates that are bundled with Git. In particular the default ‘ca-bundle.crt’ certificates. Your initial response could be to triage by checking that the certificate is present at the location detailed by the ‘CAfile’ value. My advice is to not bother. It is highly likely that you will find that the path is wrong. It looks like when they updated Git they moved the default location but forgot to change the code. You’ll spend hours working out how to change it to the correct location only for more errors to occur e.g. ‘unable to get local issuer certificate’ . You’ll then spend more time scouring the web and following dead ideas. Do not bother.

The fastest fix is a clean installation of Git and Git Desktop.

1. Uninstall Git
2. Uninstall Git Desktop
3. Restart your machine
4. Reinstall Git with administrator rights (this is critical – see later)
5. Reinstall Git Desktop

IMHO there are two critical items that combined can cause the error:

1. Not installing Git using the ‘Run as administrator’ option
2. Using the bundled certificates

As mentioned earlier the path to the bundled certificates is wrong. My recommendation is to use the certificates that are native to your machine as this avoids the path error. As you work through the Git setup screens pay particular attention to this one:

Pick the option to ‘Use the native Windows Secure Channel library’. Choosing the ‘Use the OpenSSL library’ option leads to path problems.

I’ve not tried it but it looks like you can rerun the Git setup using the installer without uninstalling first. If you’d rather dig deeper into solving the issue then I would start with SSL certificate problem: Unable to get local issuer certificate as once you fix the path you’ll probably get a new error or two… Usefully the uninstall process seemingly does not remove the connection details for your repositories and so you will not need to setup Git Desktop or Visual Studio Code again.