Leaderboard

If you're seeing 'Failed to start transient service unit: Unit websocat.service was already loaded or has a fragment file', then you can try: sudo systemctl restart websocat

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

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.

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

Sorry if this has been mentioned already. There needs to be a way to store a boot disk config or recovery file on one of the arrays to allow easy recover of a dead boot drive (all done within HexOS! I shouldn't have to go into truenas if I don't know what I'm doing). I did install on redundant boot drives but bought too cheap and they both failed simultaneously. The only way I could find to recover was a fresh install without the array drives connected, then plug them in and manually recreate the exact share folder names in the HexOS from the list in truenas. Also, I would love to see a way to transfer or transition the boot drive to another drive by simply connecting a new drive. That way if all you had for a boot drive was a 1 Tb but wanted to use that for something else later you could get a smaller drive and transition.

I can confirm that if you do a fresh install you can set up the folders again and have access to all data, but you need to do things in a specific order and with the array disks unplugged (if you try to set up a new array through HexOS interface it will wipe the drives). If you know all your folders now you won't need to go into into truenas. I really think there needs to be a recovery feature in case of boot drive failure. Here's a link to a thread with good instructions on how to recover, but it would work to "downgrade" as well, though kinda janky. I would assume cloning would work as well but haven't tried it. https://hub.hexos.com/topic/3227-restoring-hexos-from-a-dead-boot-drive/

The reason Tailscale gets recommended so often is because it (and VPNs in general) is the most secure ways to access your services remotely. It's also pretty easy to install and get running. Nginx, on the other hand, is a completely different approach. To make lives a bit easier, let's take Nginx Proxy Manager instead of plain Nginx. Installing it is the easy part. The real work starts afterwards. You’ll usually need a domain, set up a DNS token for the certificate DNS challenge, configure something to keep your public IP updated, and create and manage all your subdomains. And all of that just to make your services reachable from outside your network. Once you’ve done that, your services are basically exposed to the entire internet. That means any device online can try to reach them. Because of that, you also need to put additional security measures in place to protect them from people trying to access or exploit them. Therefore only expose what you absolutely need to expose.

You rock, interesting fact, Chat GPT highlighted this post. Giving you Credit because i was also trying to fix this.

I had the same issue where HEX Deck would not recognize my server (deck said it was offline) but TrueNas UI worked. I realized it was my fault, I blocked it on my ubiquiti firewall accidentally when i was troubleshooting another issue. That's why truenas works because the HEX OS Deck has to call to Eshtek's server and the truenas ui does not. to answer another question in this forum, the local ui will mask this issue, not fix, because it will allow local connection, but wont change the fact that your server is blocked from external internet firewall level so connected to Eshtek wont work (only for this exact issue though). Another symptom of this exact issue was truenas did not have external internet access either, the app catalog was failing to update. Good luck to you guys hopefully this helps.

Hi I wrote the next blog https://www.gingerling.co.uk/how-easy-is-hexos-to-resurrect-when-youve-ignored-it-for-3-months-because-you-had-a-new-boyfriend/

Saw your post and I’ll add this to the list for us to curate. Seems like a good one!!

I just recently started building my NAS and many of the containers I run I have seen in this form but I also have been using audiobookshelf to host my own library of audiobooks. I have to use it in conjunction with tailscale to access it out of my network so maybe it is not ideal for "simplicity", but I would love to see something like this come to HexOS in the future.

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?