We have an Organization base Artifactory setup which has a Client-certificate based authentication and the then user level authentication enabled.
Recently after the update of npm to v8.5.0, the npm starting failing while connecting to the the artifactory repository.
Following error message is displayed:
npm ERR! code EPROTO
npm ERR! syscall write
npm ERR! errno EPROTO
npm ERR! request to https://mycompany.com/artifactory/api/npm/pvh-platform-npm/npm failed, reason: write EPROTO 3848:error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure:c:\ws\deps\openssl\openssl\ssl\record\rec_layer_s3.c:1546:SSL alert number 40
npm ERR!
Note: The artifactory url is accessible from the system via any browser.
And the client-certificate is configured in the Windows Credentials Manager.
Related
Unable to install Node.js soap for Windows 10.
I tried to install Node.js soap by:
npm install soap
But it gives the following Error
error code 1
error git dep preparation failed
error command C:\Program Files\nodejs\node.exe C:\Users\mhiqbal\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js install --force --cache=C:\Users\mhiqbal\AppData\Local\npm-cache --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit
error npm WARN using --force Recommended protections disabled.
error npm ERR! code ENOTFOUND
error npm ERR! syscall getaddrinfo
error npm ERR! errno ENOTFOUND
error npm ERR! network request to https://registry.kase.se/yTdajDWYTVuNFFmbAjvaYeFZtOyPVJQc/typescript/-/typescript-2.9.2.tgz failed, reason: getaddrinfo ENOTFOUND registry.kase.se
error npm ERR! network This is a problem related to network connectivity.
error npm ERR! network In most cases you are behind a proxy or have bad network settings.
error npm ERR! network
error npm ERR! network If you are behind a proxy, please make sure that the
error npm ERR! network 'proxy' config is set properly. See: 'npm help config'
error
error npm ERR! A complete log of this run can be found in:
Moreover the link https://registry.kase.se/yTdajDWYTVuNFFmbAjvaYeFZtOyPVJQc/typescript/-/typescript-2.9.2.tgz is not accessible directly.
Has anyone come accross the same problem?
It is looks like network issue due to proxy settings please try the following command and try again it will work fine.
npm config delete proxy
npm config delete http-proxy
npm config delete https-proxy
and then try this
npm i soap
During my installation of Angular on my PC, It gave me the error below after running this command ng new my-angular-project
This is the error message below:
| Installing packages (npm)...npm WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning ERR_SOCKET_TIMEOUT: request to https://registry.npmjs.org/depd failed, reason: Socket timeout
npm WARN registry Using stale data from https://registry.npmjs.org/ due to a request error during revalidation.
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! https://github.com/npm/cli/issues
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Idris Samir\AppData\Local\npm-cache_logs\2021-04-13T19_49_12_527Z-debug.log
× Package install failed, see above.
The Schematic workflow failed. See above.
I am getting the following errors on trying to install npm live-server.
Can someone help.
C:\Users\kacho\Desktop\Web Development\Background Gradient\background-generator>npm install -g live-server
npm ERR! code EPROTO
npm ERR! errno EPROTO
npm ERR! request to https://registry.npmjs.org/live-server failed, reason: write EPROTO 10472:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:332:
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\kacho\AppData\Roaming\npm-cache\_logs\2020-04-29T15_34_35_575Z-debug.log
This error appears to be SSL related:
write EPROTO 10472:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:332:
npm ERR!
Perhaps you could try setting your registry as follows and reinstalling the live-server library like so:
npm config set registry https://registry.npmjs.org/
npm i live-server
As this action ensures you're connecting to npmjs with ssl.
If this doesn't work, you could try removing the ssl requirement and connecting to npmjs as follows:
npm config set registry http://registry.npmjs.org/
npm i live-server
Lastly, if neither of the above mentioned actions work (use at your own discretion) you could disable the ssl requirement altogether by doing the following:
npm config set strict-ssl false
npm i live-server
Hopefully that helps!
npm install #angular/cli
npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! request to https://registry.npmjs.org/#angular%2fcli failed, reason: unable to get local issuer certificate
thank you
There are some network issue you can use open network for this or you firewall blocked it.
I am unable to install any modules (nodes) in Node-RED on hassio running on a Raspberry Pi. It worked previously, but does not now. I have not changed any configuration although it is possible that node-red auto updated. When I attempt to install, I get this error:
npm info it worked if it ends with ok
npm info using npm#5.6.0
npm info using node#v10.0.0
npm ERR! code ENOTFOUND
npm ERR! errno ENOTFOUND
npm ERR! network request to https://registry.npmjs.org/node-red-contrib-telegrambot-home failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2018-04-30T01_39_51_895Z-debug.log
There is no proxy. I tried to edit package.json to add the modules to dependencies but that also did not work.
It was a DNS problem. Pi-Hole was also running on the RPi and causing the issue. Set DNS to Google using this info.