-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gyp ERR! stack FetchError: request to https://nodejs.org/download/...headers.tar.gz failed, reason: unable to get local issuer certificate #3686
Comments
If anyone else experience the same issue, it can be resolved as follow:
|
Thank you @andrew-ignatiev that does indeed work (although for
wouldn't work? |
Here's what
|
What finally worked for me is #3686 (comment). However, that's obviously not a good developer experience. |
I hit this issue on node v16.14.0 and v16.16.0. However, it works fine on v16.13.1. Is anyone looking into this? |
Same here! I can't get it working on v16.16.0. |
While this used to work perfectly for me, trying the same now fails on 16.14.2 with the following error output:
|
for some reason, I got it working with
of course, you need to delete |
I have tried so many things you wouldn't even believe and this actually worked! Thank you so much! I really hate these |
I have some problem with version 16.15.0:
|
Seems like it also happens with
However, when repeated on Ubuntu Server, this no longer happens. |
Is there a solution that actually works? I tried every suggestion...
... and neither
This might be connected to the issues nodejs/node#3742, nodejs/node-gyp#448 and nodejs/node-gyp#695, but the recommendations there are similar to those here. |
None of the other methods worked for me (see #3686 (comment)), but this command finally solved the problem (on Windows 11):
|
i am getting this error how can i get round it, i am installing lastest version of node-sass npmrc file is |
Still no solution on this? I tried every workaround suggested in this thread. Nothing helped. Can't use Node-Gyp, neither SASS as it depends on it. |
@mibadim I just worked with my company's ops team and this what we did that worked for me (may not for you, but I hope so):
Finally, I |
I can confirm, that this solution worked for me as well. $ export NODE_TLS_REJECT_UNAUTHORIZED=0 $ npm config set strict-ssl true |
in Debian, |
Is there an update for on this issue? |
Is there any update for RHEL8? I am getting the same issue. Tried almost everything... |
I as well still get this error on latest LTS Node v20.10.0 Have tried all solutions above except for downloading and setting the tar separately. Specifically when trying to build backstage.io via yarn. Linux Ubuntu latest LTS. I know its my company's vpn proxy causing the issue but there is not much I can do about that. A more official solution/fix would be nice to have. |
bumping this to see if there is any solution? |
wow, it worked |
Node.js v16 has reached EoL. If you are able to reproduce in the latest/LTS version of Node.js, please leave a comment, otherwise I'll close this is resolved. Thanks! |
This is an issue in latest version of Node... |
This issue is happening for me on Windows 11 (both from gitbash and powershell) PNPM 9.1.1 I tried the below without any change in behaviour: Env Variables: ~/.npmrc Then This actually moves me past the node headers download but it fails next on fetching node.lib again with self signed certificate. |
Hey guyyyyyys! I've been experienced the same issue and finally found out the solution! ✅ Try update your certificate👉 You can do this with updating your CURL
… and it worked 😉 |
Details
Unable to run
I've worked through all related issues (SO and nodejs/node-gyp#695), ensure that:
curl
Node.js version
Example code
No response
Operating system
OSX Darwin 21.2.0
Scope
Installation
Module and version
Not applicable.
The text was updated successfully, but these errors were encountered: