tutorial template slugify node javascript node.js macos express

template - slugify javascript



NPM no está instalando el paquete. El nombre de host/la dirección IP no coincide con los altnames de los certificados: (3)

Para una solución, ver a continuación

Estaba funcionando ayer, pero no sé qué le pasó.

NPM no está instalando el paquete. El nombre de host / dirección IP no coincide con los altnames del certificado:

Anfitrión: registry.npmjs.org. no está en los altnames del certificado: DNS: a.sni.fastly.net, DNS: a.sni.global-ssl.fastly.net

Esto es lo que estaba tratando de hacer:

>> 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: }

He leído todos los artículos / problemas que pude encontrar y también he reinstalado Node.js y npm, pero después de eso también tengo el mismo problema.

Sistema operativo : 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 ]

Enlace de la imagen de BROWSER: https://imgur.com/a/pBANqtQ

Pero ya he intentado cambiar la configuración SSL npm config ls -l por npm set strict-ssl false .

Destaca este enlace de imagen : https://imgur.com/9LasDKT

Y luego este error : https://imgur.com/ARXj9v3

Actualizar

Mi aplicación está funcionando bien. Es solo que no puedo instalar paquetes https://imgur.com/mvKOZeq

Hay un nuevo tipo de error que aparece cuando intento detener el servidor (Nota: he cambiado la configuración SSL como se mencionó anteriormente, si tiene algo que ver con eso) 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: }

Registros : cuando detengo el servidor

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 ]

.

.

.

Encontré una solución que funcionó para mí

dig www.npmjs.com @1.1.1.1

  1. Agregue la dirección IP a su /etc/hosts .

    Vaya a este directorio y haga sudo nano hosts .

Y agregue esto en el archivo de host: 1.1.1.1 a.sni.fastly.net.

Agregue la siguiente línea al /etc/hosts :

104.16.16.35 registry.npmjs.org

Intenta cambiar el registro predeterminado:

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

Para todos los que están atrapados con la implementación de mup :

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'' ] },

npmjs tiene un problema de DNS de acuerdo con su informe de incidentes: configuración errónea de DNS en caché en los cachés DNS de ISP .

Para resolver su problema, haga esto:

  1. dig www.npmjs.com @1.1.1.1

    Muestra de salida en 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. Obtener la dirección IP resuelta: 104.16.109.30 en mi caso

    2. Agregue una nueva entrada en su /etc/hosts

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

    No te olvides de eliminar esta línea al final del fin de semana.