All Activity

Got the following Error when trying to add a drive to my pool. Context: I have an existing Pool of 3 20 TB hard drives. I had a 4th that I was using for my personal (non-Hexos) server before HexOs was out. I set up the Hexos Server a while back and transferred all my data over to the new HexOs Server. I final decided to take out the 20 TB drive from the old personal server I had and add it to the pool using the Expand option on Hex Os. As seen above I got errors trying to add to the pool but Hexos detects the Drive and says its healthy (as well as all other drives already in the pool) and was working just fine from the old server before moving it to the new one. (All drives where purchased new less than 5 years ago) Thank you for any help you can provide.

I feel the same way. I bought into HexOS in the rush to get in on the initial launch price and didn't quite realize the non-local first concept. I only want it to use internet for license, updates, and apps. The cloud command deck is a non-starter for me and almost makes me want a refund. As an extra bonus where I'm definitely a minority on, I'd prefer an option for offline update files even. Then I could have HexOS on my locked down no-internet VLAN and only update/deploy app bundles to it at my leisure. I know many think that goes against the simplicity of HexOS, but I find TrueNAS to be overly complex and would prefer HexOS simplicity for setting up pools and shares along with just having a zip/tarball to upload for updates/apps. I IT all day and don't want to come home to a TrueNAS mess, but also don't want to succumb to a cloud/internet first service. I'll choose TrueNAS complexity over internet requirements especially given the free price tag.

+1 for me in ups integration

Will 1.0 include quality of life improvements like update all button and betting installed app navigation? Scrolling left to right isn't great. Can we get improved dashboard with charts for app usage and other useful information? I get HexOS is supposed to be easy to use but not having the data available makes it harder since I am left to infer. There should be toggles for what to see on different pages and how detailed.

I'm also curious about this.

if im not mistaken it looks like it isn't a docker application. you'll likely be able to get it running inside of a linux vm

Offline Server for when SHTF happens. Anyone seen this yet? It’s from the guys over at crosstalk solutions. Wondering if it can be loaded as an app or a VM???

It is an interesting fix, an you may be onto something, I am also having infinite middleware processes being spawn over time pushing the file limits, at first I didn't notice the excessive proccesses and just increased the FD Limit, this caused the middleware processes to go rampant and to consume all ram available eventually causing applications to fail. I tried to apply the fix that you propose but my system failed to start at all and running "systemctl status websocat.service" returns Unit "websocat.service could not be found." Sadly I am not as knowledgeable on truenas or this level of linux systems, so I am unaware how common this is. Hopefully a fix can be found soon, for now I will keep the 1024 FD Limit as it keeps my system stable

Hi jonp, are there any updates on implementation of portainier in HEXOS? thank you

Having the same issue. Entering the above command just returns: Failed to start transient service unit: Unit websocat.service was already loaded or has a fragment file. Fresh install. I'm looking at the web GUI and can ping the server. Attempted to connect via Firefox 148.0.2 and Chrome 138.0.7204.184.

Any update on this request?

i have this issue as well..march 2026 and still not fixed...i give up

Thanks for posting what you found. I informed a team member to review this. If everything is in order, they will submit a ticket to IX (TrueNAS) for the next system update. We appreciate all the members helping out to make HexOS better for everyone. One of the postives of the internet and forums that don't get appriciated enough.

It seems like the TrueNAS Scale build repo on GitHub is "no longer actively maintained": https://github.com/truenas/scale-build Will this affect HexOS in the long term?

Ignore me, I just found the 'expand' button 🤦‍♂️

Bought four 4tb drives to replace the 500gb ones I started this journey with. Replacing went OK, but HexOS would not recognise the 4th drives as valid replacements, so did it through TNS, which worked fine. With all drives now replaced, pool is still showing the original 1.28tb of storage available (in HexOS and TNS). Have I missed something? I thought replacing all the drives with increased capacity would increase the available storage. I could rebuild the pool but I don't really want to!

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.

I am currently on that version now and have been since before I noticed the error. Any other ideas?

There is no point going into this beyond pointing out the facts as you have. There are other posts basically saying the same thing and it seems people are either hold their breath hoping something is coming soon and the folks who think Eshtek bit off more than they could chew. There is no way for us to know what is going on but there are some pretty specific things the app needs to be considered production. Being a friend and having Linus as an angel investor may be as much trouble for the team as it was good. Linus has advertised in a fow youtube posts what the app needs in his opinion and anything short of that is a failure. Well not a failure but not worth his sizeable investment. Tough spot to be in.

IDK really depends on how much they've been cooking and how reliable it is when all is said and done. At least what has been rumoured is a fair bit from a small team.

As the title said, I have been holding out since I purchased the key. Recently heard on the LTT podcast that 1.0 was launching at the end of March. Is that still the plan? I haven't seen an official blog update in a few months.

Right now the main server is just local storage for the workstation(s), project archive and so on. The offsite machine (lower core count) has the backup ran to it, also runs a Windows VM for CAD in the workshop. We're also building a "where did I leave my tools" system with PTZ camera's around the workshop and image classification so it can tell us where we left X tool, or where it was seen last at least. That'll be running in docker probably with a GPU for the image classification. I think I'm going to have to add an SSD pool to the workshop machine as running windows on spinning rust is hilarious in 2026...

Are there any plans to implement Passkeys?

It's been 16 months since release. 17 curated apps? Still "Early Access"? What a disappointment.

Hello, One way that could fix this is to do the following. Update to TrueNAS version 25.10.2.1. which applies permanent resource limit fixes. Thank you