Leaderboard

The translation platform is live. Thanks to everyone who volunteered in this thread. Here are the instructions to get started. Where to go Head to translate.hexos.com and click Sign in. It uses your existing HexOS account, so there's nothing to register and nothing to be granted. If you can log in to HexOS, you can start translating right now. What you'll find We're running Weblate, the same open-source translation platform used by projects like Fedora and LibreOffice. Everything happens in your browser: no tools to install, no technical background needed. Just you, the English text, and a box to type your translation into. There are about 2,800 strings that make up the HexOS interface, and you can filter by area (storage, apps, tasks, and so on) if you'd rather focus on one corner at a time. Getting started Sign in at translate.hexos.com Open the Deck component and add your language (or join one that's already started) Start translating. Weblate saves as you go, and you can stop and pick it back up whenever you like. Same as Jon said: no deadlines, no commitments A few things worth knowing Placeholders like `{name}` or `{count}` need to stay exactly as they are. Move them around to fit your grammar, just don't translate what's inside the braces. Brand terms (HexOS, Command Deck, TrueNAS, ZFS) stay in English everywhere. They're marked in the built-in glossary so you don't have to memorize them. Not sure about a string? Leave a comment on it right in Weblate. We monitor those, and other translators can weigh in too. How your work reaches users Every translation goes through a review step before it ships, so don't worry about making mistakes. Nothing goes live until a reviewer approves it. We'll mark you all as reviewers once you start here soon, and once a language reaches 60% approved coverage, it ships with the next HexOS release and appears in the language picker. Below that threshold, the lang simply isn't offered yet, so nobody ever sees a half-translated interface. New strings will flow into Weblate automatically as we build new features, and the platform should email you when there's new material in your language. The full guide (with translation guidelines and how everything works under the hood) lives on the docs site: Translating HexOS. Let me know if you have any questions or something is off. Thank you!

That suggestion's Origin is coming from a similar string inside of Deck. I have just enabled Google Cloud Translate API that you ALL can access from the Automatic suggestions tab.

Hello, we have a bunch of fixes coming for this very shortly. It's tied up with buddy backups which is why we haven't pushed it yet. Just know it's coming out very soon!

To start, Docker is behaving correctly. But in HexOS, I'm seeing that the configured base 172.17.0.0/12 is technically invalid as a /12 network boundary, which is being normalized to 172.16.0.0/12. This results in automatic allocation of 172.16.x.0/24 networks. If the intention is to allocate only from 172.17.x.x, the base should be changed to 172.17.0.0/16. Practically speaking, when a user deploys apps, they typically appear to end up on new Docker bridge networks, which can quickly create IP conflicts for the few users out there using 172.16.x.x/16 networks. I noticed this after the TrueNAS login page was showing up unexpectedly for one of my unrelated endpoints. I'd suggest surfacing some configuration parameters somewhere in the UI, namely the Docker network pool config. As a more immediate fix: To reconfigure my HexOS deployment to use the 172.17.0.0/16 network ranges instead, I ran: root@HexOS[~]# midclt call docker.update '{ "address_pools": [ { "base": "172.17.0.0/16", "size": 24 }, { "base": "fdd0::/48", "size": 64 } ] }'

Following up on this — the fix is implemented and will ship in an upcoming release. You were exactly right about the root cause: the stock 172.17.0.0/12 base isn't a valid /12 boundary, so Docker canonicalizes it to 172.16.0.0/12 and allocates from 172.16.0.0/24 upward. On new installs going forward, HexOS now checks the subnets in use on the box during setup and picks the first /16 in the 172.17–172.31 range that doesn't overlap any of them, instead of leaving the stock default in place. A few notes on scope: Existing installs are deliberately left as-is. Changing the address pool on a system with deployed apps renumbers container networks and forces a redeploy of everything, so we won't touch it automatically. Your midclt call docker.update workaround is the right fix for an existing system, and it's safe to keep — HexOS only replaces the pool when it's still the untouched stock default, so a customized pool like yours won't be overwritten. One limitation of the automatic pick: it can only avoid subnets the NAS actually has an interface on. A 172.x VLAN or VPN range elsewhere on your network is invisible to it — that's the case a UI setting for the pool config covers, which is still on our list as a follow-up. Thanks again for the detailed diagnosis — it made this a straightforward fix!

Hello. Thanks for taking the time to write this. We did see the point of this and will roll it in to HexOS. Not sure when it will be releasaed but it will do this on new installs going forward once it's implimented. We don't want to cause any issues for anyone that's not currently affected.

I'd like a way to set up fan behavior within the HexOS dashboard (or curate an app that handles it). My motherboard bios doesn't allow me any control on drive temps, so my drives are always a little hotter than I'd prefer.

I appreciate the response. I imagine if it was easy somebody probably would have already integrated it into TrueNAS. Maybe you can use you relationships with the leadership and make it a feature request ;)

Unfortunately fan controller functionality is not built into truenas scale at this time and there are no fan controller apps on the truenas app catalog for us to curate.

Since the rollout of HexOS local the "hexos (ix-app)" showed up in the TrueNAS app list. Makes sense for running HexOS local software on TrueNAS. The app is showing to have available updates in the TrueNAS app list. Of course, this app doesn't show up the HexOS Deck interface. So I cannot update it from there. My question is: - What should I do with this app? - Should I update it manually? - Will HexOS update it automatically? When? - Why does it show an update but didn't update automatically yet? I understand, that the intention for HexOS is to never have to touch TrueNAS. For my use cases I do very often and just wondered about this.