fizzlepoof/truenas-stacks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record Serenity Pangolin drift workaround
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
Details
secret-guardrails / gitleaks (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Fizzlepoof
2026-05-25 20:33:09 +00:00
parent cd98fcf49a
commit 54bf27b208
3 changed files with 40 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/troubleshooting/KNOWN_QUIRKS.md
View File

@@ -70,6 +70,17 @@ Per-service gotchas that aren't bugs but will bite you if you forget them.
### Unraid-Cloudflared-Tunnel
- Dead container, should be removed
### Serenity Newt / Pangolin stale health-check IP drift
- Several Serenity Newt-backed Pangolin targets were corrected to `ip=localhost` but still retained stale `hcHostname=10.5.1.5`, so Newt health checks kept failing with `no route to host`
- Verified affected target IDs on 2026-05-25: `15`, `20`, `25`, `29`, `56`, `57`, `58`, `69`
- Fast live recovery on Serenity: add runtime compatibility alias `10.5.1.5/32` on `br0`
- command used: `ip addr add 10.5.1.5/32 dev br0`
- Verified results after alias:
- Newt logged recovery to healthy for targets `15`, `20`, `25`, `29`, `56`, `57`
- direct HTTP probes to `http://10.5.1.5:8785/` and `http://10.5.1.5:8457/` returned `200`
- `docker exec Newt` confirmed `wget` success to ports `8785` and `8457`
- This is a runtime workaround, not an authoritative fix. It will disappear on reboot unless deliberately persisted, and the real cleanup is still to rewrite Pangolin health-check hostnames away from the stale pre-renumbering IP.
---
## N.O.M.A.D.