All Activity

Jellyfin is now a curated app on HexOS. To install home assistant go to your HexOS deck > Apps > Curated > Jellyfin > Install. Find out more on our documentation site: https://docs.hexos.com/features/apps/

Home assistant is now a curated app on HexOS. To install home assistant go to your HexOS deck > Apps > Curated > Home Assistant > Install. Find out more on our documentation site: https://docs.hexos.com/features/apps/

Hi Folks, the up-dated docs for HexOS system requirements are here: https://docs.hexos.com/getting-started/overview.html

The HexOS download and install guide are now here: https://docs.hexos.com/getting-started/installation/InstallGuide.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.

Hi, when i created my pool I wasn't asked how to name it, HexOS decided it would be "HDDs". How to change that? I want to create a second pool and I'd like to have different names. "HDDs" and "HDDs-1" aren't really good names....

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.

Still having this issue. Shell command also produced the same error as others. Basically haven't be able to use the Hex-OS interface since i bought it haha. Great value right there.

Local is not required, I don't think. Cloud HexOS still works for me as before, if you go here https://deck.hexos.com/dash.

I'm running on a HP Proliant 8 (from around 2013) processor is a G2020T, HEXOS has been running fine for over a year on it and now the app wont start. Are you saying my hardware is now incompatible after the update? I want Local just as much as everyone else but making it required if it's going to force obsolescence seems like a bad choice.

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

I just installed HexOs (using the latest version, ISO TrueNAS-SCALE-25.10.3-HexOS) and I'm not able to detect the server on the Deck. I've verified I can ping directly, and can access the server via the TrueNas WebUI. I've tried manually plugging the IP into the Deck page, and it still doesn't find it. Machines are undoubtedly on the same network, as they are plugged into the same network switch via ethernet. Haven't had luck troubleshooting with any of the other posted content so far, looking for assistance. Verified in both Chrome (147.0.7727.116) and Firefox (150.0). I've tried on both deck.hexos.com and prod.hexos.com

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.

Hi Hex OS team, is it possible to have a one click deployment of guacamole app ? thank you

@da.rencan you also send me some times for tomorrow? Again in CST that we can do a Google meet?

@Maximus do you have time to do a Google meet tomorrow? We are in the CST. Can you send me over sometimes that would work for you and we can set up the appointment.

Yes that processor does not meet the minimum specs unfortunately.

Great point! I'll try and do some testing on this and see if that works.. The TrueNAS app install method does look to be a lot more granular with both access and folder creation.

I thought I remember reading something like this awhile back and not seeing an explanation so this checks with what I remember.

I have the issue since the latest truenas update (25.10.3) on an i5-7500. I have not tried to unclaim/claim, but rolling back back TN to 25.10.2.1 did not work. My machine is an HP ProDesk 600 G3 SFF i5-7500.

Hmm... @mill3000 can you connect with him on this issue?

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.

I am not expert, but after a bunch of trial and error with Gemini i was able to get my 1070 functioning. I am going to paste the steps that Gemini gave me. USE AT YOUR OWN RISK! I was doing this on a fresh install so there was no data for me to lose. If someone who knows what they are doing posts a better comment I will remove this. Again this is AI generated, but it did work for me. If you are running an older NVIDIA card (like a GTX 1070, 1080, etc.) and nvidia-smi is failing with a "communication error" after the latest update, it's because the new default Open Kernel drivers do not support your architecture. Follow these steps to manually inject the proprietary legacy driver. Step 1: Download the Legacy Driver First, we need to grab the driver extension file. (Note: Ensure the version in the URL matches your current TrueNAS SCALE base version). Bash wget -O /tmp/nvidia.raw https://truenas-drivers.zhouyou.info/25.10.2.1/nvidia.raw Step 2: Prepare the System We need to "unstack" the current (broken) driver extensions and temporarily unlock the read-only system directory to place the new file. Bash sudo systemd-sysext unmerge sudo zfs set readonly=off "$(zfs list -H -o name /usr)" Step 3: Install the Extension Move the driver file into the official system extension folder so it persists and becomes part of the system hierarchy. Bash sudo cp /tmp/nvidia.raw /usr/share/truenas/sysext-extensions/nvidia.raw Step 4: Lock and Merge Set the system back to read-only for security and merge the new driver extension. Bash sudo zfs set readonly=on "$(zfs list -H -o name /usr)" sudo systemd-sysext merge Step 5: Initialize the Device Nodes Sometimes the system needs a manual nudge to create the necessary communication nodes for the driver. Bash sudo mknod -m 666 /dev/nvidia-modeset c 195 254 Step 6: Verify Run the following command. If you see the ASCII table showing your GPU and driver version, you are successful! Bash nvidia-smi Note: You may need to restart your Apps (like Jellyfin or Plex) to ensure they pick up the "new" hardware hook. In the App configuration, ensure you have allocated 1 NVIDIA GPU.