docs: record Serenity cloudflared audit
Some checks failed
secret-guardrails / gitleaks (push) Has been cancelled
secret-guardrails / artifact-secret-scan (push) Has been cancelled

This commit is contained in:
Fizzlepoof
2026-05-25 22:00:23 +00:00
parent eba18beabe
commit 60de92339d
3 changed files with 33 additions and 8 deletions

View File

@@ -69,7 +69,8 @@ Per-service gotchas that aren't bugs but will bite you if you forget them.
### Unraid-Cloudflared-Tunnel
- Older notes called this dead, but live inspection on 2026-05-25 showed active Cloudflare QUIC edge registrations and a configured tunnel token.
- Treat it as a live service pending usage audit, not a safe blind-removal candidate.
- Follow-up audit showed it is only transport-alive: current-run metrics reported zero proxied requests, its remote-managed ingress config still points at legacy `192.168.1.x` origins, and the listed public hostnames appear to be served elsewhere now.
- Treat it as removable stale Cloudflare deadwood after a brief stop/remove observation window; preserve appdata during the cooling-off period and clean up Cloudflare-side tunnel config separately.
### Serenity Wave 1 cleanup guardrails
- Do not assume `Unraid-Cloudflared-Tunnel` is dead just because it looked obsolete in older notes; live inspection on 2026-05-25 showed active Cloudflare tunnel registrations, so audit usage before removal.