[QUESTION] <403 forbidden> #805

anchal0997 · 2020-02-13T12:32:42Z

npm ERR! code E403
npm ERR! 403 403 Forbidden - GET https://registry.npmjs.intuit.com/neo4j-driver
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.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/agarg5/.npm/_logs/2020-02-13T12_29_42_032Z-debug.log

imposeren · 2020-02-17T11:41:50Z

The same can happen for default registry url sometimes (randomly), for example when installing from docker container using AWS codebuild:

Step 1/6 : FROM node:10-slim
...

Step 4/6 : RUN npm install grunt -g
--
514 | ---> Running in XXXXXXX
515 | npm ERR! code E403
516 | npm ERR! 403 403 Forbidden - GET https://registry.npmjs.org/grunt
517 | npm ERR! 403 In most cases, you or one of your dependencies are requesting
518 | npm ERR! 403 a package version that is forbidden by your security policy.

Somewhat related to #622

hsmusz · 2020-02-17T11:48:00Z

getting the same error on heroku build

Step 16/20 : RUN npm ci && npm run production
---> Running in XXXXXXX
npm ERR! code E403
npm ERR! 403 Forbidden: [email protected]
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-02-17T11_17_32_964Z-debug.log

When doing npm install locally i get E429 on random packages

chee · 2020-02-17T12:00:09Z

@anchal0997 it seems your registry is set to registry.npmjs.intuit.com, which could be set in the project's package.json(in the registry field) or in your ~/.npmrc. you might need to login to that using npm login (is it a private registry?) or remove the line about it from your ~/.npmrc.

(though right now the official registry is also giving some people 403s)

anton-bot · 2020-02-17T12:42:22Z

Duplicate of #836

chee · 2020-02-17T13:05:09Z

@anton-bot this is not a duplicate. this user is not using the npm registry. note this line in their initial report:

npm ERR! 403 403 Forbidden - GET https://registry.npmjs.intuit.com/neo4j-driver

(this issue is also older, 4 days ago.)

DanielRuf · 2020-02-18T06:10:50Z

@chee he referred to the last sentence at #805 (comment)

DanielRuf · 2020-02-18T06:11:50Z

Generally this issue is not a bug in npm but a problem with the authentication with this intuit registry.

prozanne · 2020-03-17T07:17:38Z

I've got exactly same error message.
And I tried a lot of things but finally after I had removed specific folder in my project,
it could be published.
In my case, the folder might be banned for uploading...
And still I can't figure out the exact reason.

DanielRuf · 2020-03-17T08:07:43Z

In my case, the folder might be banned for uploading

What was the name of it?

prozanne · 2020-03-17T08:15:02Z

In my case, the folder might be banned for uploading

What was the name of it?

The folder contains tizen tv web application.
config.xml, index.html... etc
When I had removed tizen web application, I managed to publish.

DanielRuf · 2020-03-17T08:48:17Z

@prozanne I'm unsure if it is ok that you shared the code with us. This might be a different issue and requires some testing on your side (which file may be problematic?).

prozanne · 2020-03-17T23:16:29Z

@prozanne I'm unsure if it is ok that you shared the code with us. This might be a different issue and requires some testing on your side (which file may be problematic?).

Oh.... that's ture, I think I shouldn't have uploaded the code.
I'd better to remove it.
Anyway....
Having dug a lot, finally we've got a clue.
If bootstrap.css, socket.io libraries, tizen package file(.wgt) and image resource file(.png) are contained, I couldn't publish at all.
But when we removed all of them, it worked.

DanielRuf · 2020-03-17T23:52:53Z

You might want to remove the first version of your comment too.

avimehenwal · 2020-07-29T00:12:40Z

I have the same issue, how can I debug it? I am collecting and packaging only .vue files, no images. Any help is appretiated

AmitMirgal · 2020-10-13T15:30:08Z

what's the package name in package.json? @avimehenwal

gempain · 2020-10-14T09:38:02Z

