SSL certificate problem: certificate has expired

patricksteyaert pro premium commented 3 years ago

I have the same problem! This seems to be happening every year...

latakoo commented 3 years ago

Indeed, I've seen reports of this happening last year and also 3 years ago

finleysg commented 3 years ago

Our builds have also been stuck all day: error fatal: unable to access 'https://oauth2:***@git.mdbootstrap.com/mdb/react/re-pro.git/': SSL certificate problem: certificate has expired

patricksteyaert pro premium commented 3 years ago

it also happened two years ago: https://mdbootstrap.com/support/angular/git-https-oauth2-certificate-expired-2b1b4/

yearly ritual it seems

finleysg commented 3 years ago

Might be useful to note that we see this only from our build agents in Azure, where git is configured to use open ssl:

http.sslbackend=openssl

Not a great experience, bringing down customer builds every year.

patricksteyaert pro premium commented 3 years ago

No news at all????

Sebastian Kaczmarek staff pro premium commented 3 years ago

We are working on this issue at this very moment. Sorry for the inconvenience.

finleysg commented 3 years ago

For those of you still blocked with this issue, you can target just the MDB git url and turn off ssl verification. It can be done per repo, globally (for the current user), or at the system level like we did below. Once the certificate issue is sorted out here, you should turn verification back on.

git config --system http.https://oauth2:<token>@git.mdbootstrap.com/mdb/react/re-pro.git.sslVerify false

catalog360 commented 3 years ago

We too are having the same issue.

npm ERR! fatal: unable to access 'https://oauth2:*@git.mdbootstrap.com/mdb/react/re-pro.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none npm ERR! npm ERR! exited with error code: 128

@Finleysg we tried that approach with --global to disable sslverify but didnt work unfortunately.

Marek Winiarski staff pro premium commented 3 years ago

This problem must be resolved on both sides, On server everything is updated to the latest version.

On client site the problem will still exist if: - your OS is not updated to the latest version, if you can't do this please - update your security tools, in Windows you can do this by package https://support.microsoft.com/en-us/topic/support-for-urgent-trusted-root-updates-for-windows-root-certificate-program-in-windows-a4ac4d6c-7c62-3b6e-dfd2-377982bf3ea5 if you can't do it, you can try - update npm, git, and all tools which you use to work, some apps use their own chain rules, for some people it helped,

In this instruction https://docs.certifytheweb.com/docs/kb/kb-202109-letsencrypt/#clients-browsers-etc has been described how to manually update ca-certificate. during instalation certificate of ISRG Root X1 please choose Local Machine option, sometime users choose second options, and istalled cert for only one user.

If this problem still exists, write to me:

How do you use OS, when was it updated, For which application this problem has occured, and specify its version Provide your IP.

Marek From MDB

patricksteyaert pro premium commented 3 years ago

I am deploying on aws with amplify and things still don't work. Getting pretty upset about all of this!

Marek Winiarski staff pro premium commented 3 years ago

@patricksteyaert Did you check out all recommended steps? Update npm, git, ca-certificates? What OS are you using? What tool are you using to pull the package? The problem is when you pull from our repo or how to push on AWS Amplify?

patricksteyaert pro premium commented 3 years ago

Marek,

I get the following error when amplify is building the front end:

npm ERR! /usr/bin/git ls-remote -h -t https://oauth2:*@git.mdbootstrap.com/mdb/angular/ng-uikit-pro-standard.git npm ERR! npm ERR! fatal: unable to access 'https://git.mdbootstrap.com/mdb/angular/ng-uikit-pro-standard.git/': SSL certificate problem: certificate has expired

Marek Winiarski staff pro premium commented 3 years ago

Hi Patricksteyaert,

Can you write what version of node.js and npm you have installed?

Does the bug arise when using Amplify AWS?