Leaderboard

HexOS Gets a Major Upgrade This release introduces an improved Apps experience, new apps, two-factor authentication support, improved GPU support, and Goldeye compatibility. Read more about it on our docsite here at Command Deck Update - December 26, 2025 Also check out our latest blog for even more details! NOTE: This update was applied automatically. You may need to clear your cache.

Pushing a live hotfix right now that should address the majority of issues. For those experiencing problems, this should resolve them. If you are still stuck with specific apps, click options, reset, and try again. Still stuck? Email support@hexos.com so we can investigate further.

So after some digging, poking and planning I have NAS 2.0. Unlike my first nas that was built off of pure storage round 2 is planned on the fact that I have found a better way for my use case to use hexos. So moving to a newer cpu platform will give me more horsepower down the road swapping from a i3 8350k to an i7 10700. Moving to storage I will have 3 128g ssd as pool 1 for all my apps and vms. Next to that is 4 12tb drives that will be the main pool for storage. Setting up the next 6 8tb drives will be my once a month storage point "the drives will be spun down when not in use". As far as my old setup it will be getting 15 8tb hdds and will be colocated for in case things happen at home storage.

Let's Talk About Immich If you've been running Immich on HexOS this year, you know it hasn't been smooth sailing exactly. We want to talk about what's happened, why it was so challenging, and how we're working to handle these situations better in the future. What Happened? Earlier this year, Immich deprecated their old storage configuration and required all users to migrate to a new structure. For users running Immich through docker-compose or other manual setups, this meant updating some configuration files and running a few commands. Annoying, but manageable. For some HexOS users, the migration was more involved. Because of how TrueNAS SCALE structures application storage, moving to the new configuration required either reinstalling Immich fresh (the simplest solution) or manually migrating existing data between datasets (a process that involved SSH access, rsync commands, and careful attention to permissions). But if you're choosing between "reinstall the app" or "follow a 15-step guide," neither option feels great when you chose HexOS specifically to avoid that kind of complexity. Why Was This So Hard? When Immich made this change, we had a choice to make. We could have built a comprehensive rsync-based migration tool using the TrueNAS API. It has those capabilities. But that would have meant dropping everything else we were working on to build what amounts to using a cannon to kill a mosquito: a massive, complex solution for what we hope won't be a regularly recurring problem with this particular app. Instead, our community stepped up in a huge way. Users like @forsaken and @G-M0N3Y-2503 created detailed guides (to move or rsync your data). These guides walked through the manual migration process to preserve existing data in Immich. They focused on helping users through the immediate problem, while we continue building the platform we need to handle situations like this properly. That platform is HexOS Local: a locally-hosted management application that will let us perform complex operations without being bottlenecked by the engineering overhead of building one-off solutions through the SCALE API every time an application throws us a curveball. This reduces the technical burden on our team and, more importantly, gives us the flexibility to automate maintenance tasks that previously would have required manual intervention or massive engineering investments. This same platform will serve the Local UI/UX feature we've committed to delivering as part of our 1.0 release. We'll be talking a lot more about HexOS Local in an upcoming blog post, but the key takeaway is this: we're building HexOS to handle whatever the open-source ecosystem throws at it, without having to choose between "drop everything and build a custom tool" or "make users SSH into their servers." What About Right Now? If you're currently running Immich on the old storage configuration and haven't migrated yet, you have options: The simple path: Reinstall Immich fresh with the new configuration. Your photos will need to be re-uploaded, but the setup is clean and straightforward. The preservation path: Follow one of the community migration guides to keep your existing data in place. These guides are more technical and require command-line access, but they work. Our recommendation depends on your situation. If you have a manageable photo library and good backups, the fresh install is probably your best bet. If you have years of photos, carefully organized albums, and user configurations you don't want to recreate, the migration guides are there for you. And if this seems to daunting, email support@hexos.com so we can schedule a time to assist you directly. Moving Forward The Immich situation showed us exactly where we need to invest engineering effort. We can't keep facing the choice between building massive one-off solutions or asking users to break out the terminal. That's not sustainable, and it's not the HexOS we're building. Immich is an incredible project. It's exactly the kind of self-hosted solution we want to make accessible to everyone. The team behind it recently released v2.0, marking their stable release with better upgrade paths going forward. We're committed to making sure that when the next complex maintenance task comes up, whether it's Immich or any other application, we have the infrastructure in place to handle it gracefully. That's the HexOS we're building. Thanks for your patience while we get there.