Had the same issue. I was trying to publish to a scope which was not in my organization. I had a typo in the scope of my package name in my package.json.

haaarshsingh · 2020-10-23T02:10:45Z

I was having this bug too, this (probably) won't work for everyone but my problem was just that I was using an already existing pacakge.

Probably not what'll fix your problem, but it fixed mines.

jsdev-mario · 2020-11-02T19:41:12Z

same issue

jlorenzoC · 2020-12-09T01:13:14Z

Hi. The same over here when i try to: npm i @angular/material-moment-adapter

npm ERR! code E403
npm ERR! 403 403 Forbidden - GET http://my.nexus.ip/repository/npm-proxy/@angular%2fmaterial-moment-adapter
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.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\***\***\AppData\Roaming\npm-cache\_logs\2020-12-09T00_53_23_966Z-debug.log

TechQuery · 2020-12-15T20:44:04Z

Even npm whoami & npm login throw the same 403 error...

aminya · 2020-12-16T18:20:28Z

For me, I was trying to publish a package under my personal name, while I was logged in as the organization I own. It was fixed by relogging by npm login.

saltukalakus · 2020-12-31T22:06:16Z

I had the same error when publishing a package. It turned out that my email wasn't verified in my NPM account. Verifying it helped to resolve the issue.

JoseAtencio · 2021-01-08T21:17:04Z

@saltukalakus thanks it worked for me

azhaubassar · 2021-01-14T03:38:55Z

@saltukalakus thank you, you saved my hours

fayismahmood · 2021-01-22T03:16:44Z

I had the same error when publishing a package. It turned out that my email wasn't verified in my NPM account. Verifying it helped to resolve the issue.

yah it worked for me too

lzj723 · 2021-02-24T07:56:40Z

i've got the same error when i run "npm install" with company's private npm registry, even when npm login.

khurramlashari · 2021-02-28T14:40:22Z

i've got the same error and in my case package name was duplicate

Sataa-Yu · 2021-03-24T20:10:16Z

I've also got the same error when I run "npm install" after npm login with 2 factor auth.

Dharmendra205111014 · 2021-04-01T11:26:11Z

@prozanne I'm unsure if it is ok that you shared the code with us. This might be a different issue and requires some testing on your side (which file may be problematic?).

Oh.... that's ture, I think I shouldn't have uploaded the code.
I'd better to remove it.
Anyway....
Having dug a lot, finally we've got a clue.
If bootstrap.css, socket.io libraries, tizen package file(.wgt) and image resource file(.png) are contained, I couldn't publish at all.
But when we removed all of them, it worked.

Very similer thing happening to me, if i remove my README.md file it works fine. @prozanne could you find anything there ?

himharsh1997 · 2021-04-22T13:34:55Z

Hi guys! 2 things to do:

Verify your account first.
create file .npmrc file and set //registry.npmjs.org/:_authToken=<access_token> in it. You will get access_token from your account with publishing access.

moamlrh · 2021-05-16T17:44:11Z

I solved by :

go to npmjs.org
create a new access_token by :
- Click on your image in the right corner
- Access tokens
- Generate new token
- Select type : Publish
After that copy the token
got to your project
Create .npmrc file
Set //registry.npmjs.org/:_authToken=<access_token> in it

darcyclarke · 2021-06-02T21:55:13Z

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

ghost · 2021-12-06T07:32:12Z

Hi guys! 2 things to do:

Verify your account first.

create file .npmrc file and set //registry.npmjs.org/:_authToken=<access_token> in it. You will get access_token from your account with publishing access.

verifying email is not enough..2. step solves the problem

Previously, npm publish failed but according to a few sources: 1. https://gitlab.com/gitlab-org/gitlab/-/issues/242072 2. https://github.521000.bestmunity/t/unable-to-publish-package-403-repository-cant-accept-package-uploads/174606/5 3. npm/cli#805 (comment) This can be resolved by verifiying email with NPM. Done so will try to publish to the original package name

