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.

This happens to me at every update... Annoying! Thanks for the solution!

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

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.

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).

Hi there! I would love to have a way to have access to the server via my own domain. The way Yunohost its doing is fairly simple but breakes at lieased for me from time to time. Maybe there is a better way to have a self protecting login page reachable via a domain. I know that there are other ways like reverseproxy or tailscale but you have to manage security and update everything in the rightway or you have to pay for a service and teach the elder how to use tailscale ( sometimes twice a month ;D ). Love to have a solution thats easy to use, secure, stable, and inexpensive. Thanks for your thoughts on this!! ❤️

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.

After the 1.0 update not all my apps are showing on deck/local. I believe its only custom/docker compose apps. Before the update they where showing. Is there a way to fix this?

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.

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

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

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

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.

No one things thats good? Am I missing something?

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

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

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.

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 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.

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