github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Suddenly need authToken to access packages in Gitea registry #14564

New Issue
Open
opened 2025-11-02 11:16:24 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 11:16:24 -06:00
Owner
Copy Link

Originally created by @digitalextremist on GitHub (Jun 7, 2025).

Description

This seems like #14498 and #13484 returned... but intermittently.

When using docker to build a new image, with all the appropriate settings to access an extra host, Gitea returns 401 intermittently.

Then when I go to the URL which fails in my browser, I also see a login screen versus the package JSON.

I had to add my authToken to the .npmrc file in the project root, which Gitea does not itself require in the Package instructions.

And normally it does not need an authToken to pull packages, only to publish packages.

Gitea Version

1.23.8

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I am using a local instance running in Docker

Database

MySQL/MariaDB

Originally created by @digitalextremist on GitHub (Jun 7, 2025). ### Description This seems like #14498 and #13484 returned... but intermittently. When using `docker` to build a new image, with all the appropriate settings to access an extra host, `Gitea` returns `401` intermittently. Then when I go to the URL which fails in my browser, I also see a login screen versus the package JSON. I had to add my `authToken` to the `.npmrc` file in the project root, which `Gitea` does not itself require in the `Package` instructions. And normally it does not need an `authToken` to pull packages, only to publish packages. ### Gitea Version 1.23.8 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? I am using a local instance running in `Docker` ### Database MySQL/MariaDB
GiteaMirror added the topic/packagestype/bug labels 2025-11-02 11:16:24 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/packages type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14564
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?