Tor 0.4.7.8 in app sidecar containers cannot fetch directory authority certs — all hidden services broken, zero inbound connectivity

## Summary All Umbrel apps that run a `tor_server-1` sidecar (Lightning, Alby Hub, RTL, LN+, ThunderHub) are failing to fetch three directory authority signing key certificates with HTTP 404. This has been occurring for 7+ consecutive days and affects every Tor process on the node simultaneously. **Device:** Umbrel Home (2025) **umbrelOS version:** 1.7.3 (latest as of May 20, 2026) **Tor version in all sidecar containers:** 0.4.7.8 ## Evidence The following errors repeat every ~90 minutes across every container log: - Received http status code 404 ("Not found") from server 188.62.6.214:7987 while fetching "/tor/keys/fp/D586D18309DED4CD6D57C18FDB97EFA96D330566" - Received http status code 404 ("Not found") from server 109.71.252.50:9001 while fetching "/tor/keys/fp/14C131DFC5C6F93646BE72FA1401C02A8DF2E8B4" - Received http status code 404 ("Not found") from server 188.62.6.214:7987 while fetching "/tor/keys/fp/EFCBE720AB3A82B99F9E953CD5BF50F7EEFC7B97" Every Tor heartbeat across all containers shows: - I've received 0 connections on IPv4 and 0 on IPv6. - Our onion service received 0 v3 INTRODUCE2 cells and attempted to launch 0 rendezvous circuits. This has been consistent without exception for 7+ days. ## Downstream effects - Hidden service descriptor upload circuits time out on every attempt - Node .onion addresses are never published to the Tor hidden service directory - No inbound Lightning connections possible - Circular rebalances fail with No Route ## Root cause These three authority signing keys have rotated since Tor 0.4.7.8 was released. The pinned image has no knowledge of the updated certificates. Bootstrapping and outbound connections still work normally — only 4-hop hidden service circuits are affected, consistent with a cert validation failure specific to HS directory operations. ## Confirmed Image Reference Verified via `cat` of the live compose file at `/home/umbrel/umbrel/app-data/lightning/docker-compose.yml`: tor: image: >- getumbrel/tor:0.4.7.8@sha256:2ace83f22501f58857fa9b403009f595137fa2e7986c4fda79d82a8119072b6a **- The image is pinned by SHA256 digest, not just by version tag. This means the broken version is locked in place and will not self-heal — the compose file itself must be updated to a new image reference.** ## Suggested Fix Update `getumbrel/tor:0.4.7.8` to current stable in all affected app compose files.