Gitea Actions action download 404 (gitea.com) in CI
Gitea fetched the action from the configured source and got HTTP 404. The action name, owner, or tag does not exist at that source, so the download URL points at nothing.
What this error means
A run fails while downloading an action with a 404 for a URL under the configured actions host (such as https://gitea.com/...). The reference is wrong for that source.
Gitea Actions
failed to download action: unexpected status code 404 for
https://gitea.com/actions/setup-go/archive/v5.tar.gzCommon causes
The action is not mirrored at the configured source
DEFAULT_ACTIONS_URL points at gitea.com (or a mirror) that does not host that owner/action, so the archive URL 404s.
A wrong owner, name, or tag in uses
A typo or a nonexistent tag builds a download URL that no source can satisfy.
How to fix it
Correct the uses reference or its source
- Confirm the action owner/name and tag exist at the configured source.
- Either fix
uses:to a real reference, or switch DEFAULT_ACTIONS_URL to a source that hosts it. - Re-run and confirm the archive downloads.
.gitea/workflows/ci.yml
# reference a tag that exists at the configured source
- uses: actions/setup-go@v5Point uses at a full URL when mixing sources
Gitea supports absolute action URLs, so you can pull a specific action from a host that actually has it.
.gitea/workflows/ci.yml
- uses: https://github.com/actions/setup-go@v5How to prevent it
- Keep uses references consistent with the configured actions source.
- Mirror the exact tags your workflows reference.
- Prefer pinned tags that you have verified exist at the source.
Related guides
Gitea Actions "unable to resolve action" (uses) in CIFix Gitea Actions "unable to resolve action" in CI - the instance cannot fetch the action named in uses becau…
Gitea "Actions disabled" (enable Actions in repo/admin) in CIFix Gitea Actions doing nothing because Actions is disabled in CI - the feature must be enabled globally in a…
Gitea Actions "workflow is invalid" in CIFix Gitea Actions "workflow is not valid" in CI - the YAML parses but violates the workflow schema, so no job…