Leaderboard

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.

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.

Hi all! I wanted to share my NAS journey starting with something completely nonsensical to something I actually daily drive now. The first one was a DIY fully 3d printed case before I understood what all of this home lab stuff even was. I tried to connect several SSDs and an HDD to a raspberry pi via a USB hub. Surprisingly, it worked, but very badly. Open Media Vault didn't quite like this setup. The next attempt was a mini NAS based on axzez's Interceptor board crammed into a Sony DVD RW drive enclosure. It was actually decent! But too little space for upgrades. I initially ran OMV on it, but after a while HexOS came out, and that was my first HexOS NAS. That's when I began getting a grip on how a NAS actually works, what HexOS is for, and how to get the most out of it. So the next interim solution was a spare converted Mac Pro case with some custom 3d printed HDD holder bars, but still based on the aforementioned Interceptor board. This worked ok for files but lacked versatility for any other home lab use cases. I later upgraded this setup to a normal PC motherboard and relocated the HDDs to the top shelf. That was way better and that's when I got into all of the side apps that HexOS/TrueNAS could run like local AI, Immich, Plex, Jellyfin, etc. Finally, I shelled out for a case designed for a NAS. And what a difference that made! Building a NAS in a case designed for one is night and day compared to building in a hacked together Mac case.

I just ran the command from immich go with this --on-errors=continue and pushed through it, then repeated. It seems to be some specific files that fail, as 5 images come back as "pending" in the cli

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

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.

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.

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.

Here is what Jon has said on the subject for HexOS. "The problem with SMART is that it leads to a lot of false positives. Users often replace drives too early due to a SMART notification that was being misinterpreted or overstated. SMART tries to be a crystal ball and predict when a drive is about to fail, but a lot of times it could be something totally unrelated to the drive that is causing SMART to act up (faulty SATA cable, bad PSU, etc.). In the world of TrueNAS, ZFS is the ultimate arbiter for deciding when a drive needs to be replaced. So I understand why TrueNAS doesn't feel the need to have a secondary "early warning system" when the system is already designed with fault-tolerance in mind. Furthermore it creates a giant burden of support as users constantly ask "well what does this SMART error mean to me?" I can tell you that from years of reading SMART data from customer systems, the answer on whether or not a drive replacement is really required is more often than not "it depends." Users that believe in using SMART can install the Scrutiny app. Our official stance on this is that ZFS is there to protect you from device failure, so SMART is just not necessary."

Hello, You shouldn't rename pools. It could brake SMB shares and defualt locations. Not worth it.

