Topic: Migrating old Project to MDB Angular Pro 8.10.1; SSL Certificate expired?
Here I am, and not really happy about it either. But I have to revisit an older project I made years ago. Upgrading Angular 7 to 8 with all the pains involved. Which means, I have to upgrade the MDB as well. But when I try to install the latest version of MDB 8 I get this...
Expected behavior
Within the package.json
"ng-uikit-pro-standard": "git+https://oauth2:TOKEN@git.mdbootstrap.com/mdb/angular/ng-uikit-pro-standard.git#8.10.1",
Actual behavior
fatal: unable to access 'https://oauth2:<token>@git.mdbootstrap.com/mdb/angular/ng-uikit-pro-standard.git/': SSL certificate problem: certificate has expired
My token has clearly worked before and it still did with the 7.x.x version.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Status
Opened
Specification of the issue
- ForumUser: Pro
- Premium support: No
- Technology: MDB Angular
- MDB Version: MDB4 8.10.1
- Device: PC
- Browser: Chrome
- OS: Windows 10
- Provided sample code: No
- Provided link: No
Marek Winiarski staff commented 2 years ago
90% of SSL problems are caused by older versions of Node, most of the time they just update Node. Oftentimes, just editing a docker-compose file or a yarn or Jenkins file and everything starts to work.
If you are unable to update, please describe to me what your implementation process looks like, what tools you use, and in what versions, I will try to solve the problem and provide you with a solution.
If the information contains sensitive data, send me an e-mail m.winiarski@mdbootstrap.com with a description.
ak.leimrey pro commented 2 years ago
I literally described the entire process. There is no specific implementation process. I created an access token, that I use to this day, and I can't upgrade to the aforementioned version, despite applying a token. Anything newer than the 7.x.x version that I try to download brings me to the aforementioned problem. The node version is v10.16.0. I can still pull the 7.x.x versions. The entire rest is within the issue specification.
Marek Winiarski staff commented 2 years ago
I can see you are using Node 10.16.0, in September 2021 the credentials policy changed, and the current one uses a different route, see this information https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/ try to change the Node for your app to the latest version