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

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
33
down vote

favorite
4












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 npm@5.6.0
3 info using node@v8.11.4
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

> nodejs-login-registration@1.0.0 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! nodejs-login-registration@1.0.0 start: `nodemon app.js`
npm ERR! Exit status 130
npm ERR!
npm ERR! Failed at the nodejs-login-registration@1.0.0 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 npm@5.6.0
3 info using node@v8.11.4
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle nodejs-login-registration@1.0.0~prestart: nodejs-login-registration@1.0.0
6 info lifecycle nodejs-login-registration@1.0.0~start: nodejs-login-registration@1.0.0
7 verbose lifecycle nodejs-login-registration@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle nodejs-login-registration@1.0.0~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 nodejs-login-registration@1.0.0~start: CWD: /Users/prashant/Desktop/NodeJs-login-registration
10 silly lifecycle nodejs-login-registration@1.0.0~start: Args: [ '-c', 'nodemon app.js' ]
11 silly lifecycle nodejs-login-registration@1.0.0~start: Returned: code: 130 signal: null
12 info lifecycle nodejs-login-registration@1.0.0~start: Failed to exec start script
13 verbose stack Error: nodejs-login-registration@1.0.0 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 nodejs-login-registration@1.0.0
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 nodejs-login-registration@1.0.0 start: `nodemon app.js`
22 error Exit status 130
23 error Failed at the nodejs-login-registration@1.0.0 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



  1. 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.




javascript node.js macos express




share|improve this question


















  • 4




    Possible duplicate of Node.js Hostname/IP doesn't match certificate's altnames
    – coderroggie
    Sep 1 at 12:47






  • 1




    Possible duplicate of I am facing error while trying to install npm packages on windows, I am using node v10.9.0
    – Jayendran
    Sep 1 at 12:48






  • 1




    @HardikShah how that works on mac?
    – user6202188
    Sep 1 at 12:51






  • 1




    I have the exact same issue, however I just installed crypto via yarn and openssl via brew
    – E K
    Sep 1 at 12:56






  • 2




    This is a global problem. A DNS problem. This is working for me "temporarily": https://status.npmjs.org/incidents/v22ffls5cd6h
    – Jakub
    Sep 1 at 13:15















up vote
33
down vote

favorite
4












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 npm@5.6.0
3 info using node@v8.11.4
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

> nodejs-login-registration@1.0.0 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! nodejs-login-registration@1.0.0 start: `nodemon app.js`
npm ERR! Exit status 130
npm ERR!
npm ERR! Failed at the nodejs-login-registration@1.0.0 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 npm@5.6.0
3 info using node@v8.11.4
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle nodejs-login-registration@1.0.0~prestart: nodejs-login-registration@1.0.0
6 info lifecycle nodejs-login-registration@1.0.0~start: nodejs-login-registration@1.0.0
7 verbose lifecycle nodejs-login-registration@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle nodejs-login-registration@1.0.0~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 nodejs-login-registration@1.0.0~start: CWD: /Users/prashant/Desktop/NodeJs-login-registration
10 silly lifecycle nodejs-login-registration@1.0.0~start: Args: [ '-c', 'nodemon app.js' ]
11 silly lifecycle nodejs-login-registration@1.0.0~start: Returned: code: 130 signal: null
12 info lifecycle nodejs-login-registration@1.0.0~start: Failed to exec start script
13 verbose stack Error: nodejs-login-registration@1.0.0 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 nodejs-login-registration@1.0.0
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 nodejs-login-registration@1.0.0 start: `nodemon app.js`
22 error Exit status 130
23 error Failed at the nodejs-login-registration@1.0.0 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



  1. 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.




javascript node.js macos express




share|improve this question


















  • 4




    Possible duplicate of Node.js Hostname/IP doesn't match certificate's altnames
    – coderroggie
    Sep 1 at 12:47






  • 1




    Possible duplicate of I am facing error while trying to install npm packages on windows, I am using node v10.9.0
    – Jayendran
    Sep 1 at 12:48






  • 1




    @HardikShah how that works on mac?
    – user6202188
    Sep 1 at 12:51






  • 1




    I have the exact same issue, however I just installed crypto via yarn and openssl via brew
    – E K
    Sep 1 at 12:56






  • 2




    This is a global problem. A DNS problem. This is working for me "temporarily": https://status.npmjs.org/incidents/v22ffls5cd6h
    – Jakub
    Sep 1 at 13:15













