Leaderboard

I signed up as an early adopter last November, but have not yet installed it (running TrueNAS on an IXSystems Mini 3.0X+ w/a 5x8TB RAIDZ1) I'm building a custom NAS (probably overkill, this is all homelab stuff) now (parts slowly arriving) CPU: Intel 14500 I5 RAM: 128GB DDR4 (ouch!!!!) Mobo: ASUS B760M-A D4-CSM Supermicro 2U chassis 7x12TB (will be a RAIDZ2) with an HBA card and SAS extender in case I want to add more than the 8 drives the chassis supports 1TB Samsung 990 Pro NVME (boot drive, and planning on putting my VMs there, or at least the fast ones I need, w/backup to the big vdev) Intel A380 (hoping it'll work) for transcoding dual 10GBps NIC for connecting to my backbone I'll be reading a ton in the next week here 🙂 ~Horist

For us to dig deeper, I'd like you to report back with your hardware configuration as well as confirm what version of the OS you are running (25.10.1 or earlier?). There were some issues with the TrueNAS SCALE network reporting graphs in earlier releases. We'd also like to see a packet cap or something more than just a domain to prove what you're claiming here. Maybe wireshark monitor? Did you configure anything within TrueNAS SCALE's UI itself at any point or did you just utilize the HexOS dashboard for all your needs? Lots of things could account for the disk activity itself (such as background tasks or maintenance operations like the scrub that happens by default once a month) but the network activity is not us. StorJ is the used by TrueCloud if you configure your server to use it for backups (not something we support via HexOS today at all). Furthermore, the storj connection and the websocat connections are independent of each other. Websocat is used to make an outbound connection from a HexOS server to our Command Deck as outlined in one of our earlier blog posts here: https://docs.hexos.com/blog/2024-07-30.html. That's it. We do not and cannot transfer your data via that connection. The entirety of that connection is to give us API access to manage your system via our interface at deck.hexos.com. This ties back to something in TrueNAS and not anything with HexOS. Once you've unclaimed your system, we no longer have any access to do anything with your system. Generally speaking, it was quite an alarmist post and makes some pretty aggressive claims about data being "exfiltrated", that we were "misleading" about our product, and that you haven't seen any "meaningful updates." This was stated in our very first blog post that I previously linked but you won't by reliant on deck.hexos.com for long: https://docs.hexos.com/blog/2025-11-25.html. Furthermore, having a management interface hosted via cloud doesn't go against self-hosting as a concept. All of your data and applications are still running local on your LAN, which gives you the value of self-hosting. Management interactions for most customers are limited to initial setup of storage, folders, users, and applications. Once running, users mostly just interact with the applications and data, which run entirely local. Ultimately we want to know if this is a real bug/issue that ties back to TrueNAS SCALE so we can escalate to the right people or if this is simply a misunderstanding or misconfiguration. In reviewing multiple test systems we have configured and going back over a month in the network reporting, we see no significant network activity that matches anything close to what you are reporting.

Every time I update Hexos to latest version the website stops working. I can still login via TrueNAS but hexos is broken.

can you try doing this

Any plans to implement Kiwix serve? Being able to host Wikipedia locally (through .zim file) would be great. https://wiki.kiwix.org/wiki/Kiwix-serve It’s the only feature left that would remove my barrier to switching my current setup to hexos.

Update: I think I was able to get to the bottom of it. A while ago, after upgrading the server, I set a bunch of power efficiency options in BIOS to minimise the hardware impact on the power bill. However, it seems these settings may impact the system stability at high loads, which is what I've been experiencing. I also played around with the EXPO profile a little bit since I've seen system instability with some stock profiles in the past.

Oh and regarding this: You can unclaim your system from the Settings -> Reset page without losing any data.

I did miss this before I got around to it. I ended up reinstalling. I was able to migrate all my data off since it was in read only to save my self a headache of reorganizing all of it, then set it back up and moved data back onto it. This time I took a trueNAS backup so this cannot happen again. Thank you for your time and help!

So I noticed that HexOS requires encryption at the folder-creation stage for future offsite backups. Since Buddy Backup isn't out yet, how will the migration path look for users who have already populated large unencrypted datasets? Specifically: Will there be a built-in 'Migrate to Encrypted' tool to move data into a new encrypted dataset for Buddy Backup? Will Buddy Backup support 'Replication-level encryption' (encrypting the stream during transit/at rest on the destination) without requiring the source folder on my local NAS to be encrypted? What about application data folders that are already not encrypted, how would those be handled?

+1 is there any plans regarding ARM as of today ?

Would be great if we could get ente photos support just like immich. I tried to set it up myself but couldn't. Here's the link: https://ente.io/help/self-hosting/

I also would love to see paperless ngx curated!

Def not cloud only. If your isp/network supports peer to peer, we can coordinate that and then get out of the way. That is what's included in a lifetime license. If we end up having to relay traffic for some users, that will require a subscription as we will have to pay for the relay traffic, but obviously it will still be encrypted.

I ran into the same problem, and this fixed it. I think the install script for HexOS for this app needs to be modified slightly. Made a data set in the home-assistant folder, give it a name like "config" or "data", and modify the "Host Path" for "Home Assistant Config Storage" to be in that new dataset. Now I need to look at how to remove a bunch of junk from a folder without removing the datasets I want.

Yup! We went through great pains to make our UI mobile responsive, and this will make porting it to mobile apps easier in the future. For now, navigating to the deck from mobile is already a pretty pleasant experience.