a month ago
I have known working github packages token getting 403, was working yesterday, tried with fresh token.
Confirmed working with curl -H "Authorization: Bearer ghp_xxxxx" \
"https://npm.pkg.github.com/@redacted" locally, but when installing I get this error:
ERRPNPMFETCH_403 GET https://npm.pkg.github.com/download/@redacted: Forbidden - 403
An authorization header was used: Bearer ghp_[hidden]
These authorization settings were found:
@jsr:registry=https://npm.jsr.io/
@redacted:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:authToken=ghp[hidden]
Is there some work around for this?
29 Replies
this guy should get banned from station threads, he's trying to cherry pick github issues to farm bounties.
he responded within only 2 minutes of the thread being auto toggled to public.
a month ago
Link?
I do seriously need to figure out a work around for this issue though <:pepe_sweat:786868788560920576>
a month ago
Just to confirm it, it works locally but stopped working on Railway since yesterday?
Correct.
The direct curl from local with the same Bearer railway is using works, but the installation fails here in railway all of a sudden.
I even tried temporarily subbing in a token with higher access scope, no dice.
Haven’t had any issues until now, no major changes to the package / org permissions upstream.
Hmm maybe I can try changing the region of the service for now? Giving it a shot.
a month ago
Can you create a new private repository and deploy it with this Dockerfile being the only thing in the said repo?
FROM alpine:latest
RUN apk add --no-cache curl
RUN curl -fsS -o /dev/null -L \
-H "Authorization: Bearer ..." \
-w "HTTP Status: %{http_code}\n" \
https://example.com
CMD ["echo", "done"]Insert additional headers and authorization headers as needed, also replace the URL with the actual one as opposed to example.com.
a month ago
This should log the http status in your build logs.

well no, it looks like it is working properly:
```
An authorization header was used: Bearer ghp[hidden]
These authorization settings were found:
@jsr:registry=https://npm.jsr.io/
@opengameprotocol:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:authToken=ghp[hidden]
this is the shape of my .npmrc:
@opengameprotocol:registry=https://npm.pkg.github.com //npm.pkg.github.com/:_authToken=${GITHUB_PACKAGES_TOKEN} always-auth=true
a month ago
Hmm, I wonder if the metal build environment has anything to do with this, can you check if the affected service has it enabled/disabled (it can be found in the service's settings)?
ah sorry i edited it to make sure you didn't think it actually logged redacted and it mogged the code block lol
ah, okay sorry for wasting your guys time…
I think I found the issue, the metadata endpoint works but the download is blocked by billing on our end <:cryfistsq:1238327748464873472>
a month ago
No worries, glad you figured it out <:salute:1137099685417451530>
Status changed to Solved uxuz • about 1 month ago



