Hello guys,
I’ve been having this error since yesterday. Any help would be appreciated, thank you.
Welcome to the forums @objeff,
I just tried this out for myself and didn’t have any problems.
Is you system time correct? Incorrect system clock can often cause expiry issues
I have the same problem, I tried other macs with the same results.
=> Errors while adding packages:
While downloading fourseven:scss@4.12.0...:
error: certificate has expired
Any help would be appreciated, thank you.
For an unknown reason in my /etc/hosts file, there was the entry: 54.192.225.217 warehouse.meteor.com; removed that entry, now adding packages works. Thanks to all.
4 Likes
@pbeato Yup, that fixed it for me too. I recall adding that entry to the hosts file to solve a problem I had with updating meteor.
it’s Always appear this problem,also i’m https://travis-ci.org/meteor/meteor/builds/612069764 office source code
vpn used ChromeGAE.
cdn use cloudflare.
c:\windows\system32\drivers\etc
54.192.225.217 warehouse.meteor. DNS Server
can you help me?
alway use InstallMeteor.exe add 54.192.225.217 warehouse.meteor. DNS Server
hah!
Same here. Fixed it. Thanks.
Oh my God! Thank you so much.
My meteor was completely dead, and obviously uninstalling and re-installing did no good.
I really wonder how that little vicious line ended up in that file…
My application was running fine in production. But all of a sudden I am getting “code”:“CERT_HAS_EXPIRED”. This is causing huge problem. Looking forward to help on this.
1 Like
Same here really hoping someone has a workaround
Hi, if you are in a Meteor version before 1.9 it runs old Node.js.
Node.js before 10 (and Meteor before 1.9) doesn’t include let’s encrypt’s newest root certificate: DST Root CA X3 Expiration (September 2021) - Let's Encrypt
A workaround, for now, is to run all the meteor commands with the following environment variable NODE_TLS_REJECT_UNAUTHORIZED, for example in the deploy command:
NODE_TLS_REJECT_UNAUTHORIZED=0 meteor deploy .....
We are investigating if we can find a better workaround for old Meteor versions.
14 Likes
Thank you for sharing the fix on such short notice. After setting the environment variable, the error is gone. Thanks again.
If your getting this error inside your app in runtime I believe this topic in the docs will be helpful to you Expired Certificates | Meteor API Docs
I just came across this with a custom kadira deployment connecting to meteor for oauth - I resolved it with NODE_EXTRA_CA_CERTS=[path to letsencrypt root] - this may not be practical for galaxy hosted apps, but works nicely if you have access to the file system of the server you’re deployed on, and is safer than disabling TLS entirely
@znewsham I’m curious, what you use for letsencrypt root?
I tried downloading the pem file from https://letsencrypt.org/certs/isrgrootx1.pem[1] and all I’m getting is the following error:
(node:2056) Warning: Ignoring extra certs from `/root/isrgrootx1.pem`, load failed: error:0B07C065:x509 certificate routines:X509_STORE_add_cert:cert already in hash table
[1] it’s the self-signed version BTW
I went to meteor.com, clicked the padlock and I thought exported the root certificate. Though as I’m now thinking about it, it’s possible I actually exported meteors certificate. I’ll check that today, in any case, it fixed the issue while we work on upgrading
Hi @filipenevola, I use WSL instance to run the meteor app(v1.4) and getting this below errors. Any insights will be helpful.
While downloading webapp@1.3.12…: error: certificate has expired
While downloading webapp-hashing@1.0.9…:
error: certificate has expired
While downloading ziarno:restrict-mixin@0.0.4…:
error: certificate has expired
While downloading zimme:active-route@2.3.2…:
error: certificate has expired
=> Your application has errors. Waiting for file change.