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.

Hey, Seeing that you want to host a lot of VMs, may I suggest that you use Proxmox as the OS and Hexos as a VM. Proxmox is brilliant to run VMs while Hexos doesn't support VMs yet, you have to use the truenas gui and don't have the same flexibility as proxmox offers. Therefor, use proxmox ass your OS an Hexos in a VM. Just make sure to pass through the SATA controller to Hexos to give it HW level access and don't connect anything other then the Hexos drives to that controller. You can still just use Hexos as the OS and run your VMs in there, the initial Hexos setup is easier but you are not as flexible in the long run. There is no right or wrong in this one, both have there pros and cons. 🙂 HDDs: yes, avoid SMR drives as they are causing issues with ZFS. Go for CMR drives, but IIRC most, if not all 8TB drives are CMR anyway. Basically stay away from desktop and WD Red (non plus/pro) drives and go for NAS/Server drives. Check alternate if they still have refurbished server drives, might be a good starting point. And yes at least 3 drives now, to create a RaidZ1 which is expandable in the future. CPU: yes only AMD/Intel is supported. Intel iGPU from 12th gen onwards is brilliant for HW transcoding. 13th and 14th gen had problems where they died prematurely, but Intel supposedly fixed this with BIOS updates, but still a lot of people don't trust them, that's why some people don't recommend them. But you can still use them if you like, just make sure to use the latest bios and don't buy the F version as you mentioned. MoBo: whatever fits in the case and doesn't use a Realtek NIC. Typically ITX boards only have 1 pcie slot, so you can either use a GPU (for ML & LLM) or an Intel NIC or a HBA card. If you can go full ATX you don't have this problem anymore. Also most boards are either DDR4 or DDR5, you have to make your choice now. Almost no consumer CPU/MoBo supports ECC, so you will likely not be able to use your DDR4 EEC memory. Raid Controller: if you have enough SATA ports you don't necessarily need one. Network: wifi is a BIG no no! Neither Hexos nor Proxmox support WiFi you absolutely have to use a wired network connection, that's not optional but a hard requirement. Additionally Hexos doesn't not allow you to use your boot drive for anything else, so go with a small SSD (32GB are enough) if you use Hexos as your OS. If you use Proxmox, you don't have that limitation, there you can even install VMs on your boot drive.

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.

Hi All, this guide is now in the HexOS docs https://docs.hexos.com/community/community-guides/ReplicatingVirtualMachines.html

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

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.

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.

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.

i just tested my 25.10.3 - Goldeye .with a 3050 6gb on oculink and was able to pass through the card on 25.10.3 , this is with an AMD igpu 780M , jellyfin was set to transcode with nvenc set and i set it to point to /dev/dri/renderD129 /renderd128 would have been the 780M for my configuration at least. im using a hdmi emulatator dummy plug on the 3050 I have a 5060 ti 16gb i could replace it with i could retest with jellyfin if this might help

I'm having this issue too. Looks like there is a fix on GitHub posted below, but I can't figure out how to access the app configuration files for a curated app..... really hoping I don't need to nuke my install and back up all of my photos again...... If I do I think I'll give up on the curated apps and start installing this in a docker container now that I've managed to teach myself that process. Before I do though - did anyone find a way to fix this on HexOS? https://github.com/truenas/apps/issues/4628#issuecomment-4098018533

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!

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

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 🙂

First, a huge thank you to @lnkd for posting the actual steps to do this. All I did was follow everything they said and take pictures, so really all credit goes to them. Original post here: Prepare TrueNAS for reinstall: 1. Login to TrueNAS web interface – go to deck.hexos.com and click Settings: Then click the TrueNAS icon: 2. Once logged into TrueNAS, go to System > General Settings > Manage Configuration > Download File: 3. Read the note presented when you click Download File: 4. Click Save: 5. If you have encrypted datasets, go to Datasets > select the encrypted dataset > Export Key: 6. Now it is time to shutdown the server. In the top right of the TrueNAS web UI click the power icon and click shutdown: 7. Make your changes to the hardware that you would like – for me I added a 10 GB network card to run off fiber. 8. Prepare the HexOS installation drive by following these steps: https://hub.hexos.com/topic/103-illustrated-installation-guide-start-here/ 9. In your router settings, give the new hardware the same IP as your old one, then restart TrueNAS to grab the correct IP. 10. Once rebooted you can confirm on the server the IP address is correct: 11. Login to the TrueNAS web interface with the username and password you set during install (username should be truenas_admin). 12. Confirm your version on the dashboard – if needed, apply the update to the server: a. To confirm what version you need check the filename of the .tar file you downloaded from your configuration. It will have the version number on the end of it. b. Select the same version from the upgrade screen and confirm you want to switch to that upgrade train. c. Apply the pending updates and the system will reboot. 13. Go to Storage > Import Pool > find your zpool: 14. I have two pools so I will import them both. 15. Go into System > General Settings > Manage Configuration > Upload file: 16. The server will reboot after the configuration is applied. Log back into the TrueNAS server once the reboot is finalized. 17. If, like me, you replaced the network cards you will need to login directly to the server and adjust the IP settings: 18. Setup your new interface with the primary IP in CIDR notation, then you can log back into the TrueNAS server. 19. To setup apps, you need to go to Apps > Configuration > Unset Pool: 20. Restart your TrueNAS server then go back into Apps > Configuration > Choose Pool: 21. Once the pool is set you will see your apps again and be able to start them. 22. Navigate to the HexOS Interface (http://deck.hexos.com), unclaim your old server and claim your new one: 23. I ran into an issue where no matter what password I input it would not take it: 24. Currently troubleshooting that to be able to claim my HexOS server in the deck. All of my apps and storage are up and running so I will report back here when I fix this issue.

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.

I'm out of town right now but let me just state that I totally get the folks that are upset. Honestly, writing blogs is pretty stressful for me as we constantly are working on moving targets and I stress over communicating about things that are still in flux and getting the words right. Tbh, I stress over comms in general. It's nerve wrecking. It's why I am earmarking funds this year to bring someone in to handle this for us. I just didn't want to spend any money on non dev/support resources until we got to 1.0. Again, I get it and I am not gonna make any excuses for it, so if you want to be mad, please direct that anger at me, not my team. They are busting their butts to get this thing polished and rolled 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

Is it possible to back up the hexos configuration as something like a xml file? So all the settings can be backed up. Possible to automate the back up on a regular basis?

Try the following. Most likely this will fix your issue. If this does, TrueNAS has a fix that is in it's next update. 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. You might need to run this after reboots. Let us know if this works. Thank you,

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.

Just wanted to provide a quick update on this feature in particular. We are going to try to add this in for Q1 along with a few other big updates to be announced soon.

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.

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