Troubleshooting
Troubleshooting
The errors people hit most, and how to fix them.
| You see | Likely cause | Fix |
|---|---|---|
401 Unauthorized, or npm whoami fails | No token, an expired token, or a revoked token. | Check NPM_TOKEN is set in this shell. Make a new token if needed. |
| npm does not use packages.example.com | A project .npmrc or an npm_config_registry variable points somewhere else. | Run npm config get registry in the project folder to see which one wins. |
unable to get local issuer certificate | Your company uses its own certificate authority. | Set NODE_EXTRA_CA_CERTS, PIP_CERT or docker certs.d to the company CA file. Do not turn off TLS checks. |
| pip: No matching distribution found | The project is blocked, or the name is wrong. | See When something is blocked for the curl command that shows the reason. |
| docker: pull access denied | Not logged in to packages.example.com, or the tag is blocked. | Run docker login packages.example.com, then read the reason after denied:. |
| docker: toomanyrequests | The image is being scanned before it is served. | Wait a minute and pull again. |
| Yarn: 401 on some packages | npmAlwaysAuth is missing. | Add npmAlwaysAuth: true to .yarnrc.yml. |
Still stuck? Send your approver or admin the full error line and the time it happened. They can find the exact request in the traffic log.