up vote
33
down vote

favorite
4









up vote
33
down vote

favorite
4






4





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 npm@5.6.0
3 info using node@v8.11.4
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

> nodejs-login-registration@1.0.0 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! nodejs-login-registration@1.0.0 start: `nodemon app.js`
npm ERR! Exit status 130
npm ERR!
npm ERR! Failed at the nodejs-login-registration@1.0.0 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 npm@5.6.0
3 info using node@v8.11.4
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle nodejs-login-registration@1.0.0~prestart: nodejs-login-registration@1.0.0
6 info lifecycle nodejs-login-registration@1.0.0~start: nodejs-login-registration@1.0.0
7 verbose lifecycle nodejs-login-registration@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle nodejs-login-registration@1.0.0~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 nodejs-login-registration@1.0.0~start: CWD: /Users/prashant/Desktop/NodeJs-login-registration
10 silly lifecycle nodejs-login-registration@1.0.0~start: Args: [ '-c', 'nodemon app.js' ]
11 silly lifecycle nodejs-login-registration@1.0.0~start: Returned: code: 130 signal: null
12 info lifecycle nodejs-login-registration@1.0.0~start: Failed to exec start script
13 verbose stack Error: nodejs-login-registration@1.0.0 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 nodejs-login-registration@1.0.0
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 nodejs-login-registration@1.0.0 start: `nodemon app.js`
22 error Exit status 130
23 error Failed at the nodejs-login-registration@1.0.0 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



  1. 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.




javascript node.js macos express




share|improve this 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 npm@5.6.0
3 info using node@v8.11.4
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

> nodejs-login-registration@1.0.0 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! nodejs-login-registration@1.0.0 start: `nodemon app.js`
npm ERR! Exit status 130
npm ERR!
npm ERR! Failed at the nodejs-login-registration@1.0.0 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 npm@5.6.0
3 info using node@v8.11.4
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle nodejs-login-registration@1.0.0~prestart: nodejs-login-registration@1.0.0
6 info lifecycle nodejs-login-registration@1.0.0~start: nodejs-login-registration@1.0.0
7 verbose lifecycle nodejs-login-registration@1.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle nodejs-login-registration@1.0.0~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 nodejs-login-registration@1.0.0~start: CWD: /Users/prashant/Desktop/NodeJs-login-registration
10 silly lifecycle nodejs-login-registration@1.0.0~start: Args: [ '-c', 'nodemon app.js' ]
11 silly lifecycle nodejs-login-registration@1.0.0~start: Returned: code: 130 signal: null
12 info lifecycle nodejs-login-registration@1.0.0~start: Failed to exec start script
13 verbose stack Error: nodejs-login-registration@1.0.0 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 nodejs-login-registration@1.0.0
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 nodejs-login-registration@1.0.0 start: `nodemon app.js`
22 error Exit status 130
23 error Failed at the nodejs-login-registration@1.0.0 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



  1. 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.





javascript node.js macos express





share|improve this question













share|improve this question




share|improve this question








edited Sep 1 at 20:30









Peter Mortensen

12.9k1983111




12.9k1983111










asked Sep 1 at 12:43









user6202188

18027




18027







  • 4




    Possible duplicate of Node.js Hostname/IP doesn't match certificate's altnames
    – coderroggie
    Sep 1 at 12:47






  • 1




    Possible duplicate of I am facing error while trying to install npm packages on windows, I am using node v10.9.0
    – Jayendran
    Sep 1 at 12:48






  • 1




    @HardikShah how that works on mac?
    – user6202188
    Sep 1 at 12:51






  • 1




    I have the exact same issue, however I just installed crypto via yarn and openssl via brew
    – E K
    Sep 1 at 12:56






  • 2




    This is a global problem. A DNS problem. This is working for me "temporarily": https://status.npmjs.org/incidents/v22ffls5cd6h
    – Jakub
    Sep 1 at 13:15













  • 4




    Possible duplicate of Node.js Hostname/IP doesn't match certificate's altnames
    – coderroggie
    Sep 1 at 12:47






  • 1




    Possible duplicate of I am facing error while trying to install npm packages on windows, I am using node v10.9.0
    – Jayendran
    Sep 1 at 12:48






  • 1




    @HardikShah how that works on mac?
    – user6202188
    Sep 1 at 12:51






  • 1




    I have the exact same issue, however I just installed crypto via yarn and openssl via brew
    – E K
    Sep 1 at 12:56






  • 2




    This is a global problem. A DNS problem. This is working for me "temporarily": https://status.npmjs.org/incidents/v22ffls5cd6h
    – Jakub
    Sep 1 at 13:15