Hi, very nice update, here are some points of feedback: On the Immich app, it showed the button "An updated configuration is available for this app", which I clicked. Afterwards, my Immich instance wouldn't start up again. I looked into it on the truenas interface where the server container wouldn't start but instead display long error messages before crashing. I noticed that the data storage path was moved from "Host Path" to ixVolume. After I changed it back to the original path, everything worked again. If the switch to an ixVolume is intended, I'd like to have the option (in HexOS) to choose a host path instead, as I want to be able to access my photos via the smb share from another pc. I guess, my trouble with the immich app could have been avoided, if the update notification in the HexOS interface showed the changes clearly, instead of the generic "This will reset every change you made in TrueNAS" message that pops up right now. Also, I installed Nextcloud before it was curated on HexOS, so now I would be interested in migrating my installation to the curated version (without uninstalling and re-installing the app). I tried using the configuration update button, which (expectedly) did not do anything.

This is a bit more of a loaded question than you'd expect. We do support usb DAS* we do not recommend using usb external storage and there is higher risk of things going wrong. Also it very much depends on the DAS hardware as well. As a cost cutting measure instead of passing through the HDD/SSD serial number many just tell the connected computer the same generic serial number for all the drives. Those enclosures do not work properly with HexOS. HexOS needs the DAS or enclosure to pass through unique serial numbers for each drive. If the DAS does provide the unique serial number for each drive the enclosure will work.

at the top of the hub, you can select the store tab and then orders or manage purchases. both should show you how many licenses you have

The difference is pretty big, while they do the same thing, they do it very differently. Immich just stores all the images in plain on the file system, all the processing is done on server side, you can connect an external library and if your Immich DB or installation becomes corrupted or breaks and there is no more support for Immich you just take the photos folder and move on. But the admin and everyone who's access to the folder can see all the photos of everyone, so privacy is not that great, but administration is easier and recovery in case of an issue is easy. Ente (FunFact: Ente is German for Duck) is all about privacy. The photos are all encrypted on the server and only the client side can decrypt/see the photos. This also means that the client side needs to do all the processing, but therefore the server can be very low spec (although this doesn't matter in our case, because Hexos needs to run in the first place, so HW specs is not really a concern in any way) and it needs S3 storage and requires more setup an administration. However if your Ente DB becomes corrupted or the Ente app breaks or the Ente dev stops and your app becomes unusable, you lose all your photos, because you cannot access it any other way. But until that happens only your client side device can access the photos and no-one else can.

I ran into the issue that my boot drive was corrupted and I had to restore my HexOS install from scratch. I found posts that said basically just reinstall it but nothing that explained the process. I had several issues, when I reinstalled HexOS it wanted to wipe my raid, once i disconnected the raid and went through the initial setup, I had no shares. So I wanted to document this so that others with this issue find a solution instead trying to rename and recreate shares and move data between datasets. This was done after I figured out a process for doing this so sorry if I missed any steps. Step 1. Remove the bad boot drive. Step 2: Disconnect the Raid drives. Step 3: Install your new boot drive and usb HexOS install media. Step 4: Follow the standard install process, including setting your admin account and claiming your server. When you finish the setup you will not have any disks so you will name your server and just continue. Step 5: Shutdown the system. Step 6: Reconnect your raid drives and boot up. Step 7: Log in to the TrueNAS gui by going to the IP address of your server in the browser and using the credentials you set up during install Username: truenas_admin Password: <whatever you entered at install>. Step 8: Go to Storage Tab and select Import Pool. 9: Select your pool from the drop down it should be named 'HDDs' and select Import. It will take a few minutes to import and complete. At this point the storage should be detected in HexOS and you should be able to start creating shares, but your existing folders and shares will not have returned. To get your shares back you must recreate them by renaming your datasets and naming them back as follows: Step 1: Under Datasets you can find all of your existing data on the RAID. Find the Dataset you want to restore in HEXOS and note the name. Step 2: Back in HexOS go to the Folder tab and select 'New Folder' Note: you may want to recreate your old users manually or create your folders with public access and recreate the users and add permissions later. Step 3: Create a new folder with the same name as the Dataset but add a 1 (In this case 'Plex1'). Make sure to keep the array the same 'HDDs; and give it the permissions you want (this can be adjusted later). Step 4: Back in TrueNAS go to Shares and select the edit button on the 'Plex1' share, depending on screen resolution you may need to scroll the horizontal scroll bar to the right. Step 5: In the side bar remove the '1' from the Path or use the drop down to select the original shared folder, then click into the Name field which should auto update and remove the 1. Step 6 Scroll down and click 'Save' and you will be prompted to restart the SMB service, do this and your share should be updated. Step 7: Navigate to the dataset tab select the 'Plex1' dataset and click delete on the right side. It will make you confirm by typing the whole dataset path. Step 8: When this is done you should be able to refresh the folders tab on the HexOS page and see the updated folder name (it took a minute to refresh for me). Redo this for each share that you wish to recreate. Once I did this and set up the users and permissions correctly, other servers I used to connect to my shares started working seamlessly. I didn't experience this but I can imagine you may run into some permissions issues since the new users in HexOS could have different IDs than before. Unfortunately you would need to manually adjust permissions on the files and folders. P.S. I imagine minutes after posting this someone will tell me I am dumb and should have done it this way, or someone else posted better over here. If that's the case let me know and Ill point to a better example, but when I needed help I couldn't find it.

