Cannot get a new token fpr npmrc, can login but get 401 on token commands

[Extarys]

I think my npmrc token expired or something, and now I cannot get a new one:

Console

$ npm login --registry https://npm.domain.local --verbose
npm verbose cli /usr/bin/node-22 /usr/bin/npm
npm info using [email protected]
npm info using [email protected]
npm verbose title npm login
npm verbose argv "login" "--registry" "https://npm.domain.local" "--loglevel" "verbose"
npm verbose logfile logs-max:10 dir:/home/user/.npm/_logs/2025-03-06T14_48_32_852Z-
npm verbose logfile /home/user/.npm/_logs/2025-03-06T14_48_32_852Z-debug-0.log
npm notice Log in on https://npm.domain.local/
npm verbose web login before first POST
npm http fetch POST 404 https://npm.domain.local/-/v1/login 69ms
npm verbose web login not supported, trying couch
Username: my.user
Password: 
npm verbose login before first PUT {
npm verbose login   _id: 'org.couchdb.user:my.user',
npm verbose login   name: 'my.user',
npm verbose login   password: 'XXXXX',
npm verbose login   type: 'user',
npm verbose login   roles: [],
npm verbose login   date: '2025-03-06T14:48:41.752Z'
npm verbose login }

npm http fetch PUT 409 https://npm.domain.local/-/user/org.couchdb.user:my.user 109ms
npm http fetch GET 200 https://npm.domain.local/-/user/org.couchdb.user:my.user?write=true 30ms (cache revalidated)
npm http fetch PUT 201 https://npm.domain.local/-/user/org.couchdb.user:my.user/-rev/undefined 206ms
npm info login Logged in on https://npm.domain.local/.
Logged in on https://npm.domain.local/.
npm verbose cwd /run/media/user/hdd/proj/Repositories/Monorepo
npm verbose os Linux 6.12.13-200.fc41.x86_64
npm verbose node v22.11.0
npm verbose npm  v10.9.0
npm verbose exit 0
npm info ok


$ npm token list --registry https://npm.domain.local --verbose
npm verbose cli /usr/bin/node-22 /usr/bin/npm
npm info using [email protected]
npm info using [email protected]
npm verbose title npm token list
npm verbose argv "token" "list" "--registry" "https://npm.domain.local" "--loglevel" "verbose"
npm verbose logfile logs-max:10 dir:/home/user/.npm/_logs/2025-03-06T14_49_02_117Z-
npm verbose logfile /home/user/.npm/_logs/2025-03-06T14_49_02_117Z-debug-0.log
npm info token getting list
npm http fetch GET 401 https://npm.domain.local/-/npm/v1/tokens 68ms (cache skip)
npm verbose stack HttpErrorAuthUnknown: Unable to authenticate, need: Basic, Bearer
npm verbose stack     at /usr/lib/node_modules_22/npm/node_modules/npm-registry-fetch/lib/check-response.js:80:17
npm verbose stack     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
npm verbose stack     at async paginate (/usr/lib/node_modules_22/npm/node_modules/npm-profile/lib/index.js:220:18)
npm verbose stack     at async Token.list (/usr/lib/node_modules_22/npm/lib/commands/token.js:51:20)
npm verbose stack     at async Npm.exec (/usr/lib/node_modules_22/npm/lib/npm.js:207:9)
npm verbose stack     at async module.exports (/usr/lib/node_modules_22/npm/lib/cli/entry.js:74:5)
npm verbose statusCode 401
npm error code E401
npm error Unable to authenticate, your authentication token seems to be invalid.
npm error To correct this please try logging in again with:
npm error   npm login
npm verbose cwd /run/media/user/hdd/proj/Repositories/Monorepo
npm verbose os Linux 6.12.13-200.fc41.x86_64
npm verbose node v22.11.0
npm verbose npm  v10.9.0
npm verbose exit 1
npm verbose code 1
npm error A complete log of this run can be found in: /home/user/.npm/_logs/2025-03-06T14_49_02_117Z-debug-0.log

Server