I encountered the same issue overnight. I was able to update the app in TrueNAS interface to 1.3.10 (can't recall the previous version) while it was in the "Deploying" state using the "three dots" next to "Edit" under "Application Info". Server still up as of 8 minutes ago.

Having AMP (https://cubecoders.com/AMP) supported would allow users to get game servers up and running super fast and easy! I know my primary use cases for hexos is media streaming, image backups, and gaming servers. The first two are already covered with plex and immich. Just need a game server app for hexos and therefore recommend AMP!

I will be having family use my server for backing stuff up and as we all know end users always end up accidently deleting things and then wanting them back. Luckily, TrueNAS has a recycle bin option and hopefully HexOS can add it in one day as a setting that can just be turned on. For anyone who finds this and wants to do it, here are the steps: Set up the folder in the HexOS UI and then in the TrueNAS UI go to: Shares > Click edit on the SMB you want to add the recycle bin too > Purpose = No Presets > Click Advanced Options > Scroll to Other Options > Check Export Recycle Bin Then you will want to set up a job to automatically empty your recycle bin: Navigate to Chron Jobs in the TrueNas UI (just search for it but it's under System > Advanced Settings). Click add then you can either enter this into the command field as ONE LINE or save it to a file find /mnt/HDDs/FOLDER/.recycle/* -atime +30 -delete; find /mnt/HDDs/FOLDER/.recycle/* -depth -type d -empty -delete; If you want to test to see what files will be deleted with this command run it without the "-delete" If you save it to a file (like I did) you will enter this as the command. sh /mnt/HDDs/PATH_TO_FILE/empty_recycle_bin.sh Then just fill out the description, run as truenas_admin, and how often you want it to run and you are good to go. Hope this helps and hopefully it can just be a 1 click type of setup in the future!! P.S. Here is what the commands do: The first command searches for files and directories in /mnt/HDDs/FOLDER/.recycle/ that have not been accessed in the last 30 days and deletes them. The second command searches for empty directories in /mnt/HDDs/FOLDER/.recycle/ and deletes them. Also commands were stolen from here

I love the purple 3d printed case! It's really sweet.

Well, I don't recommend either one I tried but they were a fun distraction for a day. It also shows the overall ability of HexOS/TrueNAS that, in my case, it ran on a PI 5, loaded PLEX and played a video off an external HHD Not well mind you but it worked. And please don't tell the admins I said that because I will just have to deny it. I have my reputation to consider. 😉

radarr, sonarr, prowlarr, qbittorrent have already been curated into 1 click install applications Portainer, Adguard Home, Karakeep, Homepage, NZBget, RustDesk, and Tautulli are available on the TrueNAS app store for manual installation Ombi can be installed via docker compose or you can use seerr to do a similar task.

Geez. I thought I was cutting edge with a GMKtek mini PC and a Rasberry Pie 5 as my non standard desktop PC entries.

Users licenses are saved under the email address you select when purchasing. Think of a Google or Apple account. We keep track of the amount of servers you link which takes a license. You can remove the link to a server which then adds the license back. You can buy now and use anything time..

We don't have hardware to test more of the advanced setups. It would be a lot of effort and time and costs to do this. We rely on trying to find things online for support for TrueNAS Scale since we are focused on making the interface and not the hardware. In the long run I think most of our users will max out at 2.5 to 10 GB nics. Probably between 4 and 7 drives. This is where we focus because the when you start going to more advanced setups those users will just use TrueNAS. Now I do see down the road we may have some features that are so easy to use along with a killer apps system that they may just buy for that.

Intel cards are well-supported by TrueNAS Scale. With that said I can't guarantee it but it should. Once you install it you'll have to update a few things if this isn't going to be a new install. On the server once fully booted you'll have to go through options 1 and 2 to make sure it knows to use the new network card. Once that is set you can log into the new ip address for the TrueNAS UI. Once in there you'll want to update the network settings to make sure the settings are correct for the new network card. Last step is edit the HexOS app in the app section of TrueNAS. You need to update the ip of what your TrueNAS was with the old network card to the ip of the new network card (Ip with TrueNAS WebUi). Just go down till you see a setting with the old ip and update to the new then scroll to the bottom to save it. Hope this helps. Thanks for supporting HexOS.

Thank you so much for this fix, it fixed it for me as well. I have been having the issue since the first Goldeye update, and this finally fixed it. I'm on 25.10.3 and still have the problem.

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

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

Thanks for the suggestion. We probably won't be able to look at doing this till after buddy backup are out. I'm not sure if they only show the connected ones or have an advanced toggle that would let you hide them indevidually. Thanks again for supporting HexOS!

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.

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

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

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

That worked thank you so much

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,

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'

Hi there :). I'm upgrading from a hdd enclosure that I had connected to a mini-pc to this. I'll have 48tb of usable space and plan on upgrading with another 5hdd's at some point and then another 5hdd's even further down the line. I'll eventually add a GPU as well. Looking at the Nvidia Quadro p5000. Named the server Leela 🙂 CPU - Intel Core i9-12900K Mobo - ASUS Z790 Prime Gaming Mem - 64gb DDR5 (16x4) Boot Storage - 1tb nvme Teamgroup Mass Storage - WD Red 12tb NAS HDD's x5 SAS - SVNXINGTII SAS9305-16i PSU - NZXT C1000 ATX 3.1 Case - RackOwl 4U Server Chassis

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.

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

+1 definitely passkey support

I suppose if there was a priority, that had to be set. I would rather have Passkey support over 2FA.

+1, and maybe passkey support?

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