Certificate expired

Completed

Follow

Neil Young

• February 09, 2024 16:53

While trying to install the Cloud-API-Demo-Web project I'm running into this problem with npm install:

 

ubuntu@ca:~/Cloud-API-Demo-Web$ npm install
npm ERR! code CERT_HAS_EXPIRED
npm ERR! errno CERT_HAS_EXPIRED
npm ERR! request to https://registry.npm.taobao.org/yallist/download/yallist-4.0.0.tgz failed, reason: certificate has expired

npm ERR! A complete log of this run can be found in: /home/ubuntu/.npm/_logs/2024-02-09T16_42_34_943Z-debug-0.log

And indeed, opening https://registry.npm.taobao.org/  shows an expired certificate (Jan 22)
You might have better contacts to this provider to make them fix the certificate issue. 

I could work around by 

npm set strict-ssl false

but this can't be really the solution.

1

• 

  DJI Developer Support

  • February 10, 2024 07:28

  We've already passed along this issue to our dedicated development team. In the meantime, you can try resolving it with these friendly steps: 1. Deploy the Demo by using a source code compilation build method, where you manually replace all outdated image sources within the front-end project directory. 2. Alternatively, modify the npm mirror source through a global replacement method. registry=https://registry.npmmirror.com/

  0

  Comment actions Permalink
• 

  Neil Young

  • February 10, 2024 07:52

  Well, being not that strict as usual worked for me "npm set strict-ssl false"

  Thanks

  0

  Comment actions Permalink
• 

  Neil Young

  • February 23, 2024 16:54

  Seems to be working again. Can you confirm?

  0

  Comment actions Permalink
• 

  Neil Young

  • February 25, 2024 09:34

  No, it's not solved

  0

  Comment actions Permalink
• 

  Mario Kaufmann

  • March 22, 2024 19:28

  Hi DJI Developer Support

  We have same issue, do you have more informationen when you can solve it?

  0

  Comment actions Permalink
• 

  Neil Young

  • March 23, 2024 05:43

  Meanwhile they published 1.9.1, which uses another registry. By that the issue is solved

  0

  Comment actions Permalink
• 

  Mario Kaufmann

  • March 23, 2024 15:26

  Great, thank you very much.

   

  0

  Comment actions Permalink
• 

  Tamer Mazen

  • September 11, 2024 13:11

  I'm using release 1.10.0 and still have the same issue.
  Does anyone managed to solve it, without going with source code build approach ? 

  0

  Comment actions Permalink

Please sign in to leave a comment.