4




4




Possible duplicate of Node.js Hostname/IP doesn't match certificate's altnames
– coderroggie
Sep 1 at 12:47




Possible duplicate of Node.js Hostname/IP doesn't match certificate's altnames
– coderroggie
Sep 1 at 12:47




1




1




Possible duplicate of I am facing error while trying to install npm packages on windows, I am using node v10.9.0
– Jayendran
Sep 1 at 12:48




Possible duplicate of I am facing error while trying to install npm packages on windows, I am using node v10.9.0
– Jayendran
Sep 1 at 12:48




1




1




@HardikShah how that works on mac?
– user6202188
Sep 1 at 12:51




@HardikShah how that works on mac?
– user6202188
Sep 1 at 12:51




1




1




I have the exact same issue, however I just installed crypto via yarn and openssl via brew
– E K
Sep 1 at 12:56




I have the exact same issue, however I just installed crypto via yarn and openssl via brew
– E K
Sep 1 at 12:56




2




2




This is a global problem. A DNS problem. This is working for me "temporarily": https://status.npmjs.org/incidents/v22ffls5cd6h
– Jakub
Sep 1 at 13:15





This is a global problem. A DNS problem. This is working for me "temporarily": https://status.npmjs.org/incidents/v22ffls5cd6h
– Jakub
Sep 1 at 13:15













3 Answers
3






active

oldest

votes

















up vote
19
down vote



accepted










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


    1. Get resolved IP address: 104.16.109.30 in my case



    2. 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.








share|improve this answer






















  • works for me, had to use nano to open /etc/hosts, echo gave me permission denied because I'm an amateur
    – gray
    Sep 1 at 15:07


















up vote
27
down vote













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



104.16.16.35 registry.npmjs.org





share|improve this answer






















  • I did something and it works, see the post above, i have update the solution check it out
    – user6202188
    Sep 1 at 14:00






  • 2




    I needed this answer. 1.1.1.1 is now returning the corruped a.sni.fastly.net ip's for me instead of the actual registry IPs.
    – Routhinator
    Sep 1 at 14:03






  • 1




    I can confirm that this works. Adding the below line /etc/hosts on my dev machine fixed this issue. 104.16.16.35 registry.npmjs.org
    – Gavster
    Sep 1 at 14:26






  • 2




    Hey u saved my day..
    – Gokul Kulkarni
    Sep 1 at 14:48






  • 1




    @burnt1ce That's likely the IP address the user gets when digging into the npmjs.org from their geographic region. I'm in the SE US & when I dig npmjs.org I see my resolved IP is 104.16.109.30 I've not performed any networking work on Windows in many years, but I would imagine you have a dig, or dig-like command line utility to help in determining the IP address you should use (until the weekend end ^^ See previous comment)
    – user2977468
    Sep 1 at 15:35

















up vote
3
down vote













Try to change the default registry:



npm config set registry http://registry.npmjs.org


For everyone who is stuck with mup deploy:



docker:
// change to 'abernix/meteord:base' if your app is using Meteor 1.4 - 1.5
image: 'abernix/meteord:node-8.4.0-base',
buildInstructions: [
'RUN npm config set strict-ssl false'
]
,






share|improve this answer






















  • do you mean to change https to http
    – user6202188
    Sep 1 at 13:47










Your Answer





StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52128212%2fnpm-not-installing-package-hostname-ip-address-doesnt-match-certificates-altn%23new-answer', 'question_page');

);

Post as a guest

















3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
19
down vote



accepted










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


    1. Get resolved IP address: 104.16.109.30 in my case



    2. 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.








share|improve this answer






















  • works for me, had to use nano to open /etc/hosts, echo gave me permission denied because I'm an amateur
    – gray
    Sep 1 at 15:07















up vote
19
down vote



