bower / bower

A package manager for the web
bower.io
MIT License
14.99k stars 1.85k forks source link

CERT_HAS_EXPIRED Request to https://registry.bower.io/packages/jquery failed: certificate has expired #2623

Closed hajdukda closed 1 year ago

hajdukda commented 1 year ago

bower jquery#1.10.2

Seems the certificate is expired - are there any actions taken to renew ?

Edit. notBefore=Apr 24 01:43:54 2023 GMT Seems certificate was rotated today, so this app should already work with new certificate. Why it does not work with the new certificate ?

My assumption is that if you move your pc datetime by one day into the future suddenly it will start working. Too lazy to test. But if someone has a moment to verify how stupidly this app is written - feel free to do so.

nataliasver commented 1 year ago

I have the same issue! Just looking at this old one https://github.com/bower/bower/issues/2608 Other people are having trouble with the same certificate problem. Waiting for a solution =(

nataliasver commented 1 year ago

I tried changing the date on at least my pc locally, but doesn work either. I think maybe its checked with other timezone? Also tried with "strict-ssl: false" that´s mention on the other issue, and that works, but it isn´t a viable solution to deploy.

ghost commented 1 year ago

As others have said, I'm having this issue as well, the new certificate seems OK but for some reason, the bower client fails when trying to execute "bower update".

Adding "strict-ssl": false" to .bowerrc solves the issue (by disabling SSL requirement), but it's far from ideal.

SureshGedela commented 1 year ago

I am getting the same error

bower json3#3.3.2 CERT_HAS_EXPIRED Request to https://registry.bower.io/packages/json3 failed: certificate has expired

sheerun commented 1 year ago

Certificate seems fine for me, maybe you are MITM by spyware or something. I don't know. Try following commands on urls to debug:

curl -v https://registry.bower.io/packages/json3
echo | openssl s_client -connect registry.bower.io:443 -servername registry.bower.io | openssl x509 -noout -text
echo | openssl s_client -connect registry.bower.io:443 -servername registry.bower.io -showcerts
bryant-finney commented 1 year ago

I was able to reproduce this on some older versions of node:

❯ for i in `seq 6 14`; do
    printf 'node:%s\t%s\n' "$i" $(
      docker run --rm "node:$i" /bin/sh -c "npm i -g bower &&
        bower install --allow-root jquery" 2>&1 | grep -o CERT_HAS_EXPIRED
    )
  done
node:6  CERT_HAS_EXPIRED
node:7  CERT_HAS_EXPIRED
node:8  CERT_HAS_EXPIRED
node:9  CERT_HAS_EXPIRED
node:10
node:11
node:12
node:13
node:14
NguyenKhacTung commented 1 year ago

I also got it with node v8 Shall we waiting for a solution from Github?

scan0qr commented 1 year ago

I also got it with node v8 Shall we waiting for a solution from Github?

Please let me know if you find valid solution instead of just disabling ssl

hajdukda commented 1 year ago

I was able to reproduce this on some older versions of node:

❯ for i in `seq 6 14`; do
    printf 'node:%s\t%s\n' "$i" $(
      docker run --rm "node:$i" /bin/sh -c "npm i -g bower &&
        bower install --allow-root jquery" 2>&1 | grep -o CERT_HAS_EXPIRED
    )
  done
node:6  CERT_HAS_EXPIRED
node:7  CERT_HAS_EXPIRED
node:8  CERT_HAS_EXPIRED
node:9  CERT_HAS_EXPIRED
node:10
node:11
node:12
node:13
node:14

Switching to newer nodeJS fixes the issue, thank you for validating which versions are broken. Time to update legacy stuff boyz, cheers.

scan0qr commented 1 year ago

I was able to reproduce this on some older versions of node:

❯ for i in `seq 6 14`; do
    printf 'node:%s\t%s\n' "$i" $(
      docker run --rm "node:$i" /bin/sh -c "npm i -g bower &&
        bower install --allow-root jquery" 2>&1 | grep -o CERT_HAS_EXPIRED
    )
  done
node:6  CERT_HAS_EXPIRED
node:7  CERT_HAS_EXPIRED
node:8  CERT_HAS_EXPIRED
node:9  CERT_HAS_EXPIRED
node:10
node:11
node:12
node:13
node:14

Switching to newer nodeJS fixes the issue, thank you for validating which versions are broken. Time to update legacy stuff boyz, cheers.

Can you please check if 16 is fine? We are getting same error for node 16.

theobscenezen commented 1 year ago

NODE_OPTIONS=--use-openssl-ca bower install

https://github.com/bower/bower/issues/2608#issuecomment-1521355964

hajdukda commented 1 year ago

Another option I've seen was to run "bower cache clean"

sheerun commented 1 year ago

Solution is to use NODE_OPTIONS=--use-openssl-ca and Node >= 8, and true solution is to finally let go of Bower https://github.com/bower/registry/issues/304#issuecomment-1521604693

If you want to comment, please do it in linked thread