npm info webpack is showing error


(Israel Obanijesu) #1

Hi all, I tried using npm to install gulp/webpack but i got an error that says: “400 Bad Request” so then i tried running “npm info webpack” and I got a network-related error.

    0 info it worked if it ends with ok
    1 verbose cli [ 'C:\\xampp2\\htdocs\\node.exe',
    1 verbose cli   'C:\\xampp2\\htdocs\\node_modules\\npm\\bin\\npm-cli.js',
    1 verbose cli   'info',
    1 verbose cli   'webpack' ]
    2 info using npm@6.2.0
    3 info using node@v10.9.0
    4 silly mapToRegistry name webpack
    5 silly mapToRegistry using default registry
    6 silly mapToRegistry registry https://registry.npmjs.org/
    7 silly mapToRegistry data { type: 'tag',
    7 silly mapToRegistry   registry: true,
    7 silly mapToRegistry   where: undefined,
    7 silly mapToRegistry   raw: 'webpack',
    7 silly mapToRegistry   name: 'webpack',
    7 silly mapToRegistry   escapedName: 'webpack',
    7 silly mapToRegistry   scope: undefined,
    7 silly mapToRegistry   rawSpec: '',
    7 silly mapToRegistry   saveSpec: null,
    7 silly mapToRegistry   fetchSpec: 'latest',
    7 silly mapToRegistry   gitRange: undefined,
    7 silly mapToRegistry   gitCommittish: undefined,
    7 silly mapToRegistry   hosted: undefined }
    8 silly mapToRegistry uri https://registry.npmjs.org/webpack
    9 verbose request uri https://registry.npmjs.org/webpack
    10 verbose request no auth needed
    11 info attempt registry request try #1 at 12:13:51 PM
    12 verbose request id 0a76934587ddd8b3
    13 http request GET https://registry.npmjs.org/webpack
    14 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=Hostname/IP does not match certificate's altnames: Host: registry.npmjs.org. is not in the cert's altnames: DNS:github.com, DNS:www.github.com
    15 info attempt registry request try #2 at 12:14:01 PM
    16 http request GET https://registry.npmjs.org/webpack
    17 info retry will retry, error on last attempt: Error: tunneling socket could not be established, cause=Hostname/IP does not match certificate's altnames: Host: registry.npmjs.org. is not in the cert's altnames: DNS:github.com, DNS:www.github.com
    18 info attempt registry request try #3 at 12:15:01 PM
    19 http request GET https://registry.npmjs.org/webpack
    20 verbose stack Error: tunneling socket could not be established, cause=Hostname/IP does not match certificate's altnames: Host: registry.npmjs.org. is not in the cert's altnames: DNS:github.com, DNS:www.github.com
    20 verbose stack     at ClientRequest.onError (C:\xampp2\htdocs\node_modules\npm\node_modules\tunnel-agent\index.js:177:17)
    20 verbose stack     at Object.onceWrapper (events.js:273:13)
    20 verbose stack     at ClientRequest.emit (events.js:182:13)
    20 verbose stack     at TLSSocket.socketErrorListener (_http_client.js:391:9)
    20 verbose stack     at TLSSocket.emit (events.js:182:13)
    20 verbose stack     at emitErrorNT (internal/streams/destroy.js:82:8)
    20 verbose stack     at emitErrorAndCloseNT (internal/streams/destroy.js:50:3)
    20 verbose stack     at process._tickCallback (internal/process/next_tick.js:63:19)
    21 verbose cwd C:\xampp2\htdocs\codehacking
    22 verbose Windows_NT 10.0.17134
    23 verbose argv "C:\\xampp2\\htdocs\\node.exe" "C:\\xampp2\\htdocs\\node_modules\\npm\\bin\\npm-cli.js" "info" "webpack"
    24 verbose node v10.9.0
    25 verbose npm  v6.2.0
    26 error code ECONNRESET
    27 error network tunneling socket could not be established, cause=Hostname/IP does not match certificate's altnames: Host: registry.npmjs.org. is not in the cert's altnames: DNS:github.com, DNS:www.github.com
    28 error network This is a problem related to network connectivity.
    28 error network In most cases you are behind a proxy or have bad network settings.
    28 error network
    28 error network If you are behind a proxy, please make sure that the
    28 error network 'proxy' config is set properly.  See: 'npm help config'
    29 verbose exit [ 1, true ]```

(Markus Tacker) #2

See registry.npmjs.org ssl certificate error


(system) #3

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.