accepted










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


    1. Get resolved IP address: 104.16.109.30 in my case



    2. 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.








share|improve this answer






















  • works for me, had to use nano to open /etc/hosts, echo gave me permission denied because I'm an amateur
    – gray
    Sep 1 at 15:07













up vote
19
down vote



accepted







up vote
19
down vote



accepted






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


    1. Get resolved IP address: 104.16.109.30 in my case



    2. 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.








share|improve this answer














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


    1. Get resolved IP address: 104.16.109.30 in my case



    2. 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.









share|improve this answer














share|improve this answer



share|improve this answer








edited Sep 1 at 20:32









Peter Mortensen

12.9k1983111




12.9k1983111










answered Sep 1 at 14:28









shadaï ALI

472310




472310











  • works for me, had to use nano to open /etc/hosts, echo gave me permission denied because I'm an amateur
    – gray
    Sep 1 at 15:07

















  • works for me, had to use nano to open /etc/hosts, echo gave me permission denied because I'm an amateur
    – gray
    Sep 1 at 15:07
















works for me, had to use nano to open /etc/hosts, echo gave me permission denied because I'm an amateur
– gray
Sep 1 at 15:07





works for me, had to use nano to open /etc/hosts, echo gave me permission denied because I'm an amateur
– gray
Sep 1 at 15:07













up vote
27
down vote













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



104.16.16.35 registry.npmjs.org





share|improve this answer






















  • I did something and it works, see the post above, i have update the solution check it out
    – user6202188
    Sep 1 at 14:00






  • 2




    I needed this answer. 1.1.1.1 is now returning the corruped a.sni.fastly.net ip's for me instead of the actual registry IPs.
    – Routhinator
    Sep 1 at 14:03






  • 1




    I can confirm that this works. Adding the below line /etc/hosts on my dev machine fixed this issue. 104.16.16.35 registry.npmjs.org
    – Gavster
    Sep 1 at 14:26






  • 2




    Hey u saved my day..
    – Gokul Kulkarni
    Sep 1 at 14:48






  • 1




    @burnt1ce That's likely the IP address the user gets when digging into the npmjs.org from their geographic region. I'm in the SE US & when I dig npmjs.org I see my resolved IP is 104.16.109.30 I've not performed any networking work on Windows in many years, but I would imagine you have a dig, or dig-like command line utility to help in determining the IP address you should use (until the weekend end ^^ See previous comment)
    – user2977468
    Sep 1 at 15:35














up vote
27
down vote













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



104.16.16.35 registry.npmjs.org





share|improve this answer






















  • I did something and it works, see the post above, i have update the solution check it out
    – user6202188
    Sep 1 at 14:00






  • 2




    I needed this answer. 1.1.1.1 is now returning the corruped a.sni.fastly.net ip's for me instead of the actual registry IPs.
    – Routhinator
    Sep 1 at 14:03






  • 1




    I can confirm that this works. Adding the below line /etc/hosts on my dev machine fixed this issue. 104.16.16.35 registry.npmjs.org
    – Gavster
    Sep 1 at 14:26






  • 2




    Hey u saved my day..
    – Gokul Kulkarni
    Sep 1 at 14:48






  • 1




    @burnt1ce That's likely the IP address the user gets when digging into the npmjs.org from their geographic region. I'm in the SE US & when I dig npmjs.org I see my resolved IP is 104.16.109.30 I've not performed any networking work on Windows in many years, but I would imagine you have a dig, or dig-like command line utility to help in determining the IP address you should use (until the weekend end ^^ See previous comment)
    – user2977468
    Sep 1 at 15:35












up vote
27
down vote










up vote
27
down vote









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



104.16.16.35 registry.npmjs.org





share|improve this answer














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



104.16.16.35 registry.npmjs.org






share|improve this answer














share|improve this answer



share|improve this answer








edited Sep 1 at 20:35









Peter Mortensen

12.9k1983111




12.9k1983111










answered Sep 1 at 13:55









Kangur

241113