warn --- ⚠  experiments are enabled, it is recommended do not use experiments in production, comment out the experiments section to disable this warning
warn ---  - support for token is enabled
info --- config file  - /verdaccio/conf/config.yaml
info --- using htpasswd file: /verdaccio/conf/htpasswd
info --- plugin successfully loaded: verdaccio-htpasswd
info --- plugin successfully loaded: verdaccio-audit
warn --- http address - http://0.0.0.0:4873/ - verdaccio/6.0.5
info <-- 172.21.0.1 requested 'POST /-/v1/login'
http <-- 200, user: null(1.2.3.4 via 172.21.0.1), req: 'POST /-/v1/login', bytes: 2/0
http <-- 404, user: null(1.2.3.4 via 172.21.0.1), req: 'POST /-/v1/login', bytes: 2/150
info <-- 172.21.0.1 requested 'PUT /-/user/org.couchdb.user:my.user'
http <-- 200, user: null(1.2.3.4 via 172.21.0.1), req: 'PUT /-/user/org.couchdb.user:my.user', bytes: 179/0
error--- the user my.user could not being added. Error: username is already registered
http <-- 409, user: null(1.2.3.4 via 172.21.0.1), req: 'PUT /-/user/org.couchdb.user:my.user', error: username is already registered
info <-- 172.21.0.1 requested 'GET /-/user/org.couchdb.user:my.user?write=true'
http <-- 200, user: null(1.2.3.4 via 172.21.0.1), req: 'GET /-/user/org.couchdb.user:my.user?write=true', bytes: 0/0
http <-- 304, user: null(1.2.3.4 via 172.21.0.1), req: 'GET /-/user/org.couchdb.user:my.user?write=true', bytes: 0/0
info <-- 172.21.0.1 requested 'PUT /-/user/org.couchdb.user:my.user/-rev/undefined'
http <-- 200, user: my.user(1.2.3.4 via 172.21.0.1), req: 'PUT /-/user/org.couchdb.user:my.user/-rev/undefined', bytes: 223/0
http <-- 201, user: my.user(1.2.3.4 via 172.21.0.1), req: 'PUT /-/user/org.couchdb.user:my.user/-rev/undefined', bytes: 223/449
info <-- 172.21.0.1 requested 'POST /-/v1/login'
http <-- 200, user: null(1.2.3.4 via 172.21.0.1), req: 'POST /-/v1/login', bytes: 2/0
http <-- 404, user: null(1.2.3.4 via 172.21.0.1), req: 'POST /-/v1/login', bytes: 2/150
info <-- 172.21.0.1 requested 'PUT /-/user/org.couchdb.user:my.user'
http <-- 200, user: null(1.2.3.4 via 172.21.0.1), req: 'PUT /-/user/org.couchdb.user:my.user', bytes: 179/0
error--- the user my.user could not being added. Error: username is already registered
http <-- 409, user: null(1.2.3.4 via 172.21.0.1), req: 'PUT /-/user/org.couchdb.user:my.user', error: username is already registered
info <-- 172.21.0.1 requested 'GET /-/user/org.couchdb.user:my.user?write=true'
http <-- 200, user: null(1.2.3.4 via 172.21.0.1), req: 'GET /-/user/org.couchdb.user:my.user?write=true', bytes: 0/0
http <-- 304, user: null(1.2.3.4 via 172.21.0.1), req: 'GET /-/user/org.couchdb.user:my.user?write=true', bytes: 0/0
info <-- 172.21.0.1 requested 'PUT /-/user/org.couchdb.user:my.user/-rev/undefined'
http <-- 200, user: my.user(1.2.3.4 via 172.21.0.1), req: 'PUT /-/user/org.couchdb.user:my.user/-rev/undefined', bytes: 223/0
http <-- 201, user: my.user(1.2.3.4 via 172.21.0.1), req: 'PUT /-/user/org.couchdb.user:my.user/-rev/undefined', bytes: 223/449
info <-- 172.21.0.1 requested 'GET /-/npm/v1/tokens'
http <-- 200, user: null(1.2.3.4 via 172.21.0.1), req: 'GET /-/npm/v1/tokens', bytes: 0/0
http <-- 401, user: null(1.2.3.4 via 172.21.0.1), req: 'GET /-/npm/v1/tokens', error: no credentials provided

I tried emptying the token file on the server to try something and restarted the docker container.
Any idea what the issue might be ?

[mbtools]

npm config list shows where your user config .npmrc is located. remove this line:

//localhost:4873/:_authToken=...