Leaderboard

Sorry and Thank you for the update for some reason I couldn't find anywhere else it was stated being addressed. Looks like I know what I am doing this weekend.

Originally the reason for making all the apps a SambaShare was because sometimes users needed access to edit or change something in the apps directory. This is not something TrueNAS does but we were trying to make it easier for normal people who wouldn't know how to get into those folders and edit a file if they needed. It's still something we discuss if it's still something we need to do or maybe we should just hide it since we're on our way to building a whole apps system.

Hi, since the new HexOS update, I can't use the deck, server is still there, TrueNAS still accessible. I've unclaim and reclaim the server, but it's stuck on waiting for connection and will fail. HexOS now appears in the Applications tab on TrueNAS but will periodically try to start and then crash after running for a second, and there appears to be an update available. Thanks in advance for you help!

This was solved. The machine that HexOS is installed on had a different outbound IP than the machine that I was using Deck on. Using the TrueNAS interface, running this shell command got me the correct IP to enter manually on the Deck page. curl ipinfo.io/ip

Maybe by default it's public, but afterwards you can adjust the folder within HexOS to be private and be selective on which users have access. It's not as in-depth as the TrueNAS access options, but for someone like me who isn't well-versed in ACL access, it's a lot easier to understand and navigate.

Your not the first to ask and this post is not the first to bring it up. So far there has been no response.

Yup, this was addressed a while back. We do allow 1 drive pool creations now with a warning about no protection from data loss.

There has been no mention of this in the current roadmap. Your current options are either to place it somewhere where it can be connected via cable or get yourself 2 D-Lan adapters.

Yup. Unfortunately one of the packages that HexOS local depends on (bun) requires these CPU features (for now at least).

