stokkup2313 priority asked 1 year ago

Expected behavior

Deployed project to production (aws ec2 instance). run npm install and it should install everything.

Actual behavior when i run npm install it fails on npm ERR! fatal: unable to access '': SSL certificate problem: certificate has expired

using node version: 14.21.1 angular: 14.2.12 Angular CLI: 14.2.10 Node: 14.21.1 Package Manager: npm 6.14.17 OS: linux x64

Angular: 14.2.12 ... animations, common, compiler, compiler-cli, core, forms ... platform-browser, platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.1402.10 @angular-devkit/build-angular 14.2.10 @angular-devkit/core 14.2.10 @angular-devkit/schematics 14.2.10 @angular/cdk 14.2.7 @angular/cli 14.2.10 @schematics/angular 14.2.10 rxjs 7.8.0 typescript 4.7.4

im trying to push this live asap and this is my biggest blocker...

Resources (screenshots, code snippets etc.)

Sebastian Kaczmarek staff commented 1 year ago

Hi, this problem started to appear since Let's encrypt changed its authentication chains. Previously, they used Root CA X3. Currently, the chain used ISRG Root X1. Generally, all vendors, starting from OS developers like Windows or Linux, through infrastructure providers like AWS or Azure, then creators of various tools like Node, NPM, git, and MDB, ending with end users like you, had to switch to a new system. There is some information on that here

Does the problem occur only on AWS/EC2? What happens when you run npm install from your local machine?

Please insert min. 20 characters.


Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.



Specification of the issue

  • ForumUser: Priority
  • Premium support: Yes
  • Technology: MDB Angular
  • MDB Version: MDB5 3.0.1
  • Device: MACOS
  • Browser: CHROME
  • Provided sample code: Yes
  • Provided link: No