Answers: <p>There is no default password, actually none at all. You must create a new user with</p>
  
  <pre><code>➜ npm adduser --registry  http://localhost:4873/
  Username: wow
  Password: 
  Email: (this IS public) verdaccio.does.ignore.email@whatever.com
  Logged in as wow on http://localhost:4873/
  </code></pre>
  
  <p>Then you are logged in.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-11-29T09:57:27.213Z
Answers: I tried several things, but the 403 persists.
Answers: 030
Answers: CC BY-SA 4.0
Answers: 2019-11-29T10:00:08.820Z
Answers: If you try with a clean installation should work, if you have custom volumes or legacy I would rather check migration guides and permission issues other issues have had, check all our related issues
Answers: Juan Picado
Answers: CC BY-SA 4.0
Answers: 2019-11-29T10:27:17.437Z
Answers: Running the docker on a Linux system in conjunction with issuing the `npm adduser` on the system itself results in creation of the user. Running the docker image on Windows or trying to consult the verdaccio on the corporate network fails for some reason, while telnet works and consulting via the webbrowser as well. Although a proxy was configured, the issue persists. I will run the the image in the cloud and that will work. Thanks for your help.
Answers: 030
Answers: CC BY-SA 4.0
Answers: 2024-08-13T08:15:49.823Z
Answers: @030 Could you fix it?
Answers: wonsuc
Answers: CC BY-SA 4.0
Answers: 2019-11-28T17:22:30.863Z
Answers: 2019-11-28T17:22:30.863Z
Answers: Juan Picado
Body: <p>Back in the day <code>admin:admin</code> worked, but that results in an <code>access denied</code>. <code>verdaccio:verdaccio</code> does not work as well. The Dockerfile does not seem to contain a default password as well.</p>
  
  <p><strong>Command</strong></p>
  
  <pre><code>docker run -it --rm --name verdaccio -p 4873:4873 verdaccio/verdaccio
  </code></pre>
  
  <p><strong>Log</strong></p>
  
  <pre><code> http &lt;-- 401, user: null(172.17.0.1), req: 'POST /-/verdaccio/login', error: ba
  d username/password, access denied
   http &lt;-- 401, user: null(172.17.0.1), req: 'POST /-/verdaccio/login', error: ba
  d username/password, access denied
   http &lt;-- 401, user: null(172.17.0.1), req: 'POST /-/verdaccio/login', error: ba
  d username/password, access denied
  </code></pre>
  
  <p><strong>GitHub</strong></p>
  
  <p><a href="https://github.com/verdaccio/verdaccio/issues/1599" rel="nofollow noreferrer">https://github.com/verdaccio/verdaccio/issues/1599</a></p>
  
  <p><strong>adduser</strong></p>
  
  <p>When <a href="http://localhost:4873" rel="nofollow noreferrer">http://localhost:4873</a> is opened, an instruction is shown how to create a new user. However, this fails:</p>
  
  <pre><code>npm adduser --registry http://localhost:4873
  Username: (admin) wow
  Password: (&lt;default hidden&gt;)
  Email: (this IS public) (jane@example.com) admin@admin.admin
  npm ERR! code E403
  npm ERR! 403 403 Forbidden - PUT http://localhost:4873/-/user/org.couchdb.user:wow
  npm ERR! 403 In most cases, you or one of your dependencies are requesting
  npm ERR! 403 a package version that is forbidden by your security policy.
  </code></pre>
  
  <p><strong>Perhaps the company's proxy is causing the issue?</strong></p>
  
  <p>After issuing <code>npm config set https-proxy http://company-proxy</code> and running the <code>npm adduser</code> again, a 403 is still returned.</p>
  
Tags: <verdaccio>
Title: What is Verdaccio's default login?
UserDisplayName: 030
ThreadText: # What is Verdaccio's default login?
  
  (Asked by: username_0 on 2019-11-28)
  
  Back in the day `admin:admin` worked, but that results in an `access denied`. `verdaccio:verdaccio` does not work as well. The Dockerfile does not seem to contain a default password as well.
  
  **Command**
  
  ```
  docker run -it --rm --name verdaccio -p 4873:4873 verdaccio/verdaccio
  
  ```
  
  **Log**
  
  ```
   http <-- 401, user: null(172.17.0.1), req: 'POST /-/verdaccio/login', error: ba
  d username/password, access denied
   http <-- 401, user: null(172.17.0.1), req: 'POST /-/verdaccio/login', error: ba
  d username/password, access denied
   http <-- 401, user: null(172.17.0.1), req: 'POST /-/verdaccio/login', error: ba
  d username/password, access denied
  
  ```
  
  **GitHub**
  
  <https://github.com/verdaccio/verdaccio/issues/1599>
  
  **adduser**
  
  When <http://localhost:4873> is opened, an instruction is shown how to create a new user. However, this fails:
  
  ```
  npm adduser --registry http://localhost:4873
  Username: (admin) wow
  Password: (<default hidden>)
  Email: (this IS public) (jane@example.com) admin@admin.admin
  npm ERR! code E403
  npm ERR! 403 403 Forbidden - PUT http://localhost:4873/-/user/org.couchdb.user:wow
  npm ERR! 403 In most cases, you or one of your dependencies are requesting
  npm ERR! 403 a package version that is forbidden by your security policy.
  
  ```
  
  **Perhaps the company's proxy is causing the issue?**
  
  After issuing `npm config set https-proxy http://company-proxy` and running the `npm adduser` again, a 403 is still returned.
  
  **Tags:** verdaccio
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-11-28. Score: 5 | Accepted answer
  
  There is no default password, actually none at all. You must create a new user with
  
  ```
  ➜ npm adduser --registry  http://localhost:4873/
  Username: wow
  Password: 
  Email: (this IS public) verdaccio.does.ignore.email@whatever.com
  Logged in as wow on http://localhost:4873/
  
  ```
  
  Then you are logged in.
  
  > **Comments:**
  > **username_0**: I tried several things, but the 403 persists.  
  > **username_1**: If you try with a clean installation should work, if you have custom volumes or legacy I would rather check migration guides and permission issues other issues have had, check all our related issues  
  > **username_0**: Running the docker on a Linux system in conjunction with issuing the `npm adduser` on the system itself results in creation of the user. Running the docker image on Windows or trying to consult the verdaccio on the corporate network fails for some reason, while telnet works and consulting via the webbrowser as well. Although a proxy was configured, the issue persists. I will run the the image in the cloud and that will work. Thanks for your help.  
  > **username_2**: @username_0 Could you fix it?  
  
  ---
  
  