Leaderboard

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.

Unless if @Mobius has another solution for your specific router (brand), you can also add 1.1.1.1 as the DNS server in your router, this way, you don't need to add a DNS server per device.

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

this is exactly what i would do for a tp link router.

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.

There is a chance this is happening because of how your router handles dns rebinding. Disabling dns rebind protection should allow you to access local. If you can share with me the brand of router you have I can share instructions for how to disable dns rebind protection

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.

Thanks for your Answer, i was unaware of the ZFS 80% 90%, 94% Rules.

I made a post about the same issue, they are looking into it:

fast answer: no you don't, full answer: from what i know zfs (the filesystem of truenas, underlying os of HexOS) have different stage of speed: under 80% the storage is fast en responsive, this is the base mode: the performance mode over 80% the file system is going from a performance mode to a more slow mode (zfs is attentively looking for freespace on disk to store files) so after you hit the 80% trigger the warning is on and you shouldn't ignore it it you are really near the full capacity (99%+)

Hey, just click back on the top left and then skip.

We are extremely close to releasing HexOS Local, our solution for accessing/managing your HexOS servers through a locally installed application on your server. Before we roll this out to all current users, we are looking for a handful that are able/willing to help us test the migration process. The requirements are pretty simple: 1) Users that agree to enroll in this early access test will have ALL of their servers migrated (we cannot apply the test to just a single server, so if you have multiple, it's all or nothing). 2) Users must have a discord account as those accepted will be invited to our new discord server for the purposes of bug reporting and support needs. If you are interested in helping us test this, please drop a DM to @mill3000 with the subject "HexOS Local Early Access" and be sure to include your Discord username in the message. Any questions, post them here! Thanks everyone!!

Hello, It seems the after the update some systems on reboot are reaching out to our server so it doesn't know your there. Try the following. Login to TrueNAS interface. Left side select "system". Then after screen refreshes select "shell" from the list. Paste in the following command. Can't use normal short cuts Will need to use Shift + Insert Key for pasting. sudo python /usr/lib/python3/dist-packages/middlewared/scripts/vendor_service.py If that works within about 1 min you should be able to go to deck.hexos.com and see your server or claim it.

Still learning about NAS servers in general, but I'm potentially looking to build my first NAS though I'm still not sure of some of the finer details; I'm quite familiar with hardware but not so much on the software. All I want to do is have a storage server for all my video work and general backups, but I have poor internet at my parents house and want to avoid a network bottleneck as much as possible in the meantime. It seems on typical NAS units it is possible to connect directly into a device via ethernet using it's IP address, but is this possible to achieve on a DIY NAS through HexOS? Was considering HexOS because it seemed easy to use for a noob like me with minimal compromise and the ability to expand my storage capacity fairly easily, but bouldn't find anything regarding whether it's even possible to do a direct ethernet connection from desktop to desktop.

I just tried that and it seemed to work thank you! The truenas button is also not greyed out now so thats great. I am logged into a different computer on my network using a different browser but I will try it on my other computer as well

Another typical problem is if you use Pi-Hole together with Unbound or possibly Adguardhome.

Hi Folks, the up-dated docs for HexOS system requirements are here: https://docs.hexos.com/getting-started/overview.html

I want you to know I successfully migrated only to experience database corruption about a week later losing my instance. I have a backup of the raw data fortunately. I understand engineering resources but this is why we really need to be able to have arbitrary backup and restore per app. Please bring that engineering focus to implement backup and restore up sooner than later. I can't wait to see that functioning built into buddy back up as well! More thoughts it looks like there's others in the community that are looking forward to this future as well see TrueNas Scale needs a first party application backup and restore system

Anyone still looking for their email to be changed please email support@hexos.com with their existing email account and the one you want to change to. Thank you.

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.

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.

Thanks for the fix! Like other people notice it also reduce cpu usage quite a bit, this gonna help my old i5 4690k based system but like you noted the script does not seem to survive an update cuz I just updated to 25.10.3 from 25.10.2.1 and I had to redo your fix.

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

Truenas Scale switched to the open source nvidia driver which only support never cards.

When I had local UI installed I had to log in just like the very first time I setup HexOS. It took a little while. Just long enough to make me think I was doing something wrong but the dashboard came up When I logged in I saw picture. I clicked on the word local and saw this. I am guessing it's not exactly the word that is the trigger. That just happens to be where the mouse pointer was when I clicked. I clicked on Switch to Hosted and went to the online dashboard so I started on local. Now to switch back I click the Return to Local button on the top banner. If you don't start that way I am guessing the down arrow next to your server name will allow you to go back and forth.

Hi Jamespigeon i also reach out to you in your dms

You can join the official discord and request help in there, this should get sorted out rather quickly. https://discord.gg/fCW2htvYdz

Follow up, @shpligthe updated driver's removed support for non-RTX cards as I understood so 10xx series and below no longer work with containers/apps but should still work with virtual machines because you install the drivers in the virtual machine and just have to make sure the card is passed through. @CosmoI am hoping the TrueNAS 26.1 update will address my specific card compatibility. A thread on the TrueNAS forum seems to suggest that NVidia driver 570. 172.08 is what shipped with Goldeye 25.10 and comparing that against the earliest Linux driver for the 5060 Ti on the NVidia website shows a driver version of 570.211.01. Long story short, I think this card just missed the boat on support but according to a recent TrueNAS blog post 26.1 adds NVidia driver 590.48 which means it'll definitely be supported on the next major HexOS release

I followed the instructions and it solved the problem for me. Can confirm an instant CPU usage drop. Thanks!

Hey, The Team believes there is a bug in Truenas itself related to the vendor service which triggers the command deck connection. This is currently under investigation.

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

Luxembourg!

You can still run VMs in Hexos, but you need to go to the Truenas Gui. VMs will only be supported in the future in the Hexos GUI. But Proxmox is likely the better OS for your purposes and just put Hexos in a VM. 🙂 If you run Hexos as the OS, the 64GB SSD is more then enough. If you want to run Proxmox then get a bigger SSD (512GB or more) and make sure it's not connected to the same controller ass your HDDs. (Best is getting a NVME SSD anyway for Proxmox and the VMs). If you use Hexos as OS, you need 3 SSDs (1 for the boot drive, at least 2 for a mirrored pool for apps and VMs) while you only need 1 SSD if you use Proxmox as the OS, since you can install everything on the boot drive. Check this video to get a good overview of all the WD drives: But you can also go for Seagate and their IronWolf (Pro) or Exos Range. Unless you go for 10gbps networking, the speed difference in the drives is not going to be really noticable/worth the extra cost for most users. I'm using Intertech rack-mounted server cases. They are big, offer a lot of space and airflow and are ugly as hell and are ment to be mounted into a 19'' rack. 🙂 So yeah, unfortunately I cannot give you any none rack mounted recommendations. 🙂 You can use some PowerLAN adapters in the meantime if needed. 🙂 Yes, the rest can run over wifi, just the server absolutely needs to be connected via cable. Fan noise and HDD noise are a real thing and can be annoying. You don't need to have it good looking but noisy in the living room you can also put it noisy and ugly in the garage or cellar 🙂 Haha, no, my country is a lot smaller, but has the same flag, just with lighter blue and alternate is also available here =D 😉 If you have any more questions don't be afraid to ask them 🙂 Also, once you have your server speced out make sure to post it here as well so that we can take a look to avoid common pitfalls before buying 🙂

Hey, the local GUI access is currently being rolled out to everyone in accordance to the purchase order and should be available to everyone in the next couple of days.

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 !

We've added everyone from our list. We'll start to migrate people based on the order of purchase to local UI.

Likely unpopular opinion, but thank you!

Hi everyone, this moring i though of a very good feature to add: gluetun + qbittorrent through a docker compose, just need to implement an interface where you select your vpn provider and fill the needed infos, you can add port forarding through the yaml install script ( for example for proton vpn) and i think i could be a very good option for the users who doesn't know how to setup a thing like this. i add below an example of a yaml docker compose file (mine): services: gluetun: cap_add: - NET_ADMIN container_name: gluetun devices: - /dev/net/tun:/dev/net/tun environment: - VPN_SERVICE_PROVIDER=custom - VPN_TYPE=wireguard - WIREGUARD_PRIVATE_KEY=XXXXXXXXXXXXXXXXXXXXX - WIREGUARD_PUBLIC_KEY=XXXXXXXXXXXXXXXXXXXX - WIREGUARD_ADDRESSES=10.2.0.2/32 - VPN_ENDPOINT_IP=185.246.211.193 - VPN_ENDPOINT_PORT=51820 - VPN_DNS_ADDRESS=10.2.0.1 - VPN_PORT_FORWARDING=on - VPN_PORT_FORWARDING_PROVIDER=protonvpn - WIREGUARD_MTU=1420 - FIREWALL_OUTBOUND_SUBNETS=192.168.1.0/24 image: qmcgaw/gluetun:latest ports: - '8080:8080' restart: unless-stopped volumes: - /mnt/HDDs/Applications/gluetun:/gluetun - /mnt/HDDs/Applications/gluetun:/tmp/gluetun gluetun-qbittorrent-port-manager: environment: HTTP_S: http PORT_FORWARDED: /tmp/gluetun/forwarded_port QBITTORRENT_PASS: password QBITTORRENT_PORT: 8080 QBITTORRENT_SERVER: localhost QBITTORRENT_USER: admin image: snoringdragon/gluetun-qbittorrent-port-manager:latest network_mode: service:gluetun restart: unless-stopped volumes: - /mnt/HDDs/Applications/gluetun:/tmp/gluetun qbittorrent: container_name: qbittorrent depends_on: - gluetun environment: - PUID=568 - PGID=568 - TZ=Europe/Paris - WEBUI_PORTS=8080/tcp image: ghcr.io/hotio/qbittorrent:latest network_mode: service:gluetun restart: unless-stopped volumes: - /mnt/HDDs/Applications/qbittorrent_vpn/config:/config - /mnt/HDDs/Applications/qbittorrent_vpn/data:/data - /mnt/HDDs/Downloads/qbittorrent:/downloads version: '3.9'

I tried following the recommended guides - frankly too time consuming/complicated for a non-technical person. Instead I went the uninstall/reinstall route, it's very easy if you can backup/re-upload your content (which takes forever 😑). The below post explains how to reinstall. It requires re-creating users/settings and logging in again on the mobile app.

I have a very similar situation, I want to use an old PC to make my first NAS for backing up important files from my Windows Desktop automatically (daily). I'm also new to NAS servers so I like the idea of using HEX OS for it's ease of use. I currently still live at University, so I imagine since I don't have any access to their router or admin privileges for the WIFI or internet that setting it up through a network connection like I would at home would be very difficult. It would be adequate for me to just connect to the NAS via a wired connection for now but before investing in Hex OS I would want to make sure this is possible.

Great question! Because I have limited needs, just a storage device with basic streaming capabilities, I use HexOS on the daily - mainly Plex. However, this is just part of my larger effort to build out a home solution that will eventually replace paid-for services that have increasingly risen is price and are more inclusive of advertisements (I LOATH ads with a perfect hatred). I am attempting to time my efforts with HexOS maturation. Which is to say as HexOS gains in features, I look to increase my DIY replacement of paid-for services. I know not everyone has the same timeline, level of effort, risk tolerance etc.. as I do, but that's why I jumped in early. I keep backups, try to contribute to this community and help where I can to see where this is going.

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! =)

Just a few things spring to mind that I’d love to see implemented at some point: - Jellyfin (my personal #1 most wanted) - Tailscale - Game servers (Minecraft, Valheim, etc.) - HomeAssistant would be super handy