NPM not installing package. Hostname/IP address doesn't match certificate's altnames:

Question

For a solution, see below

It was working yesterday, but I don't know what happened to it.

NPM is not installing the package. The hostname/IP address doesn't match the certificate's altnames:

Host: registry.npmjs.org. is not in the cert's altnames: DNS:a.sni.fastly.net, DNS:a.sni.global-ssl.fastly.net

This is what I was trying to do:

>> ROOT: }   npm install up to date in 1.797s  >> ROOT: }   npm install express-messages npm ERR! request to https://registry.npmjs.org/express-messages failed, reason: Hostname/IP doesn't match certificate's altnames: "Host: registry.npmjs.org. is not in the cert's altnames: DNS:a.sni.fastly.net, DNS:a.sni.global-ssl.fastly.net"  npm ERR! A complete log of this run can be found in: npm ERR!     /Users/prashant/.npm/_logs/2018-09-01T11_54_09_205Z-debug.log >> ROOT: } 

I have read all the articles/issues that I could find and also have re-installed Node.js and npm, but after that too I have the same issue.

OS: macOS v10.12 (Sierra) (16A323)

LOGS

0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', 1 verbose cli   '/usr/local/bin/npm', 1 verbose cli   'install', 1 verbose cli   'express-messages' ] 2 info using [email protected] 3 info using [email protected] 4 verbose npm-session 54f0308df52fc8a7 5 silly install loadCurrentTree 6 silly install readLocalPackageData 7 silly fetchPackageMetaData error for express-messages@latest request to https://registry.npmjs.org/express-messages failed, reason: Hostname/IP doesn't match certificate's altnames: "Host: registry.npmjs.org. is not in the cert's altnames: DNS:a.sni.fastly.net, DNS:a.sni.global-ssl.fastly.net" 8 verbose type system 9 verbose stack FetchError: request to https://registry.npmjs.org/express-messages failed, reason: Hostname/IP doesn't match certificate's altnames: "Host: registry.npmjs.org. is not in the cert's altnames: DNS:a.sni.fastly.net, DNS:a.sni.global-ssl.fastly.net" 9 verbose stack     at ClientRequest.req.on.err (/usr/local/lib/node_modules/npm/node_modules/pacote/node_modules/make-fetch-happen/node_modules/node-fetch-npm/src/index.js:68:14) 9 verbose stack     at emitOne (events.js:116:13) 9 verbose stack     at ClientRequest.emit (events.js:211:7) 9 verbose stack     at TLSSocket.socketErrorListener (_http_client.js:387:9) 9 verbose stack     at emitOne (events.js:116:13) 9 verbose stack     at TLSSocket.emit (events.js:211:7) 9 verbose stack     at emitErrorNT (internal/streams/destroy.js:64:8) 9 verbose stack     at _combinedTickCallback (internal/process/next_tick.js:138:11) 9 verbose stack     at process._tickCallback (internal/process/next_tick.js:180:9) 10 verbose cwd /Users/prashant/Desktop/NodeJs-login-registration 11 verbose Darwin 16.0.0 12 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "express-messages" 13 verbose node v8.11.4 14 verbose npm  v5.6.0 15 error request to https://registry.npmjs.org/express-messages failed, reason: Hostname/IP doesn't match certificate's altnames: "Host: registry.npmjs.org. is not in the cert's altnames: DNS:a.sni.fastly.net, DNS:a.sni.global-ssl.fastly.net" 16 verbose exit [ 1, true ] 

BROWSER image link: https://imgur.com/a/pBANqtQ

But I have already tried to change the SSL setting npm config ls -l by npm set strict-ssl false.

It stucks on this image link: https://imgur.com/9LasDKT

And then this error: https://imgur.com/ARXj9v3

Update

My application is running fine. It's just I am not able to install packages https://imgur.com/mvKOZeq

There is a new kind of error that comes when I try to stop the server (Note: I have changed the SSL setting as mentioned above, if it has something to do with that) https://imgur.com/yPKq0n5