Hey there! For advanced uses you can set up the UPS functionality within trueness if you have a supported UPS (which is most modern - be with USB or network connected). While it is slightly more technical, can be done and it's not too hard. You can also setup Peanut which will interface with Nut in truenas and give you a nice GUI.

I got it to fix below is my step-by-step solution Select Unclaim Server Plugged in HDMI cable to server to a monitor Reset the Server I was not getting any output so I did a reset to get an output. There was a boot window upon restarting the server, I selected it Let it boot while my other/main PC was on the HexOS dashboard discovering After about 10~ min it was discoverable Boot up took a while to complete Followed the "start-up" prompts on the HexOS dashboard I skipped the Storage set up process because I already had them set up prior Everything was working like before, but it did NOT complete the update that caused this issue I am holding off on updating until there is a more stable release. Hope this helps someone!

Truenas Scale is adding a File Browser as seen on their T3 pod cast

dm me we can try working this out

Hello all! We are excited to announce HexOS Local, powering the new local UI/UX for HexOS and capable of so much more. Read more about it on the Blogpost - Introducing HexOS Local

@Dylan OMG OMG OMG I figured it out! I went into TrueNAS and found the Applications dataset, found the permissions and everything looked fine there, but I also noticed that under the Applications folder there was the Plex folder. Only the Plex folder. Because I had only installed Plex, nothing else. And since I uninstalled it, it shouldn't still be there. The fact it is still there, I reasoned, could be causing issues when it tries to install. I figured it must not have fully deleted the folder during the uninstall. So I deleted that folder and then tried to install Plex again through HexOS and IT WORKED! So happy! Thank you for pointing me in the right place!

Hello, We just processed the refund for the 2 pack you purchased. Please give it 5 business days for the credit to show up. Apologies for the delay in your refund. We appreciate you supporting HexOS. Happy holidays.

A fine attempt to clarify some of the conflicting nomenclature of how storage verbiage is used. I hope this helps!! (clear as mud, right??)

Live fixes do not require users to perform any action locally. They hit our servers and affect everyone automatically. We will get you sorted through support. We are still tracking down why some reboots are losing connectivity to the deck. If you are comfortable with truenas UI, you can revert to a previous working boot by going to System > Boot and them clicking the activate icon on the right for the previous boot environment. Then restart.

We did deploy some hotfixes already but they were minor. The bigger issues are still being looked at by the team. We are on the trail of breadcrumbs now and should have most of this resolved soon. Thanks for everyone's patience and understanding.

Damn, launching a major update on the 26th of December is a bold move. I would have launched it in the first week of Jan as people using HexOS and celebrating Christmas would have been travelling (such as myself) and may have unknowingly reset their app settings after the update. I do have a remote connection via Tailscale so it wouldn't be a huge issue but it could have been a ton of work for me and anyone else to re-setup apps, like Immich to enable offsite backups, especially if those people didn't have a laptop or desktop to make the process easier and faster. I'm going to hold off on upgrading the apps until I get back and I'm going to backup all my data and settings before doing so as I don't want to lose access to my existing data and have to reinitialise the sync process. Still, I appreciate the drive to get HexOS features deployed within the calendar year and HexOS continues to improve significantly and return value for money, especially for early adopters.

We are investigating these issues. Thank you for reporting. I can confirm that when a curation gets updated, it can enable things like GPU transcoding. Our apologies for any inconvenience this has caused and we will work to right this in a future update.

😎 All part of the Beta experience lol As long as I don't lose my ACTUAL data I'm cool. Ripping all those DVDs was a PITA.