Question for any of you affected by this issue, are you running HexOS in a VM or on a really old CPU? HexOS Local, which is now a requirement of HexOS, requires the AVX and SSE4.2 instruction set on your processor to function. Pretty much all modern CPUs released since 2011 have these instruction sets (there may be a few outliers that I'm unaware of), so either you are all running on really really old hardware, or you're running in a VM that is not exposing those instruction sets with the CPU model. If a VM, you can change the CPU model to "host-passthrough" or simply something that supports these instruction sets.

I just saw an update pushed to my HexOS Deck; it's showing custom apps now, so I'd expect others to get the update soon if they're rolling it out slowly to everyone.

The site https://hexoscalculator.com seems to work well. It is simple up front, but has some advanced features as well.

In case you haven't found the other thread: It's not completely on the HexOS interface, but the rollback workaround is close.

AnyRaid is not released yet. When it gets released by the ZFS people it has to be adopted first into TrueNas. So just a guess is that it probably won't be here till next year. There won't be a way to convert to it. You have to start from scratch so you'd have to copy off all the data from your existing system to something and then format the drives as AnyRaid. Then copy the data back over. Thanks

Hi Jamespigeon i also reach out to you in your dms

I would love to see an easy to setup PXe server get integrated into HexOS

Hi everyone, I’ve been thinking about the roadmap lately and I’m a bit confused by the focus on Buddy Backup over "standard" Cloud Backup (Backblaze B2, S3, etc.) with proper snapshot management. I get that Buddy Backup is the "cool" feature that makes HexOS different from every other NAS OS out there, but I’m struggling to see the logic in prioritizing it right now. HexOS is still brand new, and the user base is obviously still small. Most of us don't actually have "buddies" running HexOS yet, so for the average user today, that feature isn't very useful yet. On the other hand, almost everyone needs a reliable way to get their data off-site to a professional provider immediately. Having a solid, classic cloud backup integration feels like a "must-have" for any NAS, whereas Buddy Backup feels like something that becomes great once the community is much larger. I feel like the majority of us would get way more value out of a standard cloud backup feature in the short term even if I agree that buddy backup is the way to go mid-long term. Am I the only one who feels this way? I’d love to hear what you guys think—maybe I’m missing something about why this is being pushed so hard early on ? Big shoutout to the dev team, congrats for 1.0 and keep up the great work !

I'm having the exact same issue on 25.10.2.1 — so the update alone doesn't fix it. I dug into it and found the actual root cause: The ix-vendor.service runs /usr/bin/start_vendor_service on boot, which calls vendor_service.py. This script starts a transient systemd unit called websocat.service (the websocket bridge between your local middleware and deck.hexos.com). The problem is that the script doesn't check whether websocat is already running before calling systemd-run --unit=websocat. If websocat is already active, the call fails with "Unit websocat.service was already loaded", but the script always exits with code 0 (it has a finally: sys.exit(0) block). Something then re-triggers ix-vendor, it fails again, and you get a rapid restart loop. Each loop iteration spawns a Python process that opens Docker sockets, and since the middlewared service only has a soft file descriptor limit of 1024, the FDs get exhausted quickly — hence the "Too many open files" error. Here's the fix that worked for me in truenas shell — a systemd override that adds a simple check before running the script: sudo mkdir -p /etc/systemd/system/ix-vendor.service.d/ sudo tee /etc/systemd/system/ix-vendor.service.d/no-loop.conf << 'EOF' [Service] ExecStart= ExecStart=/bin/bash -c 'if systemctl is-active --quiet websocat.service; then echo "websocat already running, skipping"; exit 0; fi; /usr/bin/start_vendor_service' EOF sudo systemctl daemon-reload sudo systemctl restart ix-vendor.service After this, ix-vendor shows active (exited) with status 0, websocat keeps running, and deck.hexos.com works fine. No more loop, no more FD exhaustion. I also raised the middleware FD limit as an extra safety net: sudo mkdir -p /etc/systemd/system/middlewared.service.d/ sudo tee /etc/systemd/system/middlewared.service.d/fd-limit.conf << 'EOF' [Service] LimitNOFILE=65536 EOF sudo systemctl daemon-reload sudo systemctl restart middlewared Both overrides live in /etc/systemd/system/ which - as far as I understand it "so far" - survives reboots. After a HexOS update you may want to verify they're still in place. Hopefully the HexOS team can add the is-active check to vendor_service.py itself so this gets fixed upstream.

UPDATE: As of 4/17/26, we have updated the ISO installer to run on version 25.10.3 of TrueNAS SCALE. Existing users should NOT reinstall to get this version. You can update from within the Activity card on the Dashboard (or the Notification). Hello and thank you for joining the HexOS beta program! You are an elite and vital part of this project and your participation is greatly appreciated. This post contains all the information you will need to get started with HexOS and how to communicate with our team during your beta experience. Disclaimer Beta Products, Software, and any related Services are still in development, and therefore, you are advised to safeguard important data, to use caution, and not to rely in any way on the correct functioning or performance of the products, software, or any related services. Beta Products and Services are provided to you “AS IS”, without any warranty whatsoever. Expectations During your participation in the beta, we expect you to do the obvious: use and test the software. But we also expect you to communicate with us when things don’t go right or if you’re having trouble. Please post feedback and let us know about your experiences, good and bad. That being said, please remember that this is beta software and early access. HexOS has a long and healthy roadmap ahead. Quickstart Guide For those that just want to get started, here’s the TLDR: Download the ISO here: https://downloads.hexos.com/TrueNAS-SCALE-25.10.3-HexOS.iso or https://hexos-downloads.sfo3.cdn.digitaloceanspaces.com/TrueNAS-SCALE-25.10.3-HexOS.iso (SHA256 Checksum: e551911445c95c1943e6638091896f34d2d423900cccd688ac09d811e78ed450) Use a tool such as Balena Etcher to image a USB flash device with the ISO. Boot your server from the flash device and install the OS to preferably an SSD. When given the option, opt to create the admin password in the installer (do not select the option to "Configure using WebUI"). Remove the flash device and reboot your server when the install is complete. From another device (mobile, tablet, desktop) that is on the same LAN as your server, login to https://deck.hexos.com using your HexOS credentials. Follow the instructions to complete your server configuration. NOTE: As of the 24.10.2.2 build of this ISO, configuring the admin password via the webUI option has been removed from the installer. However, if you select to create an admin password, but then attempt to "cancel" that process, the ISO will proceed with an installation with no admin password set. This is a known bug and the TrueNAS team will be addressing this in a future update to the ISO. Just don't cancel out of creating the admin password in the installer ;-). Hardware Requirements Booting HexOS is designed to support a wide variety of x86 hardware (Intel or AMD). The minimum requirements are a 2-core 64-bit CPU, 8GB of memory, and a 16GB or larger SSD boot device. However, depending on your needs for performance and applications, more resources may be required. Storage Pools Pools are made up of storage devices based on size and type (HDDs vs. SSDs). Storage devices in each pool need to be roughly the same size*. The OS boot device cannot be a part of a pool. Expandable pools require a minimum of 3 devices and can be grown one device at a time. Non-expandable pools can be created with 2 devices. Initial pool width should not exceed 8 devices. Maximum expanded pool width should not exceed 12 devices. At least one storage pool must be created to use HexOS. *In the event of slight variations (e.g. 240GB and 256GB), devices can be grouped, but total capacity for the pool will sacrifice the larger device’s excess storage. Build Recommendations HexOS has been designed so that a relatively modern PC can be easily transformed into a very viable home server. This means using standard HDDs/SSDs and using onboard controllers for storage/networking. However, since we’re based on TrueNAS, our hardware support is actually rather vast. For more detailed hardware recommendations for advanced builds, please refer to the TrueNAS SCALE Hardware Guide. Installing in a VM As HexOS is based on TrueNAS SCALE, it can be installed as a virtual machine as well. While the process should be fairly self-explanatory, please see the TrueNAS SCALE documentation for additional instructions on VM installation. Setup and Configuration Once the OS has been installed and rebooted, you will use a web browser on the same network as your server to register your system and complete the setup process. This can be a PC, tablet, or mobile device. Using a capable browser, login to https://deck.hexos.com. Beta 1 Features Our first release is focused on providing a streamlined user experience for setup and configuration and laying the framework for what’s to come. The main features of Beta 1 include: Setup and configuration wizard Configure your home server in minutes with ease. Analyze system health, with warnings for SMR HDDs. Auto-configure storage pools to safeguard against device failures. Securely manage your server remotely via Command Deck. Storage device management Detect error states and conditions and report through the dashboard Highlight individual storage devices and their respective faults Replace devices from storage pools due to failure or preventative maintenance Expand pools as little as one device at a time Folders and users Create and share folders over your local network. Easily manage permissions for secure access. Apps One-click deploy Immich as a personal photo library app. One-click deploy Plex as a home media server. Automatic folder creation for app storage. Dashboard / UI Access key statistics like CPU, memory, network, and storage usage at a glance. Monitor storage health and see alerts for errors or degraded pools. Manage multiple servers from a single, unified interface. Enjoy mobile-responsive design for effortless navigation on any device.

For detailed installation instructions, please refer to this thread: Illustrated Installation Guide - START HERE! =)