Skip to content

v10.0.3-alpha — Config-resilience & self-healing startup

Choose a tag to compare

View all tags
@takwerx takwerx released this 24 Jun 04:32
v10.0.3-alpha
7e22b01

A rare race condition could corrupt the console's settings file and make a healthy server suddenly behave as if it had no domain — a "No Domain Configured" banner, a drop to self-signed certificates, and (if the domain was then re-entered) broken single sign-on. v10.0.3 makes that class of failure impossible and hardens the surrounding paths.

What's fixed

  • Config is now unloseable. The console's settings file is written atomically (never caught half-written, even under heavy background activity or a restart), it never drops the server's core identity (domain, SSL mode, OS, install paths), and it self-heals any missing setting on startup — re-detecting the OS and recovering the domain from the server's own configuration. A box always comes back up on its real domain instead of a degraded state.
  • SSO domain changes are reliable. Changing a server's domain no longer produces a malformed sign-on hostname (which could surface as an "Authentik — Not found" error), and single sign-on redirects always point at a browser-reachable address.
  • The console always starts. It now finishes startup even if Authentik's LDAP component is briefly unhealthy — healing in the background instead of hanging.
  • No more identity-provider restart loops. On slower disks, the identity provider can no longer get stuck in a database-lock crash loop on restart.
  • Native ARM installs detected correctly. TAK Server installed natively on ARM (before container support existed) is now shown as running instead of "Stopped."

Works identically on Ubuntu 22.04, Rocky / RHEL 9, and ARM64.

Upgrade: applied automatically on the next console update — no action required. The protection is most valuable on long-running servers.

Assets 2
Loading