Skip to content

Edge cases & misc — FAQ

Catch-all weird problems that don't fit other categories. Search Ctrl+K first.

MSC-001 — Something broke — where start?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Search FAQ (Ctrl+K), check status.saxobroko.com, Common issues. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-002 — Everything down at once?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Power → router → NAS → cloudflared — turn everything on. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-003 — Internet up but all saxobroko subdomains fail?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Cloudflare or tunnel issue — cloudflared FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-004 — Only one app down?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Restart that Docker app on TrueNAS. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-005 — Works in AU not overseas?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. block no aus WAF — VPN to Australia or use public sites only. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-006 — Works on LTE not home Wi‑Fi?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. LAN DNS or Pi-hole issue — DNS FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-007 — Time wrong on devices?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Fix NTP — breaks SSL logins everywhere. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-008 — Pool degraded?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. STOP heavy writes — pool FAQs, when pool degraded. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-009 — Disk full?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check disk space. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-010 — SMART errors?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Read SMART errors. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-011 — Scrub running slow?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Normal — don't panic-stop unless errors. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-012 — Jellyfin black screen?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Jellyfin playback FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-013 — Movie requested not appearing?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Overseerr FAQs + arr pipeline. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive:* Common Issues
MSC-014 — qBittorrent stuck?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. qBittorrent FAQs — don't delete random files. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-015 — Music won't play?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Navidrome FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-016 — Photos app slow?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Photos FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-017 — Plex still used?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Legacy — Plex FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-018 — UniFi Wi‑Fi weird?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. UniFi FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-019 — Dream Machine SE reboot?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. One reboot OK — not factory reset. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-020 — CGNAT mentioned in old notes?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Tunnel replaces port forwarding — ignore port-forward guides. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-021 — DNS propagation wait?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Up to 48h for external DNS changes — DNS FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-022 — Certificate mismatch on random subdomain?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check tunnel hostname vs cert — Cloudflare edge FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-023 — Bot fight blocked login?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. WAF skip for auth/docs — Ryan. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-024 — GitHub Actions billing?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Check repo settings — usually free for public SaxDocs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-025 — Cloudflare Access bypass for emergency?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Disable Access temporarily — Ryan only. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-026 — TrueNAS update pending?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Read release notes — don't update during pool degraded. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-027 — Docker app update broke service?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Rollback app version in TrueNAS Apps. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-028 — Windows share A: slow?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Wi‑Fi vs ethernet — windows shares. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-029 — Storj node on PC?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. See Storj doc — separate from NAS media. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-030 — Aither ratio panic?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Read tracker rules — don't cheat; Ryan handles account. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-031 — Tracker credentials?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Vault only — Aither doc. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-032 — Random port scan worry?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Cloudflare tunnel reduces exposure — don't open router ports. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-033 — UPS battery dead?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Graceful NAS shutdown risk — replace UPS battery. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-034 — Lightning storm?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Unplug sensitive gear if safe — power FAQs. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-035 — Smoke from NAS?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Power off, fire safe, do not open pool — call emergency. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-036 — Water leak near server?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Power off NAS first — hardware loss vs electrocution. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-037 — Kid clicked something on PC?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Close tab — don't install random software. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-038 — Email hacked suspicion?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Change password via vault order — Cloudflare, banks. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-039 — Ransomware message?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Isolate PC from network — professional help — don't pay blindly. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-040 — Two FAQ answers conflict?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Prefer newer git date on page — or ask Ryan. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-041 — Guide vs FAQ?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Guides = step-by-step beginners; FAQ = symptom fix list. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-042 — todo.md in repo?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Saxon's scratch list — may be outdated. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-043 — Certifications expired?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Certifications — McDonald's training renewals. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-044 — Weather station offline?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Weather station — separate from SaxWeather site. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-045 — Trusted brands doc?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Shopping preferences — trusted brands. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-046 — LinkedIn out of date?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Update career.md — LinkedIn is external. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-047 — IPv6 issues?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. May disable on client for testing if v4 works. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-048 — MTU black hole?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Rare streaming glitch — Ryan network tuning. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-049 — Nothing here matches?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Add FAQ entry via SaxDocs git — or Guides index. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues
MSC-050 — Still stuck?

Stack context: Cross-cutting · odd failures Integrated runbooks: Symptom finder · Outage runbook

Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.

  1. Ryan inherits tech per will — escalate after vault + YubiKey + status check. Verify: Repeat the original symptom check — it should be gone or clearly improved. Deep dive: Common Issues