241113











  • I did something and it works, see the post above, i have update the solution check it out
    – user6202188
    Sep 1 at 14:00






  • 2




    I needed this answer. 1.1.1.1 is now returning the corruped a.sni.fastly.net ip's for me instead of the actual registry IPs.
    – Routhinator
    Sep 1 at 14:03






  • 1




    I can confirm that this works. Adding the below line /etc/hosts on my dev machine fixed this issue. 104.16.16.35 registry.npmjs.org
    – Gavster
    Sep 1 at 14:26






  • 2




    Hey u saved my day..
    – Gokul Kulkarni
    Sep 1 at 14:48






  • 1




    @burnt1ce That's likely the IP address the user gets when digging into the npmjs.org from their geographic region. I'm in the SE US & when I dig npmjs.org I see my resolved IP is 104.16.109.30 I've not performed any networking work on Windows in many years, but I would imagine you have a dig, or dig-like command line utility to help in determining the IP address you should use (until the weekend end ^^ See previous comment)
    – user2977468
    Sep 1 at 15:35
















  • I did something and it works, see the post above, i have update the solution check it out
    – user6202188
    Sep 1 at 14:00






  • 2




    I needed this answer. 1.1.1.1 is now returning the corruped a.sni.fastly.net ip's for me instead of the actual registry IPs.
    – Routhinator
    Sep 1 at 14:03






  • 1




    I can confirm that this works. Adding the below line /etc/hosts on my dev machine fixed this issue. 104.16.16.35 registry.npmjs.org
    – Gavster
    Sep 1 at 14:26






  • 2




    Hey u saved my day..
    – Gokul Kulkarni
    Sep 1 at 14:48






  • 1




    @burnt1ce That's likely the IP address the user gets when digging into the npmjs.org from their geographic region. I'm in the SE US & when I dig npmjs.org I see my resolved IP is 104.16.109.30 I've not performed any networking work on Windows in many years, but I would imagine you have a dig, or dig-like command line utility to help in determining the IP address you should use (until the weekend end ^^ See previous comment)
    – user2977468
    Sep 1 at 15:35















I did something and it works, see the post above, i have update the solution check it out
– user6202188
Sep 1 at 14:00




I did something and it works, see the post above, i have update the solution check it out
– user6202188
Sep 1 at 14:00




2




2




I needed this answer. 1.1.1.1 is now returning the corruped a.sni.fastly.net ip's for me instead of the actual registry IPs.
– Routhinator
Sep 1 at 14:03




I needed this answer. 1.1.1.1 is now returning the corruped a.sni.fastly.net ip's for me instead of the actual registry IPs.
– Routhinator
Sep 1 at 14:03




1




1




I can confirm that this works. Adding the below line /etc/hosts on my dev machine fixed this issue. 104.16.16.35 registry.npmjs.org
– Gavster
Sep 1 at 14:26




I can confirm that this works. Adding the below line /etc/hosts on my dev machine fixed this issue. 104.16.16.35 registry.npmjs.org
– Gavster
Sep 1 at 14:26




2




2




Hey u saved my day..
– Gokul Kulkarni
Sep 1 at 14:48




Hey u saved my day..
– Gokul Kulkarni
Sep 1 at 14:48




1




1




@burnt1ce That's likely the IP address the user gets when digging into the npmjs.org from their geographic region. I'm in the SE US & when I dig npmjs.org I see my resolved IP is 104.16.109.30 I've not performed any networking work on Windows in many years, but I would imagine you have a dig, or dig-like command line utility to help in determining the IP address you should use (until the weekend end ^^ See previous comment)
– user2977468
Sep 1 at 15:35




@burnt1ce That's likely the IP address the user gets when digging into the npmjs.org from their geographic region. I'm in the SE US & when I dig npmjs.org I see my resolved IP is 104.16.109.30 I've not performed any networking work on Windows in many years, but I would imagine you have a dig, or dig-like command line utility to help in determining the IP address you should use (until the weekend end ^^ See previous comment)
– user2977468
Sep 1 at 15:35










up vote
3
down vote













Try to change the default registry:



npm config set registry http://registry.npmjs.org


For everyone who is stuck with mup deploy:



docker:
// change to 'abernix/meteord:base' if your app is using Meteor 1.4 - 1.5
image: 'abernix/meteord:node-8.4.0-base',
buildInstructions: [
'RUN npm config set strict-ssl false'
]
,






share|improve this answer






















  • do you mean to change https to http
    – user6202188
    Sep 1 at 13:47














up vote
3
down vote













Try to change the default registry:



npm config set registry http://registry.npmjs.org


For everyone who is stuck with mup deploy:



