v10.1.3-alpha — CloudTAK updates that actually finish, a database that repairs itself, and a version pin you can trust

CloudTAK updating is fixed end to end, and CloudTAK is now pinned to a tested release. Updating is recommended; healthy boxes are left untouched.

What was wrong

Three separate things could go wrong when you updated CloudTAK — all three are closed in this release.

Updates timed out. A large CloudTAK rebuild on a slower VPS connection could get killed partway through, leaving the update unfinished.

CloudTAK could come back dead with a database error. PostgreSQL only accepts its password the first time a database is created and ignores it from then on. If a box's configuration had drifted from its actual database, CloudTAK would fail with "password authentication failed" the moment an update restarted it — even though nothing was visibly wrong beforehand.

Updates could jump to an untested version. CloudTAK installs simply took whatever was newest upstream, including on brand-new deployments — so a release that had not been checked against browser plugins could land on your box by surprise.

What is fixed

Updates complete. The rebuild now streams its progress and is given the time it actually needs.

The database repairs itself. After every start, the console checks the stored password against the live database and fixes a mismatch automatically. Affected boxes heal on their next update — no manual steps, no data loss.

A version pin you can trust. CloudTAK now follows the same tested-version track as the identity provider and NetBird: the main channel installs only the release that has been validated, including on fresh installs. Every module card reads the same way — your version · what main is pinned to · update (only when there is actually one to install).

Also in this release

• A box that changed public IP could fail to start. Common after a cloud stop/start: the box could write bad data into its own settings and then refuse to bring the console up at all. That is now prevented and self-healing.
• CloudTAK now validates the console's certificate instead of skipping verification, so its connections are properly checked.
• TAK Portal map fix so the map is not empty for admins.
• Security hardening, including tightened validation on monitoring inputs and a pinned, verified bootstrap for the connectivity anchor.

Upgrade

Applied automatically on the next console update. Healthy boxes are left untouched; affected boxes repair themselves on restart.