Interesting thing just happened: I updated Prowlarr to test the restore functionality for Sonarr and it wasn't reset after the script got updated. Started up and had all the Indexers and connections still set up. Could someone from the HexOS Team maybe elaborate on what those updates in their scripts actually do?

Awesome! I have a Intel iGPU with Jellyfin. How do I know if transcoding is taking advantage of my iGPU now?

They did post on X.

Another quarter until version 1.0. Can't say I'm not disappointed, but I get that quality takes time. At least give us a bone in the meantime.

Are we really talking about the "failure" of HexOS before we even go live? I got told off when I brought up this possibility several months ago and I was just talking about having backups. Can we at least wait until either Eshtek sounds a warning of some critical issue, Eshtek misses a checkpoint established for a specific date or they go even more silent?

It's here!!! https://forums.truenas.com/t/truenas-25-10-1-is-now-available/60830. Can't wait until this is integrated into HexOS!

Pretty disappointed with this limitation. I understand the reason to avoid unscrupulous reselling, but I do think there are better ways of avoiding that without these issues. There are probably a lot of people in a similar situation as me; wanting to get a license for a relative as the family tech guy, but not wanting to have to be the sys admin for everyone. I bought a license at release because I support the mission, with no intention of using it until the features got more flushed out (still on plain TrueNAS). I am in the process of building a NAS for my father, which I intended to set up with a HexOS license so he could use buddy backup and some apps as a relatively nontechnical user. The HexOS interface is simple enough I think he can grasp it. But if I have to be an admin for his NAS anyway I might as well just set up Tailscale and rsync on TrueNAS. I understand it's a sale price and I'll probably end up getting him his own but it just feels like a slap for people that bought in to support and I hate feeling like I'm throwing money away. I'm no business major but it seems like expanding the user base would be prioritized given the possibility of genuinely useful subscription features coming down the pipe. Anyways. Just my $0.02. Still love what you guys are building.

Buddy backup will definitely work with two licenses under the same account. You will be your own buddy 😉

For this, the fix was to in HexOS go into Settings > Reset > Unclaim System. Then reclaim the server and it should be fine. From what I can tell it gets like that because when you reclaim the server before restoring the config backup in TrueNAS the API key is different than what HexOS has so when you reclaim the server it checks and see the API key in TrueNAS and uses that. Sidenote if you are importing your config file back into TrueNAS for the apps if they are gone and nothing happens after you set the pool, try unsetting (unset pool) then select the pool again it and then it takes a bit to run through the HDDs and bam it comes back.

Are there plans to add other MFA possibilities than Google Authenticator? I'd really rather not have to use that app.

Hi there :). I'm upgrading from a hdd enclosure that I had connected to a mini-pc to this. I'll have 48tb of usable space and plan on upgrading with another 5hdd's at some point and then another 5hdd's even further down the line. I'll eventually add a GPU as well. Looking at the Nvidia Quadro p5000. Named the server Leela 🙂 CPU - Intel Core i9-12900K Mobo - ASUS Z790 Prime Gaming Mem - 64gb DDR5 (16x4) Boot Storage - 1tb nvme Teamgroup Mass Storage - WD Red 12tb NAS HDD's x5 SAS - SVNXINGTII SAS9305-16i PSU - NZXT C1000 ATX 3.1 Case - RackOwl 4U Server Chassis

If you are lucky it's just a caching issue. What if you refresh the page and reset the cache? (Ctrl + R on most browsers). Does the folders show correct then?

@Dylan I apologize if I have made anything confusing with my ramblings. To clarify, I installed HexOS following the standard install guide in February and it installed fine. I then used the HexOS Plex app install option, and it worked fine, but I never used it. Now just a couple days ago I try to use Plex and noticed it said there was an update available, but that update didn't work, so I uninstalled Plex through HexOS (which was successful) and tried reinstalling it through HexOS (which failed with the permissions error). I have never gone into TrueNAS for anything or modified any permissions. So I'm not sure how things got into this state, but I fully agree that this sounds like some kind of permissions issue. Since I have never done anything inside of TrueNAS, do you know if there is a guide somewhere regarding setting permissions? And what would I be looking for on the applications dataset/folder? You suggest making sure the application has write access, would that be HexOS having write permissions? Like, am I looking to give HexOS write permissions or am I looking to give Plex write permissions? Sorry, I just want to make sure I know what I'm looking for before I go into TrueNAS so I don't mess anything up, because the NAS itself has more space used than I have backup storage available. Thank you for your help so far, I really appreciate it!

