relate: 499462d9 --BUILDS_ON--> f4683542
This commit is contained in:
parent
dbf1c699dc
commit
f8410884d4
@ -6,7 +6,13 @@ tags: [gitea, ci-cd, actions, act-runner, docker, authentication]
|
||||
importance: 0.9
|
||||
confidence: 0.8
|
||||
created: "2026-02-18T19:57:12.550575+00:00"
|
||||
updated: "2026-02-18T19:57:12.550575+00:00"
|
||||
updated: "2026-02-18T19:57:25.899334+00:00"
|
||||
relations:
|
||||
- target: f4683542-eb76-4397-9e84-673c86a05904
|
||||
type: BUILDS_ON
|
||||
direction: outgoing
|
||||
strength: 0.8
|
||||
context: "This auth fix extends the original runner setup - runner must use internal URL for registration, but action clones still go through ROOT_URL causing host mismatch"
|
||||
---
|
||||
|
||||
Problem: act_runner fails to clone composite actions from cal/gitea-actions with 'authentication required: Unauthorized'. Root cause: Runner registered at http://10.10.0.225:3000 (internal) but Gitea sends clone URLs using ROOT_URL (https://git.manticorum.com). go-git compares url.Host - hosts don't match so no auth token is passed. Combined with REQUIRE_SIGNIN_VIEW=true, unauthenticated clone fails.
|
||||
|
||||
@ -6,13 +6,18 @@ tags: [gitea, ci-cd, actions, runner, troubleshooting, docker, reverse-proxy, 40
|
||||
importance: 0.9
|
||||
confidence: 0.8
|
||||
created: "2026-02-05T19:24:11.871715+00:00"
|
||||
updated: "2026-02-18T18:00:00.224971+00:00"
|
||||
updated: "2026-02-18T19:57:25.899469+00:00"
|
||||
relations:
|
||||
- target: 53328fc9-796a-47b7-81ae-fc57c9b3a202
|
||||
type: BUILDS_ON
|
||||
direction: incoming
|
||||
strength: 0.8
|
||||
context: "Extends original runner troubleshooting with auth for composite actions"
|
||||
- target: 499462d9-3804-4651-9f46-ffabc2e4713f
|
||||
type: BUILDS_ON
|
||||
direction: incoming
|
||||
strength: 0.8
|
||||
context: "This auth fix extends the original runner setup - runner must use internal URL for registration, but action clones still go through ROOT_URL causing host mismatch"
|
||||
---
|
||||
|
||||
Problem: Gitea Actions runner showing as 'Offline' in admin UI, jobs stuck in 'Waiting' status with no steps executing. Runner container shows '403 Forbidden' errors when trying to fetch tasks.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user