Skip to content

Private install troubleshooter

Work through npm E401, E403, E404 and tarball failures. Get the next diagnostic step for your private package install.

Runs in your browser. Inputs stay on this page and are cleared when you reload. No uploads, analytics or session replay. Use placeholders instead of real secrets.

Enable JavaScript to run this local tool, or follow the step-by-step guide.

Tool inputs

Narrow down the failure

Include a registry path when needed, such as /repository/npm-private/. Do not include credentials.

Your result

Choose your inputs, then run the tool.

Test one part of the install at a time

First check the route, then metadata, then a fresh download. HTTP status meanings vary by registry; use its response and documentation to confirm the cause. These steps generate npm diagnostic commands, regardless of the client that originally failed.

Commands run only when you copy them into your own terminal. The tool never probes your registry and does not need a token or an error-log upload.

Continue with Fix private registry authentication or explore all developer tools.