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
Error: self signed certificate in certificate chain #2061
Comments
in this case check for if you want to debug this use
|
Thanks for the explanation. I found out how to avoid problems with fake certificates in case anyone is interested:
With that I can use fake SSL auth to inspect the communications between my client and a server. |
My error was similar but now I"m good thanks @nmaxcom Error: unable to verify the first certificate |
or you can just use let's encrypt, certificates that are signed by a legit CA. |
For self-signed CA, we can specify 'rejectUnauthorized = false'. |
Better alternatives are: In this way you have a single configuration across all your environments. |
rejectUnauthorized works in dont know why 😢 |
https://github.com/request/request/blob/v2.81.1/request.js#L257-L259 Sorry, only see the code. I get that |
getting this error while runnign code |
for people who suggest to set rejectUnauthorized=false what if i have internal servers that should have encrypted connections with each other with some self signed certificates , iguess setting rejectUnauthorized to false will stop the error but my connections are 100% prone to MITM atacks , I see that this is a bug in nodejs tls library that it suffers from and i can't find any fix any where (i have google to page 5 of google results that is really deep) i don't know how other people don't talk about it , AM I missing something here! !!!!! please correct me if i am wrong !! |
Both do not work for me
P.S. Running the code from within ELECTRON with ssl disable flag on. |
For me, disabling Kaspersky antivirus solved the problem. |
#2061 (comment) seems to be the answer to the general question |
Gives no effect. |
I'm trying to analyze my requests against a server using Charles Proxy. The server uses TSL so I have the classic fake certificate to be able to view clear traffic.
NodeJS / Request don't like it, so my script doesn't run and throws that error.
How can I bypass this?
The text was updated successfully, but these errors were encountered: