File Browser

One of our most requested features is here. You can now manage your files without ever leaving Command Deck.

• Browse, inspect, and manage files on your server directly from Command Deck with a two-pane layout and details panel
• Switch between icon and list view modes
• Copy, move, delete, and rename files and folders with tracked progress and per-file transfer notifications
• Upload and download files directly to your NAS when on Local (this works over VPN connections as well, just not through the hosted Command Deck)
• Drag-and-drop upload support with bulk batching
• Download files from the internet directly to your server with optional checksum verification
• Shift-click range selection and Ctrl/Cmd-click toggle selection for managing multiple files at once
• Burn ISO files directly to USB devices attached to your server with verified writes and step-by-step progress tracking (Local connection required)

Apps

• First-boot-only install questions are now hidden from app Options after initial setup, keeping the settings view clean
• App update notifications are now grouped by day with the date each update was first detected
• Newly curated apps now appear newest-first in the catalog
• App version display now shows both the app version and TrueNAS catalog version

Storage

• Cache, log, special, and dedup vdev members are now correctly assigned to their pool instead of appearing as unused drives

Reliability

• DNS rebind protection detection: if your router is blocking Command Deck from reaching your server, HexOS now detects this and notifies you with guidance on how to fix it
• Improved hosted-mode banner: Return to Local is disabled until the local Command Deck is confirmed reachable

NOTE: All of these updates are applied automatically to your Command Deck. You may need to clear your cache. Help with clearing your cache is available here.

Release Notes Link: https://docs.hexos.com/release-notes/command-deck/2026-08-17

I originally installed HexOS, then I personally decided to upgrade the underlying TrueNAS install to 26.0.0-BETA.1. Looking back, running my actual server on an unsupported beta was probably not my best idea.

It worked fine for quite a while, until one normal reboot suddenly dropped me into (initramfs) because TrueNAS couldn’t import boot-pool.

BIOS still saw every drive, and my older 25.10.3 boot environment still worked, so the NVMe itself wasn’t dead.

The actual problem turned out to be VFIO grabbing my boot NVMe.

On working 25.10.3, my boot controller 0000:04:00.0 used:
.../drivers/nvme

On broken 26 Beta it was using:
.../drivers/vfio-pci

I found that TrueNAS had generated:
/etc/initramfs-tools/scripts/init-top/truenas_bind_vfio.sh

and the device list inside it actually included my boot NVMe.

The source was an old GPU isolation/passthrough setting. I cleared that setting in the 26 config, then booted once with break=top in GRUB so I could temporarily disable the bad VFIO script before it ran.

Once 26 successfully booted, I rebuilt the initramfs with:
python3 /usr/local/bin/truenas-initrd.py / --database /data/freenas-v1.db

After that, the VFIO script was gone from the rebuilt initramfs and a normal reboot worked.

Everything is back: all pools online, apps running, and the boot NVMe is using the correct nvme driver again.

In short:
Boot into an older working TrueNAS boot environment.

Remove the GPU isolation setting that caused the boot NVMe to be included in the VFIO device list.

Boot 26 once with break=top, disable truenas_bind_vfio.sh for that boot, then rebuild the 26 initramfs from inside 26:
python3 /usr/local/bin/truenas-initrd.py / --database /data/freenas-v1.db

Reboot normally

TL;DR: if TrueNAS 26 Beta suddenly says Failed to import boot-pool, BIOS still sees your drives, and an older boot environment works, check whether vfio-pci has grabbed your boot controller.

In my case, GPU isolation caused TrueNAS 26 Beta to include the boot NVMe in its VFIO device list.

If anyone hits the exact same issue, I have the full troubleshooting process and commands.

We have one experimental Curation this week. This was a big one.

Palworld Server - Create and manage a multiplayer palworld server.

Instructions for how to use it can be found on our docsite here

TLDR: current "local" access makes no sense and feels like they just ticked off a box "we have local access"

I have bought hexos license back in the day when the life time was on offer with the promise of local access being added in 1.0.

Now that local access is available, I finally did the install and oh boi was i disappointed. For me local access is a must have from security perspective. I have important files on NAS (that are backed up, but still) and having a remote access to that machine is big no no, either from having access to files or to the configuration. Because Hexos offers local access, I thought that remote access can be disabled, which I wanted to do because of potentially destructive config changes could be done remotely. Remote access cant be disabled, so I would need to rely on Hexos saying "yeah, trust us, our environment is secure". What if theres a leak/hack, what if they mess up and other user will be able to change my config (like it happened to ubiquity), what if their server goes haywire and start to change config on its own. As "unlikely" these risks might be, it just not a risk I would ever accept, even if it would be to store movies.

To me the current implementation of local very much feels like the team just needed to tick off "we have local access", because I am failing to see what the purpose of it currently is. Because if you have forced remote access, then you might as well change config that way. Its not like its running http and the packets could be intercepted.

If I could, I would cancel my order, but I cant, so hopefully full offline mode is coming at somepoint..

Also, this article on hexos forum caught my eye, wish hexos team would address it :)
https://hub.hexos.com/topic/595-hexos-security-and-compliance/

EDIT: also what happens if hexos goes bankrupt, because in the current state, the software will be unusable without hexos servers running.

EDIT 2: after digging in more, the machine (only runs truenas+hexos, nothing else) calls to:
update.truenas.com
o1158394.ingest.us.sentry.io (idk if thats hexos or truenas, either way i dont like it)
auth.hexos.com
prod.hexos.com
api.hexos.com

and seems like auth.hexos.com is taking care of checking licensing. as if i allow it, local access works but remote doesnt. My rant still stands tho, this is something that, tbf doesnt seem that hard to integrate, should be inside the settings of hexos. If hexos has local access, there should be a switch to disable remote, doesnt seem to me to be that hard to code, or am i missing something?

I would have been fine if Eshtek would go "we have local access, it still needs to call home for license, that is something we might look into in future to make it true offline, but right now remote access can be disabled". All im saying is that disabling a remote access should be a must have and top priority when adding local access

I cannot log into my Hexos dashboard. Why is that?

Pretty significant update and groundwork has been laid for buddy backups (coming soon)!

Hi!

I've had a browser bookmark to my local dashboard, which was naturally of course working well. But after a month or two of not using the "backend", and only using the apps from other devices, the link no longer resolves.

Switching to local from the dashboard doesn't work either.

Were there any changes I'm not aware of?

Thank you.

I would like to get rid of the http warnings, seems like Nginx Proxy Manager Plus

might be a good solution? Everything will still only be accessed locally (or locally over vpn).

I don't have the need to login to the deck of Hexos much lately, but I did today and thought I'd launch the suggested upgrades.. But then I see that it says I'm now running an unsupported version of TrueNAS. The upgrades I triggered were all directly through the deck GUI (local) ... why would that even give me the option of upgrading to a version that's not supported, seems kinda dumb that it lets me get into this situation.

Will this cause any troubles ? Will the version i'm on be supported later and get me past this predicament ? It's now running 26.0.0-BETA.2

https://preview.redd.it/hrtxjd0g05ih1.png?width=626&format=png&auto=webp&s=b14286265c289ff83ea76c5e564c9b8b256e2166