diff --git a/graph/edges/fix-gitea-ssh-remote-gitgitman--RELATED_TO--gitea-actions-runner-offline-m-4cb305.md b/graph/edges/fix-gitea-ssh-remote-gitgitman--RELATED_TO--gitea-actions-runner-offline-m-4cb305.md
new file mode 100644
index 00000000000..122d0d0fe36
--- /dev/null
+++ b/graph/edges/fix-gitea-ssh-remote-gitgitman--RELATED_TO--gitea-actions-runner-offline-m-4cb305.md
@@ -0,0 +1,13 @@
+---
+id: 4cb3054a-c8d4-4eb5-bc5e-bdae9732b7cc
+type: RELATED_TO
+from_id: 4479674f-16de-4cfb-afc1-73042d4ab8db
+from_title: "Fix: Gitea SSH remote (git@git.manticorum.com) resolves to Pi-hole instead of Gitea LXC"
+to_id: f4683542-eb76-4397-9e84-673c86a05904
+to_title: "Gitea Actions runner offline - must use internal URL not public domain"
+strength: 0.75
+created: "2026-02-27T05:48:31.928716+00:00"
+updated: "2026-02-27T05:48:31.928716+00:00"
+---
+
+Both involve Gitea connectivity issues on the homelab — internal URL vs public domain routing
diff --git a/graph/fixes/fix-gitea-ssh-remote-gitgitmanticorumcom-resolves-to-pi-hole-447967.md b/graph/fixes/fix-gitea-ssh-remote-gitgitmanticorumcom-resolves-to-pi-hole-447967.md
index df3ae926c4e..85169e6b149 100644
--- a/graph/fixes/fix-gitea-ssh-remote-gitgitmanticorumcom-resolves-to-pi-hole-447967.md
+++ b/graph/fixes/fix-gitea-ssh-remote-gitgitmanticorumcom-resolves-to-pi-hole-447967.md
@@ -6,13 +6,18 @@ tags: [gitea, ssh, dns, networking, fix, pihole, homelab, dotfiles]
 importance: 0.65
 confidence: 0.8
 created: "2026-02-27T05:48:03.833429+00:00"
-updated: "2026-02-27T05:48:21.730677+00:00"
+updated: "2026-02-27T05:48:31.928716+00:00"
 relations:
   - target: 5f31ea7f-9b53-427d-b601-ab98dabaa2e3
     type: RELATED_TO
     direction: incoming
     strength: 0.9
     edge_id: b1d439b6-456f-4271-bd16-0d612564e7f4
+  - target: f4683542-eb76-4397-9e84-673c86a05904
+    type: RELATED_TO
+    direction: outgoing
+    strength: 0.75
+    edge_id: 4cb3054a-c8d4-4eb5-bc5e-bdae9732b7cc
 ---
 
 # Gitea SSH Remote Resolves to Pi-hole
diff --git a/graph/solutions/gitea-actions-runner-offline-must-use-internal-url-not-publi-f46835.md b/graph/solutions/gitea-actions-runner-offline-must-use-internal-url-not-publi-f46835.md
index fd1b5269f79..9da96a445f2 100644
--- a/graph/solutions/gitea-actions-runner-offline-must-use-internal-url-not-publi-f46835.md
+++ b/graph/solutions/gitea-actions-runner-offline-must-use-internal-url-not-publi-f46835.md
@@ -6,7 +6,7 @@ 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-18T19:57:25.899469+00:00"
+updated: "2026-02-27T05:48:31.928716+00:00"
 relations:
   - target: 53328fc9-796a-47b7-81ae-fc57c9b3a202
     type: BUILDS_ON
@@ -18,6 +18,11 @@ relations:
     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"
+  - target: 4479674f-16de-4cfb-afc1-73042d4ab8db
+    type: RELATED_TO
+    direction: incoming
+    strength: 0.75
+    edge_id: 4cb3054a-c8d4-4eb5-bc5e-bdae9732b7cc
 ---
 
 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.