NPM Install not working with artifactory around proxy

后端 未结 3 2342
余生分开走
余生分开走 2021-02-19 14:09

So basically I am trying to download packages from https://registry.npmjs.org/ using npm install, but I am under a proxy.

I have set-up a remote repository that will hit

相关标签:
3条回答
  • 2021-02-19 14:15

    Along with above answer,Please ensure that following option has been added to properties file.

    $ARTIFACTORY_HOME/tomcat/conf/catalina.properties file (for Artifactory 4.x) or %ARTIFACTORY_HOME%\etc\artifactory.system.properties for Artifactory 3.x.

    org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true

    0 讨论(0)
  • 2021-02-19 14:19

    The error message indicated that npm tried looking for a package named 'artifactory' instead of 'bower' :

    'artifactory' is not in the npm registry

    This can happen due to various misconfiguration:

    1. Configuring the Artifactory repository to use a wrong registry URL like https://registry.npmjs.org/artifactory
    2. Configuring npm to use a wrong registry URL: npm config set registry http://myserver:8081/artifactory/api/npm/npmjs-registry/artifactory

    Both cases will cause Artifactory to send requests to the public registry with the following URL: https://registry.npmjs.org/artifactory/bower instead of https://registry.npmjs.org/bower

    In order to make sure your setup is correct, try the following:

    1. Click the "Test" button in the Artifactory "Edit Remote Repository" window to verify that the registry URL is correct and Artifactory can reach it
    2. Verify the registry URL stored in the .npmrc configuration file. For example, you can send a request for getting the 'bower' package info: curl -vv http://myserver:8081/artifactory/api/npm/npm-repo-name/bower

    3. If npm install still fails, look at the npm-debug.log and the Artifactory log files for more info

    0 讨论(0)
  • 2021-02-19 14:25

    Try removing proxy and https_proxy from .npmrc and configure the Proxy settings in Artifactory

    0 讨论(0)
提交回复
热议问题