¶ September 3, 2026 - Automatic timezone detection, storage safety, and setup recovery
Here is a summary of changes shipped since our last update.
- Translators have a new way to find strings. Turn on the key inspector and every piece of translated text on screen is outlined: hovering names the string behind it, and clicking opens it in Weblate in your language. No more guessing which of the many strings sharing a short label is the one you saw. See using the key inspector to get started.
- We need your help! Want to translate HexOS into your language? Learn how to contribute and join the conversation on Discord
- Languages ship to production once they reach 60% approved coverage
- HexOS now detects your server's timezone automatically from its IP address and sets it during setup. Previously, new servers defaulted to Pacific time regardless of location, which meant snapshot schedules, scrubs, and notifications ran at unexpected hours. A timezone picker is also available on the server settings screen if you need to adjust it manually.
- In some cases, drives belonging to a pool that had been exported but never imported were treated as unused. HexOS now recognizes these drives and will not offer or format them when you create a pool, replace a drive, expand a pool, or assign a hot spare, so an exported pool can no longer be overwritten by accident.
- Cache, log, special, dedup, and hot spare drives from a pool that is already in use no longer appear as loose drives during setup.
- The app updates screen now shows every app with an update as a grid of app icons. Click an app to see its installed and available versions and update it on its own, or use Update all to apply everything at once.
¶ Setup and claiming
- In some cases, a power cut or full storage pool could send a provisioned server back into the setup wizard. Command Deck now recognizes that the server is already set up and offers a one-click recovery path instead of walking through setup again. Servers with full pools also receive a clear explanation rather than a generic network error.
- Claiming a server that was reinstalled no longer creates a duplicate entry. Command Deck detects that the server matches an existing claim by name and replaces the old record, so reinstalled servers no longer consume an extra license slot.
- Command Deck now maintains separate connection paths for its own traffic and TrueNAS traffic. If one path reconnects on a different backend node, the other continues uninterrupted. Previously, a backend restart could briefly interrupt both connections at once.
- Self-updates now fall back to a host-side restart if the standard middleware update path is unavailable, so updates complete even when the app container is in an unexpected state.
- When a TrueNAS login fails repeatedly (for example, after a password change or key rotation), Command Deck now backs off automatically instead of retrying in a tight loop. This prevents the server from becoming unresponsive to other requests during the recovery window.
- Real-time reporting (CPU, memory, network graphs) now recovers silently if the underlying data subscription drops, instead of requiring a page refresh to restore live updates.
- If a server's local database storage disappears (for example, after a pool is removed), the local interface now detects and reports the condition instead of retrying indefinitely in the background.
- Notification toasts now remain hoverable and dismissible even while a dialog or side panel is open.
NOTE: All of these updates are applied automatically to your Command Deck. You may need to clear your cache. Help with clearing your cache is available here.