>> ROOT: }   npm start  > [email protected] start /Users/prashant/Desktop/NodeJs-login-registration > nodemon app.js  [nodemon] 1.18.4 [nodemon] to restart at any time, enter `rs` [nodemon] watching: *.* [nodemon] starting `node app.js` Remember :  start mongoDB demon -->   mongod   &&   mongo -- Server live : 3000 -- Connected to DB :  SUCCESS  ^Cnpm ERR! code ELIFECYCLE npm ERR! errno 130 npm ERR! [email protected] start: `nodemon app.js` npm ERR! Exit status 130 npm ERR! npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.  npm ERR! A complete log of this run can be found in: npm ERR!     /Users/prashant/.npm/_logs/2018-09-01T13_10_55_028Z-debug.log >> ROOT: } 

Logs: when I stop the server

0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ] 2 info using [email protected] 3 info using [email protected] 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle [email protected]~prestart: [email protected] 6 info lifecycle [email protected]~start: [email protected] 7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true 8 verbose lifecycle [email protected]~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/prashant/Desktop/NodeJs-login-registration/node_modules/.bin:/Library/Frameworks/Python.framework/Versions/3.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Frameworks/Python.framework/Versions/3.6/bin 9 verbose lifecycle [email protected]~start: CWD: /Users/prashant/Desktop/NodeJs-login-registration 10 silly lifecycle [email protected]~start: Args: [ '-c', 'nodemon app.js' ] 11 silly lifecycle [email protected]~start: Returned: code: 130  signal: null 12 info lifecycle [email protected]~start: Failed to exec start script 13 verbose stack Error: [email protected] start: `nodemon app.js` 13 verbose stack Exit status 130 13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16) 13 verbose stack     at emitTwo (events.js:126:13) 13 verbose stack     at EventEmitter.emit (events.js:214:7) 13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack     at emitTwo (events.js:126:13) 13 verbose stack     at ChildProcess.emit (events.js:214:7) 13 verbose stack     at maybeClose (internal/child_process.js:925:16) 13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 14 verbose pkgid [email protected] 15 verbose cwd /Users/prashant/Desktop/NodeJs-login-registration 16 verbose Darwin 16.0.0 17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 18 verbose node v8.11.4 19 verbose npm  v5.6.0 20 error code ELIFECYCLE 21 error errno 130 22 error [email protected] start: `nodemon app.js` 22 error Exit status 130 23 error Failed at the [email protected] start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 130, true ] 

.

.

.

I found a solution that worked for me

dig www.npmjs.com @1.1.1.1 

2. Add the IP address to your /etc/hosts file.

   Go to this directory and do sudo nano hosts.

And add this into the host file: 1.1.1.1 a.sni.fastly.net.

Answer 1

Add the following line to the /etc/hosts file:

104.16.16.35 registry.npmjs.org 

Answer 2

npmjs has a DNS problem according to its incident report: DNS misconfiguration cached in ISP DNS caches.

To solve your problem, do this:

1. dig www.npmjs.com @1.1.1.1

   Sample output on Linux

   ; <<>> DiG 9.10.3-P4-Ubuntu <<>> www.npmjs.com @1.1.1.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50308 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1  ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1452 ;; QUESTION SECTION: ;www.npmjs.com.                 IN      A  ;; ANSWER SECTION: www.npmjs.com.          128     IN      CNAME   www.npmjs.com.cdn.cloudflare.net. www.npmjs.com.cdn.cloudflare.net. 151 IN A      104.16.109.30 www.npmjs.com.cdn.cloudflare.net. 151 IN A      104.16.110.30  ;; Query time: 2 msec ;; SERVER: 1.1.1.1#53(1.1.1.1) ;; WHEN: Sat Sep 01 14:05:56 UTC 2018 ;; MSG SIZE  rcvd: 120 

   2. Get resolved IP address: 104.16.109.30 in my case

   3. Add new entry in your /etc/hosts file

      echo "104.16.110.30 www.npmjs.com registry.npmjs.org" >> /etc/hosts

   Do not forget to remove this line at the end of the weekend.