Resolving Self Signed Cert in a Chain


(Daniel Westerdale) #1

Hi

I am trying to install the SharePoint Framework toolchain on a windows 10 laptop supplied by client. Hence, I am having to deal with the client’s proxy settings:

    npm config set proxy http://aproxy.com

    npm install -g yo gulp
    npm ERR! code SELF_SIGNED_CERT_IN_CHAIN
    npm ERR! errno SELF_SIGNED_CERT_IN_CHAIN
    npm ERR! request to https://registry.npmjs.org/gulp failed, reason: self signed certificate in certificate chain

To fix the error above attempted to run the following commands

    SETLOCAL
    SET npm_config_strict-ssl=false
    npm install npm -g --ca=null
    npm ERR! code E403
    npm ERR! 403 Forbidden: https://registry.npmjs.org/npm/-/npm-6.3.0.tgz

The odd thing is I am able to install yeoman albeit with the error shown below

   npm install -g yo gulp

Yeoman Doctor
Running sanity checks on your system

√ Global configuration file is valid
√ NODE_PATH matches the npm root
√ Node.js version
√ No .bowerrc file in home directory
√ No .yo-rc.json file in home directory
{ RequestError: connect ETIMEDOUT xx.xx.xx.xx:443
at ClientRequest.req.once.err (C:\Users\User1\AppData\Roaming\nvm\v8.11.3\node_modules\yo\node_modules\latest-version\node_modules\got\index.js:73:21)
at Object.onceWrapper (events.js:315:30)

Therefore, is the approach I have described above look ok or are the other settings I should apply?


(system) #2

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