fatal: unable to access xxx server certificate verification failed. CAfile: none CRLfile: none

[RawrMeow]

So, not sure if this is the proper place for this or not.

I was going to try to compile wireguard so I can use my VPN account, but I fail right at the start with git clone. So, reporting it so that maybe I can fix it without bypassing verification.

So, went to here:
https://www.wireguard.com/compilation/

Step two, ran:
git clone https://git.zx2c4.com/wireguard-linux-compat
and get this error:
Cloning into 'wireguard-linux-compat'...
fatal: unable to access 'http://git.zx2c4.com/wireguard-linux-compat/': server certificate verification failed. CAfile: none CRLfile: none

Same error with:
git clone https://git.zx2c4.com/wireguard-tools

I use Fossapup so that is why I am here.

So, what can be done to properly fix this?

[rockedge]

@RawrMeow ,
Go into the directory you are going to clone the package into, open a terminal and enter->

Code: Select all

export GIT_SSL_NO_VERIFY=1

Now

Code: Select all

git clone https://git.zx2c4.com/wireguard-linux-compat

[OscarTalks]

I downloaded the tarball from the top of the list on the webpage using my browser.
Loaded devx and kernel_sources
Entered the "src" directory of the extracted tarball
Ran "make" and "make install"
That seems to have built and installed the kernel module
Looks OK when I run "modinfo wireguard" but don't know how to test beyond that.

[Shortstop]

I had the same exact issue after I installed the 'quickpet' version of 'devx' which apparently includes the dev tools like 'git'.

I found this Stack Overflow post on the same topic:

• https://stackoverflow.com/questions/358 ... ion-failed

Apparently, you can set this option globally for 'git' itself with this command:

Code: Select all

git config --global http.sslverify false

or you can use the previously suggested command before you run git clone:

Code: Select all

export GIT_SSL_NO_VERIFY=1

I mention this because you can either ignore it each time before 'git clone', or you can set it globally.

You might expose yourself to a man-in-the-middle attack but yeah, that might be good if its just your own git instance anyway.