Github package registry - Private package not found

waqasibrahim · December 1, 2019, 8:10pm

I have a private repository and I was able to publish a private package successfully. But when I try to install the package, It gives a 404 error. I cannot download the package from the package landing page and the assets links to https://notfound.pkg.github.com/.

I changed the visibility to public and the installation and assets’ link worked fine.

typicaljon · December 1, 2019, 10:52pm

I’m having this exact same problem.

mxxk · December 2, 2019, 2:32am

Thanks for creating a dedicated issue for this, @waqasibrahim (the previous issue wasn’t getting any attention since it’s marked fixed for an unrelated reason).

Here are the steps to reproduce:

Create a new private repository. Per npm package naming requirements, make sure the repo owner and name (i.e. @repo-owner/repo-name) are both lowercase.
Create a personal access token with the following scopes:

write:packages
read:packages
repo

Authenticate against the GitHub NPM registry using your GitHub username and personal access token:

$ npm login --scope @repo-owner --registry https://npm.pkg.github.com
Use npm init to create a new npm package called @repo-owner/repo-name.
Publish a new (and only) version of the NPM package with npm publish.
Check that the package is visible with npm view:

$ npm view @repo-owner/repo-name
@repo-owner/repo-name@0.0.1 | ISC | deps: 0 | versions: 1
…

Now, try to install the package:

$ npm install -g @repo-owner/repo-name
npm ERR! code E404
npm ERR! 404 Not Found - GET https://npm.pkg.github.com/download/@repo-owner/repo-name/0.0.1/8d84896fe3f54d8ce56962cf1f7fc760e56efe52f2d471cf703103c476d3c9a9

Check that though the GitHub UI is showing the new version, its tarball links to https://notfound.pkg.github.com/:

wpitallo · December 2, 2019, 6:24pm

I am also getting this.

freshly-pressed-trousers · December 4, 2019, 4:55pm

Same isssue here, which is a shame as when github packages was released it looked like a perfect solution for consolidating a lot of disparate repository guff I’ve had to deal with.

scottwestover · December 4, 2019, 6:27pm

I am having the same issue.

alappin · December 6, 2019, 1:18am

I can confirm that the problem has been fixed and might have been related to some “data transfer” billing issues at github. Support eventually cameback to me after 2 weeks and gave me the following response.

Hey there *NAME RETRACTED*,

Thanks for your patience here, we believe there may have been some issues with rounding the data.

Can I ask you to:

Check, and view your usage over at: https://help.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/viewing-your-github-packages-usage
Try making this installation request again.

Usage should be more accurately reflected, and you should be able to start using the package registry once more.

Thanks
*NAME RETRACTED*

anthonator · December 18, 2019, 10:52pm

Is a personal access token still required?

anthonator · December 18, 2019, 10:56pm

Yes, it is. secrets.GITHUB_TOKEN does not work.

anthonator · January 9, 2020, 4:29pm

We’ve also been getting charged for data transfer out when using personal access tokens to get a docker image hosted on the GitHub Package Registry from GitHub Actions. This is supposed to be free.

cyrus-za · April 3, 2020, 6:24am

I am still experiencing this issue, but only when installing with yarn. Not when installing with npm. So strange!

joaogarin · February 4, 2022, 3:24pm

Hello all,

I started also receiving today errors for installing packages (private) via circle ci…any ideas if there is anything wrong happenig? I feel like if it was a token problem I would not be getting a 404 but rather a permission denied…locally I can install the packages no problem…

Anyone else experiencing some issues recently on this?