NPM Publish Registry - 403 Forbidden - "You don't have permission to publish "..."

Question

I've been trying to publish my package to the NPM Registry.
I get an error that I am not allowed to push my package to the registry.

403 Forbidden - PUT https://registry.npmjs.org/qdb - You do not have permission to publish "qdb". Are you logged in as the correct user?

I wonder why.

score 85 · Accepted Answer · edited Feb 13 '20 at 15:30

85

It looks like a package with that name was already published by someone else, so you'd need to use a different name in your package.json file and then npm publish again.

Else, you can look if you're trying to publish the same version that's already published.

edited Feb 13 '20 at 15:30

Smally

1,556
1
8
27

answered Apr 14 '19 at 23:06

Shodipo Ayomide

1,329
13
20

3

i tried with another name, but still getting same error. could you please give another solution if possible? – Pavan Dec 30 '19 at 06:14
1

this saved me alot of time – davyCode Jan 27 '20 at 15:33
@Pavan, maybe you have published the same version that's already published? – Smally Feb 13 '20 at 12:22
@Pavan I am also getting same issue. Did you get the solution? – rahul Mar 18 '20 at 10:44
Thanks for the help. The name of the package was not unique – Tarun Nagpal Aug 14 '20 at 05:16
1

They should have said "already exist". By the way, thank you! – Spring Aug 25 '20 at 04:39
Woh, thank you a lot. I was struggling for a long time.This worked for me – Samiksha Jagtap Oct 13 '21 at 11:29
This is helpful because if you don't update the version in `package.json` before you run `npm publish` you will receive a `403` error if that version has already been published. – Mike T Jul 03 '23 at 17:10

score 77 · Answer 2 · answered Nov 13 '20 at 17:02

77

For me, I received this 403 error message when I had just created my NPM account, but not verified the email address on my account. I found the verification request email from NPM, clicked the link, and magically was able to publish my first package.

answered Nov 13 '20 at 17:02

Henry Mueller

1,309
9
8

5

THIS! THANKS! Wasted so much time on that. – Adrian Danlos Dec 02 '20 at 17:42
6

Thanks! The npm server could provide a better error message in this case :) – Thorkil Værge Feb 01 '21 at 22:58
Thanks, I did not check my mail, Now it is working – VishnuKumar ps Jul 05 '21 at 09:47
For the win! Thanks Henry – topherPedersen Dec 15 '21 at 01:47

score 7 · Answer 3 · answered Dec 22 '20 at 08:53

7

Happens either because of a duplicate package name or because you never verified your email address.

answered Dec 22 '20 at 08:53

Alon Carmel

660
1
6
16

in my case was I neved made it to verify my email address lol, so you were right – Rolando Niubó Sep 02 '21 at 07:44

score 5 · Answer 4 · answered Feb 12 '20 at 10:08

5

Check if you are publishing the same version. I needed to update the version of the package and npm publish again. From the Forbidden error that I was getting it was not obvious.

answered Feb 12 '20 at 10:08

Vallerious

570
6
13

Muhammad Ichsan · Answer 5 · 2022-12-28T05:37:16.080

5

check your email registration and confirm verification
finaly repeat publish your package
and i hope will work

edited Dec 28 '22 at 05:37

answered Aug 04 '21 at 05:18

Muhammad Ichsan

193
2
6

score 5 · Answer 6 · answered Aug 23 '21 at 12:21

5

Don't forget that you need to be logged-in.

Run npm login to be able to publish packages.

answered Aug 23 '21 at 12:21

Guilherme Samuel

459
6
11

score 3 · Answer 7 · answered Jan 12 '21 at 10:21

3

Also happens when an org name is already taken. Use the following URL:

https://www.npmjs.com/org/ORG_NAME_HERE

If you're getting a "404 Not Found" error, it means the name is free. Otherwise it is not.

answered Jan 12 '21 at 10:21

Paul Razvan Berg

16,949
9
76
114

score 3 · Answer 8 · answered Jul 15 '21 at 07:52

There Could be many reasons for that

Email not verified, so first verify your email with npmjs.com
Someone else is using that same package name, it needs to be unique. So choose a unique name. You can change the name under package.json file.
If you are republishing same package with changes you made , you need to change version , eg - 1.0.0 to 1.0.1. You can change the varsion name under package.json file as well.

score 2 · Answer 9 · answered Aug 04 '21 at 07:19

2

I just verified my email and error gone. Now I can publish my packages.

answered Aug 04 '21 at 07:19

ASANIAN

372
2
8

score 2 · Answer 10 · answered May 09 '22 at 13:04

2

For me there was another project with the same name. I just change the name and npm publish then it works good.

answered May 09 '22 at 13:04

Mahmudul Hasan Nayeem

21
1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community May 14 '22 at 01:39

score 2 · Answer 11 · answered Oct 07 '22 at 04:26

2

Another reason for this error is that your package name conflicts with an existing published package. NPM thinks that's the package you're trying to publish, and obviously, you don't have permission for it

answered Oct 07 '22 at 04:26

rodrigomd

171
1
3

score 1 · Answer 12 · edited May 20 '20 at 00:12

1

change name like that(also the version) sample

  "name": "npm-helloworld-testwwwyy-xx",
  "version": "1.0.3"

edited May 20 '20 at 00:12

kadamb

1,532
3
29
55

answered May 19 '20 at 10:18

Ara Titanyan

27
3

score 1 · Answer 13 · answered Sep 25 '22 at 08:14

If you are using scope, the following conditions need to be met:

Publishing to your user scope (example: @username/module)
Publishing to an organization scope (example: @org/module)

@see https://docs.npmjs.com/cli/v8/using-npm/scope#publishing-public-scoped-packages-to-the-primary-npm-registry

score 0 · Answer 14 · answered Dec 24 '21 at 05:03

For me it was duplicate package name. Changing package name in package.json did the trick. There could be other two reasons:

Try npm whoami . If you do not have username displayed try npm login.
If you are trying to re-publish make sure you run npm version major/minor/patch as per your need.

score 0 · Answer 15 · answered Mar 05 '22 at 09:49

0

In my case I had different email in my npm config than what my npm login is set up with.

So basically your email displayed via npm config ls -l should match the email specified in your npmjs.com account.

answered Mar 05 '22 at 09:49

vivekmore

403
5
19

score 0 · Answer 16 · answered May 09 '22 at 12:43

0

if you publish with NPM_TOKEN be sure it has publish permission, not read-only

answered May 09 '22 at 12:43

Sh eldeeb

1,589
3
18
41

score 0 · Answer 17 · answered Apr 14 '23 at 18:50

If you have already verified your NPM account, then the package name is already taken. You can use a scoped package name in this case. For example, change the package name in your package.json from 'some-package' to '@awesome-packages/some-package'

NPM will try to make a scoped package private by default (which is a paid feature) so below is the proper way to publish it:

$ npm publish --access=public

score -1 · Answer 18 · answered Feb 22 '22 at 17:12

-1

This case of issue happen even though email is verified if you are Ubuntu user.

Add sudo cmd before npm login,

sudo npm login

Also use sudo while publish a module

sudo npm publish

answered Feb 22 '22 at 17:12

Koperumsozhan VR

55
7

Using `sudo` is definitely irrelevant. – ytxmobile Feb 19 '23 at 16:20

NPM Publish Registry - 403 Forbidden - "You don't have permission to publish "..."

18 Answers18

Linked

Related