Maybe it's just me being super confused, but why would you need it to use a public folder? For either Immich or Nextcloud, there are already software designed to (securely) host, provide and share data explicitly (and not share their guts to a public share over the LAN) Wouldn't it be counter-productive to have them use a public share? It makes way more sense for torrent clients, music libraries and the such, than for file hosting software that usually has to enforce user separation and priviledges in a way that the public SMB share won't reflect at all.

nextcloud should be more forgiving with moving files and changing directories.

Hey, No, don't restart regularly, high memory usage is good, because unused memory = wasted memory! Hexos is using the memory for the ARC cache, this is a read only cache where Hexos is preloading files which it believes you are using next and can then deliver those files from the memory instead of having to read them from the drives. Depending on your current usage you will not notice any performance boost with more memory, but you might future proof it. Memory prices are currently going through the roof, only buy memory if it's not overpriced.

Feature Suggestion: UPS Integration for Automatic Shutdown Enable Hexos to natively support UPS devices for automatic safe shutdown during power outages. • Benefits: Prevent data loss, monitor power status, and improve reliability. • Implementation: Integrate protocols like apcupsd or NUT for broad UPS compatibility and allow configurable shutdown actions. Would you like help submitting this suggestion? support UPS devices for automatic safe shutdown during power outages. • Benefits: Prevent data loss, monitor power status, and improve reliability. • Implementation: Integrate protocols like apcupsd or NUT for broad UPS compatibility and allow configurable shutdown actions. Would you like help submitting this suggestion?

Hey, Backups are done over the local network or Internet (which requires additional setup) and are done using the existing network connection. Using an USB cable to connect to your server is not supported. What exactly do you want to backup from your devices? There are different ways and apps, depending on what you want to do. Backing up pictures from your phones (and Mac maybe?) you can use Immich, which is a one click install app in Hexos. For documents you could use something like paperless, which requires manual loading of the files and is more like a document manager, rather then a simple backup solution. And there are other solutions to backup every kind of data. For your family, not living in your house, to be able to backup to your server you need to either setup a VPN or Cloudflare Tunnel or similar. Hexos is using ZFS and in ZFS it's called RaidZ1 and not Raid5 🙂 Also please post your specs of your Server which you want to use, this way we can identify possible incompatibilities and issues beforehand and mitigate them.

Not possible. License transfers are not permitted. All licenses are tied to the purchasing account.

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/

There is no announced timeframe at this time. The benefit is being able to make bigger pools.

Just here to say - you guys are awesome and thanks for keeping your promises! I'm perfectly fine with deck and enjoy being able to pull up the stats quickly anywhere I am, but local hosting is so important to this community, so thank you.

As of today, yes, you can access your server from anywhere using deck.hexos.com. I have a discussion planned with the team to allow you to disable remote access which would be as simple as us verifying the WAN IP of the client device being used to connect to the deck and making sure it matches the server's WAN IP. When HexOS Local arrives, you will be able to even further reduce your cloud dependency, but there are some features like installing apps/VMs, configuring buddy backups, and e-mail notifications that will require a connection to our deck. Thankfully that connection is outbound from your server, which doesn't require you to open any ports on your firewall and expose the system to the wider net. We also do have plans to implement oAuth and 2FA in the future to further enhance security and options.

Great to see the progress being made compared to the early launch last year, I'm exited to see where it goes with the new upcoming roadmap. While I'll personally will be waiting till a few more curated apps will be available (such as Kometa and Bazarr) it seems at least a good solid foundation will be standing with the 1.0 launch. Keep it up guys!

Ive got qbittorrent and plex running already but from what I can tell setting up airvpn isnt that simple - so would love an easier way to do that for qbittorrent specifically. And nextcloud. Have tried to set it up using the godawful truenas instructions but to no avail.

I've got a Zimaboard with 2x 4TB Seagate Ironwolf drives mounted on the back of my TV, bolted into the VESA mount of my TV. I really think this is the perfect home setup as long as your TV is not wall mounted. It's also practical to have the TV there when you need a monitor for the server, as I just did during the setup.

I have tried several NAS Systems before, none of them had a official good functioning mobile app, where i could quickly check basic stuff on the fly. Stuff like Updating Apps, restarting containers / VMs, restarting the entire Server, only basic things like this would be awesome. With the Management being Cloud based right now, it should not even be that big of an issue i think.

An app would be awesome