Skip to content

v0.9.49-alpha — CloudTAK "Update Now" reaches the latest release cleanly

Choose a tag to compare

View all tags
@takwerx takwerx released this 09 Jun 02:36
v0.9.49-alpha
67f4ef2

CloudTAK updates from the console work again, and the version readout tells the truth.

What was wrong

Updating CloudTAK from the console (CloudTAK → Update Now) could fail at the final step with address already in use on port :9997. The update checks out the new CloudTAK release, which resets CloudTAK's container port bindings back to the public defaults — and that collided with the auth-gated video proxy introduced in v0.9.48. The result: the rebuild aborted and the box stayed on the old CloudTAK version. (It failed safe — the running CloudTAK kept serving — but the update couldn't complete.)

Separately, a fully-updated box could show a permanent "update available" badge on the CloudTAK card when CloudTAK's published version number lags its release tag.

What's fixed

  • Update Now completes again. The updater now re-applies CloudTAK's loopback port hardening immediately after checking out the new version, so the rebuild finishes and the box lands on the latest CloudTAK with no port collision. As a bonus, this re-closes a set of CloudTAK admin ports that every past update briefly re-exposed until the next restart.
  • No more phantom "update available." The console now recognizes when it is already on the latest CloudTAK release even if CloudTAK's internal version number trails the tag, and clears the badge — while still flagging a genuinely failed or pending update.

Upgrade

Applied automatically. After your console updates to v0.9.49-alpha, open CloudTAK → Update Now once to move CloudTAK itself to the latest release. No manual steps, no data loss.

Assets 2
Loading