I have the following problem:
I have two machines here, a PC (Windows) and a Raspberry Pi (Raspbian).
I have a git repo on gitlab.com, using an https URL.
On the PC, I have been using and continue to use git (command line, git shell) with zero issues.
On the Pi, today I can no longer access the repo,
git pull origin master, for example, fails with:server certificate verification failedThis is a new issue. I had been happily using git on that devices for months, and nothing was touched on it since the last time I used it successfully about a week or so ago (the device hasn't even been powered on since).
Not knowing much about SSL and certificates, I've just been hunting for solutions and blindly executing commands with no success. So far all I've found and tried is:
github: server certificate verification failed - Seems the most promising. I went through the accepted answer there, updated ca-certificates on the device, manually installed the root certificates, and made sure git was using them, but the error persisted. The OP mentioned "I just added the downloaded cacert.org CAs to my trusted.pem, and now git doesn't complain anymore" but I do not understand how to do this.
Git Clone Fails: Server Certificate Verification Failed - The suggested solution here is simply to disable SSL verification, which I don't really understand since it's always worked up until now. Anyways I tried it and, for reasons I do not understand, after git prompted me for a username and password it said "Basic Authentication Failed". I am 100% sure that I entered the correct username and password.
https://forum.gitlab.com/t/cannot-clone-via-https-with-error-server-certificate-verification-failed/4782 doesn't seem to apply as it is talking about the server side? My repo is hosted at gitlab.com, I don't run the server. In any case the solution there mentions something about adding a newline somewhere but I don't understand where or how that type of problem could suddenly have developed.
https://ubuntuforums.org/showthread.php?t=1865952 seems Ubuntu-specific and the solution doesn't seem related to my situation.
sudden Server Certificate verification failure also appears to be related to an in-house git server.
Playing with my cat for 5 minutes and trying again - This does not seem to be working.
It doesn't make sense to me that it would be a server screw-up on the GitLab side, given that my PC continues to access the repo just fine. I'm also not having any issues on their site, their status Twitter feed doesn't mention anything, and also it seems odd that they would screw this particular thing up (plus the problem has been going on all day now).
I'm not sure what to try next. What's my next step here? It's a bit frustrating as it's frozen project development all day so far.
