Node js request CERT HAS EXPIRED

Question

I m using Mikeal s request  https   github com mikeal request  to make an https request to a server  However  I keep getting an authorization error of CERT HAS EXPIRED   request           url   https   www domain com api endpoint           strictSSL  false        function error  response  body            if  error  amp  amp  response statusCode    200                res json JSON parse body              else              res json response statusCode    error    error                    I ve tried setting strictSSL to true and false  both output same error of CERT HAS EXPIRED  What is causing this issue and is there any way to fix it in nodejs

User · Answer

I think the strictSSL  false should  should have worked  even in 2013  work  So in short are three possible ways     obvious  Get your CA to renew the certificate  and put it on your server   Change the default settings of your request object   const myRequest   require  request   defaults  strictSSL  false     Many modules that use node-request internally also allow a request-object to be injected  so you can make them use your modified instance   not recommended  Override all certificate checks for all HTTP S  agent connections by setting the environment variable NODE TLS REJECT UNAUTHORIZED 0 for the Node js process

User · Answer

The best way to fix this   Renew the certificate  This can be done for free using Greenlock which issues  certificates via Let s nbsp Encrypt trade  nbsp v2  A less insecure way to fix this    use strict    var request   require  request    var agentOptions  var agent   agentOptions       host   www example com    port   443    path        rejectUnauthorized  false     agent   new https Agent agentOptions    request     url   https   www example com api endpoint    method   GET    agent  agent    function  err  resp  body                   By using an agent with rejectUnauthorized you at least limit the security vulnerability to the requests that deal with that one site instead of making your entire node process completely  utterly insecure   Other Options  If you were using a self-signed cert you would add this option   agentOptions ca     selfSignedRootCaPemCrtBuffer      For trusted-peer connections you would also add these 2 options   agentOptions key   clientPemKeyBuffer  agentOptions cert   clientPemCrtSignedBySelfSignedRootCaBuffer    Bad Idea  It s unfortunate that process env NODE TLS REJECT UNAUTHORIZED    0   is even documented  It should only be used for debugging and should never make it into in sort of code that runs in the wild  Almost every library that runs atop https has a way of passing agent options through  Those that don t should be fixed

User · Answer

I had this problem on production with Heroku and locally while debugging on my macbook pro this morning    After an hour of debugging  this resolved on its own both locally and on production  I m not sure what fixed it  so that s a bit annoying  It happened right when I thought I did something  but reverting my supposed fix didn t bring the problem back     Interestingly enough  it appears my database service  MongoDb has been having server problems since this morning  so there s a good chance this was related to it

User · Answer

Here is a more concise way to achieve the  less insecure  method proposed by CoolAJ86  request     url  url    agentOptions        rejectUnauthorized  false        function  err  resp  body

User · Answer

Add this at the top of your file   process env NODE TLS REJECT UNAUTHORIZED    0     DANGEROUS This disables HTTPS   SSL   TLS checking across your entire node js environment  Please see the solution using an https agent below

User · Answer

Try to temporarily modify request js and harcode everywhere rejectUnauthorized   true  but it would be better to get the certificate extended as a long-term solution

[javascript] Node.js request CERT_HAS_EXPIRED

Examples related to javascript

Examples related to node.js

Examples related to express

Examples related to request