Skip to content

v0.9.47-alpha — Custom TAK Portal domain · Network & Fanout metrics · WebODM resource cap

Choose a tag to compare

View all tags
@takwerx takwerx released this 07 Jun 23:55
v0.9.47-alpha
7d2ad5d

Three areas in this release.

Custom TAK Portal domain (GH #41)

If you set a custom TAK Portal domain in the Caddy module (e.g. portal.<fqdn> instead of the default takportal.<fqdn>), the console's TAK Portal buttons, the Self-Service Enrollment URL, and Authentik's proxy external_host now all resolve that configured domain. Previously the startup canonicalizer silently reverted Authentik's external_host back to the default prefix on every console restart, breaking forward auth on the custom host. IP-only / no-FQDN deployments are unchanged.

Network & Fanout metrics (Guard Dog)

A new Network & Fanout panel makes TAK Server CoT-fanout load visible in the browser:

  • External NIC throughput (TX/RX)
  • Kernel :8089 send-queue depth — the leading indicator of fanout backpressure, with stalled/idle sockets separated from live queue
  • Connected-client count and JVM heap
  • 1h / 24h views, 60s refresh, and an inline "how to read it" guide under each chart

It installs and self-heals automatically on console restart wherever Guard Dog is present.

WebODM hardening (GH #31, #32)

  • ODM resource cap (#32). A co-located WebODM/ODM processing job is now hard-capped — CPU, memory, and processing-thread concurrency — so it can't starve or OOM the rest of the TAK stack. The cap applies on deploy and self-heals onto existing WebODM installs on the next console restart, with no redeploy needed.
  • Remote-deploy UI fix (#31). The WebODM remote Deployment Target buttons (Test connection, Save, Generate/Install SSH key) now correctly report success instead of showing a false red error.

Upgrade: Update Now in the console, or pull main and restart. Existing WebODM installs pick up the ODM cap automatically on the restart.

Assets 2
Loading