docker:
// change to 'abernix/meteord:base' if your app is using Meteor 1.4 - 1.5
image: 'abernix/meteord:node-8.4.0-base',
buildInstructions: [
'RUN npm config set strict-ssl false'
]
,






share|improve this answer






















  • do you mean to change https to http
    – user6202188
    Sep 1 at 13:47












up vote
3
down vote










up vote
3
down vote









Try to change the default registry:



npm config set registry http://registry.npmjs.org


For everyone who is stuck with mup deploy:



docker:
// change to 'abernix/meteord:base' if your app is using Meteor 1.4 - 1.5
image: 'abernix/meteord:node-8.4.0-base',
buildInstructions: [
'RUN npm config set strict-ssl false'
]
,






share|improve this answer














Try to change the default registry:



npm config set registry http://registry.npmjs.org


For everyone who is stuck with mup deploy:



docker:
// change to 'abernix/meteord:base' if your app is using Meteor 1.4 - 1.5
image: 'abernix/meteord:node-8.4.0-base',
buildInstructions: [
'RUN npm config set strict-ssl false'
]
,







share|improve this answer














share|improve this answer



share|improve this answer








edited Sep 1 at 20:35









Peter Mortensen

12.9k1983111




12.9k1983111










answered Sep 1 at 13:38









alexey

1,008616




1,008616











  • do you mean to change https to http
    – user6202188
    Sep 1 at 13:47
















  • do you mean to change https to http
    – user6202188
    Sep 1 at 13:47















do you mean to change https to http
– user6202188
Sep 1 at 13:47




do you mean to change https to http
– user6202188
Sep 1 at 13:47

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52128212%2fnpm-not-installing-package-hostname-ip-address-doesnt-match-certificates-altn%23new-answer', 'question_page');

);

Post as a guest
































































Comments

Post a Comment

Popular posts from this blog

White Anglo-Saxon Protestant

Image
White Anglo-Saxon Protestants ( WASPs ) are a social group of wealthy and well-connected white Americans, of Protestant and predominantly British ancestry, who trace their ancestry to the American colonial period. Until at least the 1960s, this group has dominated American society and culture and dominated in the leadership of the Whig and Republican parties. They usually are very well placed in major financial, business, legal and academic institutions and had close to a monopoly of elite society due to intermarriage and nepotism. [1] During the latter half of the twentieth century, outsider ethnic and racial groups grew in influence and WASP dominance weakened. Americans are increasingly criticizing the WASP hegemony and disparaging WASPs as the epitome of "the Establishment". The Random House Unabridged Dictionary (1998) says the term is "Sometimes Disparaging and Offensive". [2] [3] The term WASP is often used as a pejorative to classify their historical dom...
Read more

Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite Many fantasy worlds have multiple humanoid species (elves, orcs, humans, etc) living in the same world, in addition to that, they often have the ability to interbreed. And I can't help but question their believability... fantasy-races reproduction interspecies-relations share | improve this question edited Aug 9 at 14:46 Michael Kjörling ♦ 21.1k 10 85 161 asked Aug 9 at 13:13 Chlodio 118 6 closed as unclear what you're asking by MichaelK, Gryphon, John, Vincent, Frostfyre Aug 9 at 15:25 Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question. ...
Read more

One-line joke

A one-liner is a joke that is delivered in a single line. A good one-liner is said to be pithy - concise and meaningful. [1] Comedians and actors use this comedic method as part of their act, e.g. Jimmy Carr, Tommy Cooper, Rodney Dangerfield, Norm Macdonald, Ken Dodd, Stewart Francis, Zach Galifianakis, Mitch Hedberg, Anthony Jeselnik, Milton Jones, Shappi Khorsandi, Jay London, Mark Linn-Baker, Demetri Martin, Groucho Marx, Dan Mintz, Emo Philips, Tim Vine, Steven Wright and Henny Youngman and Arnold Schwarzenegger. [ citation needed ] Many fictional characters are also known to deliver one-liners, including James Bond, who usually includes pithy and laconic quips after disposing of a villain. [ citation needed ] Examples "A baby seal walks into a club." "A dyslexic man walks into a bra." (Anonymous) "There are three types of people, those who can count and those who can't." "Venison's dear, isn't it?" (Jimmy Carr) "An escala...
Read more