real-jiakai · 2022-09-28T05:06:28Z

In my case. Before I ran the command npm login, I didn't change the registry to npm. If you are using nrm . You should change the registry to npm first. nrm ls + nrm use npm solves my problem.

AndreaPontrandolfo · 2022-10-01T21:05:06Z

I was having this bug too, this (probably) won't work for everyone but my problem was just that I was using an already existing pacakge.

Probably not what'll fix your problem, but it fixed mines.

THANK YOU. I was going crazy, couldn't figure out why npm was telling me that i was publishing a package not owned by me. Read your comment, and yeah, turn out another package with the same name got published 10 years ago, lol. Had to change the name but finally got my package published! 🎉

juliaivi · 2023-05-20T07:40:58Z

В моем случае была проблема из-за файла .npmrc . Может кому-то поможет

hsmusz mentioned this issue Feb 17, 2020

[BUG] 429 Too Many Requests #836

Closed

prozanne mentioned this issue Mar 17, 2020

[QUESTION] npm publish, 403 forbidden error #1026

Closed

darcyclarke added the Awaiting Information further information is requested label Oct 30, 2020

darcyclarke closed this as completed Jun 2, 2021

gochicus mentioned this issue Jun 18, 2021

[feature] create public package atls-academy/gochicus.github.io#81

Closed

Simkiw mentioned this issue Aug 17, 2022

code E403 forbidden - angular cli #5312

Closed

2 tasks

JavierCane mentioned this issue Apr 4, 2023

Error trying to publish to npm CodelyTV/vue-skeleton#4

Open

snyk-io bot mentioned this issue Oct 23, 2024

[Snyk] Fix for 36 vulnerabilities Graysonbarton/cli-3#153

Open

[QUESTION] <403 forbidden> #805

[QUESTION] <403 forbidden> #805

Comments

anchal0997 commented Feb 13, 2020

imposeren commented Feb 17, 2020 • edited Loading

hsmusz commented Feb 17, 2020

chee commented Feb 17, 2020 • edited Loading

anton-bot commented Feb 17, 2020

chee commented Feb 17, 2020 • edited Loading

DanielRuf commented Feb 18, 2020

DanielRuf commented Feb 18, 2020

prozanne commented Mar 17, 2020

DanielRuf commented Mar 17, 2020

prozanne commented Mar 17, 2020 • edited Loading

DanielRuf commented Mar 17, 2020

prozanne commented Mar 17, 2020 • edited Loading

DanielRuf commented Mar 17, 2020

avimehenwal commented Jul 29, 2020

AmitMirgal commented Oct 13, 2020

gempain commented Oct 14, 2020

haaarshsingh commented Oct 23, 2020

jsdev-mario commented Nov 2, 2020

jlorenzoC commented Dec 9, 2020

TechQuery commented Dec 15, 2020

aminya commented Dec 16, 2020

saltukalakus commented Dec 31, 2020

JoseAtencio commented Jan 8, 2021

azhaubassar commented Jan 14, 2021

fayismahmood commented Jan 22, 2021

lzj723 commented Feb 24, 2021

khurramlashari commented Feb 28, 2021

Sataa-Yu commented Mar 24, 2021

Dharmendra205111014 commented Apr 1, 2021

himharsh1997 commented Apr 22, 2021

moamlrh commented May 16, 2021

darcyclarke commented Jun 2, 2021

ghost commented Dec 6, 2021

real-jiakai commented Sep 28, 2022

AndreaPontrandolfo commented Oct 1, 2022 • edited Loading

juliaivi commented May 20, 2023

imposeren commented Feb 17, 2020 •

edited

Loading

chee commented Feb 17, 2020 •

edited

Loading

chee commented Feb 17, 2020 •

edited

Loading

prozanne commented Mar 17, 2020 •

edited

Loading

prozanne commented Mar 17, 2020 •

edited

Loading

AndreaPontrandolfo commented Oct 1, 2022 •

edited

Loading