v10.0.4-alpha — Service Exposure panel + self-healing server address
Network-posture release: see exactly what your server exposes, and let cloud servers heal their own address when it changes.
Service Exposure panel (new, on the Firewall page)
A read-only, at-a-glance board comparing what each part of your stack should expose against what it's actually doing right now — colour-coded green / yellow / red:
- Internet-facing by design (TAK Server, the console, video streaming) shows green.
- Admin-only services that belong behind the reverse proxy are flagged red the moment they become reachable from the internet — the exact class of silent misconfiguration that has caused real security incidents elsewhere.
- It is purely informational — it never changes a firewall rule.
- It understands both Ubuntu's UFW and Rocky/RHEL's firewalld, and correctly treats firewall-blocked ports and TAK Server's own connector ports as safe.
- A small Exposure badge on the Console dashboard gives you the one-glance verdict, with a click-through to the detail.
Self-healing server address
A cloud server that is stopped and restarted is often handed a brand-new public IP (common on AWS without a static address). That used to leave the console pointing at a dead address — a browser certificate-name mismatch and firewall rules aimed at the old IP.
The console now re-detects its real address on startup and, only when it has genuinely changed, automatically:
- repairs its saved settings,
- regenerates the self-signed console certificate so the address matches, and
- re-scopes its firewall rules to the new address.
So the box comes back reachable instead of broken. (A static/Elastic IP is still the recommended setup; this is the safety net for servers that don't have one.)
Compatibility
Works identically on Ubuntu 22.04, Rocky / RHEL 9, and ARM64.
Upgrade
Applied automatically on the next console update — no action required.