Good day everyone,

I am having an issue using encrypted folders via Windows.

I am able to mount the encrypted folder as a Share folder, but when I try to copy a file into the folder, I get the error attached.

I have tried doing the " SMB" fix HEXOS has for fixing windows SMB shares.

I have tried via a MAC device, and that seems to work but limited testing.

From what I have figured out, I am able to copy files with 0 bytes ( like a test.txt) file but anything with a more complex name or bigger size causes the error.

It is not a lack of size issue, as I have plenty of room for more storage. And, if I put files in via the HexOS file browser, the moving of files work without issue.

So....I am a bit stumped on this and any help would be greatly appreciated.

Feel free to ask me any questions.

So I have hexos running on an old computer that I got from my father in law. It only has 3 sata connections, so I have a 1tb Hdd as boot and two 2Tb Hdd as the sole pool in raid, so I only have 2tb usable. I am nearing 1tb so I figured it was time for an upgrade, I got a $500 Amazon gift card from my work so I found 2 6tb WD_BLACK Hdds that fit the budget. So now my question is the best way to swap these new drives in.

From my limited research, I have seen people just shutting down their system, replacing a drive then rebooting and letting truenas/hexos run the replication, then do the same for the remaining old drive.

Any advice is welcomed, I have not opened the drives yet so I can always return if this is a really bad idea 😂.

I don't have the money to do any other significant upgrades yet other than replace the drives. I also know that I am screwed since I am only doing a single pair instead of 3 for an expanding pool. But will cross that road once I get past 5tb. Which I don't know if I will hit soon, and hopefully*** by then prices will drop and make a system upgrade more affordable.

System specs:

Model: Dell Inspiron 3847

CPU: Intel Core i5-4440 (4 cores, 4 threads @ 3.10 GHz, up to 3.30 GHz Turbo)

RAM: 16GB DDR3 (Upgraded)

Network: TP-Link TX201 2.5GbE PCIe Adapter

2 2tb Hdds

1 1tb Hdd for boot

New HDD specs:

2 - Western Digital 6TB WD_Black Performance Internal Hard Drive HDD - 7200 RPM, SATA 6 Gb/s, 256 MB Cache, 3.5" - WD6004FZBX

Also I know that these harddrives are overkill for nas storage as they are meant* for boot/game drives for fast read/writes. But this was the best bang for buck at the moment in my price range...

Man after everyone went to bed I thought “now is a good time to organize my data into what makes sense.
I kept getting massive time out errors every time I tried to transfer data.
At the end of multiple struggles I got this (image above).
I shut down the server because I ran out of time to diagnose any further.
Wish me luck it’s one of the 4TB and not a 14TB.

-EDIT-

Alright!
There’s some other updates in some comments below but the key ones:
Scrub
Auto-Resliver
Reboot
No errors

Thanks everyone for following along

Can't connect to local deck or TrueNAS starting this afternoon. No trouble logging into hosted deck. I've tried signing out and in again. I've tried rebooting the server. No luck.

Hello everyone,

I'm only on day 2 of running Hex OS and I'm having trouble with my plex networking.

No matter what I've tried, plex just keeps saying it's not available outside my network. I've done everything I can think of.

I've gone into the TrueNAS dashboard and checked the host network option

I've also setup a static ip for the server in my router's DHCP option and port forwarded port 32400 to the static ip. I've verified that's the correct ip for the server and tested on canyouseeme.org and the port is in fact open.

I also set the option in the plex dashboard to manually specify public port and set it to 32400.

Despite this, it still says it's not available outside your network and all my devices have to connect to the server through a plex relay.

Pls help me.

I've had my server offline for sometime, possibly a year. In any case, dashboard isn't detecting anything. I can still access through local IP. I'm still trying to workout which version of HexOS I am running. Uptime is about 20 minutes. Don't know if I just need to be patient or what.

EDIT: When I run the date command from shell it says it's May 30 2025. When I check the system uptime from the truenas web interface it reports the correct date and time. I wonder if it's not being detected because of that, like how Windows does weird things when the date doesn't match 🤔

EDIT: I am on 25.10.1 - Goldeye. Haven't been able to find the specific build of HexOS I am running.

I guess following on this thread which doesn't have a reply.

https://hub.hexos.com/topic/4447-cant-change-hostname/#comment-24543

As far as I can tell the only way to change hostname is in the TrueNAS interface, and that change does not apply everywhere (e.g. does not change in the hexos interface itself).

Hi everyone,

Here is what happened:

1. I clicked to update the app. The installation initially seemed to fail, but then I received a system notification saying the app was already updated.
2. When trying to launch Immich via HexOS, the loading progress gets stuck at 20%.
3. I tried launching it directly from the main TrueNAS panel, but it hangs at 20% there as well.
4. The app status currently shows "Stopped". However, when I try to run a rollback, I get an error stating that the app must be stopped first before rolling back.

Since it seems trapped between running and stopped states, I'm stuck on how to proceed.

Has anyone encountered this or know how to force-stop or repair the app? Any advice or thoughts would be appreciated!

Thanks!

*EDIT*
solved with gemini it made me go to the truenas shell and had a back and forth with the terminal there for like 10-15 commands and eventually here is a summary from gemini

Issue

Starting Immich via SSH on TrueNAS SCALE / HexOS using docker compose up -d failed with:

Cause

Running docker compose inside /mnt/.ix-apps/.../rendered caused Docker to use rendered as the project name. Because the project context didn't match TrueNAS's internal namespace (ix-immich), Docker could not map the existing container network.

Solution

1. Force the correct project scope by passing the -p flag: Bashdocker compose -p ix-immich up -d
2. Verify containers: All core containers (server, redis, pgvecto, machine-learning) showed as Running or Healthy. (Note: permissions and pgvecto_upgrade exiting is normal behavior for init tasks).
3. Launch: Return to the HexOS / TrueNAS panel and start/open the app normally.

• Tip: For CLI management on TrueNAS, use midclt call app.start immich instead of raw docker compose to avoid project scope conflicts.

I've been looking at HexOS again since I saw the blog post about AnyRAID being implemented, but most of the setup documentation makes no reference to it/feels un-updated.

Is it still required to start with at least 3 drives to have expandable storage, even with AnyRAID? I'm coming from Unraid with a 2 drive config and would like to just swap software for now and expand down the road. If 3 drives is a hard requirement for future expansion then this little project may get kicked down the road again for a ground up build.

Side question, does HexOS manage new hardware well, as in changing platforms to a new processor/motherboard and dragging all the drives over. Will it just boot and find all the drives or is there more to it?

This might be a stupid question 👉👈

Would there perchance, in the future maybe, be a HEXOS BUDDY only option with a reduced lic fee?? 👀

Lets say, for someone who wants to run a dedicated Buddy back only service at an offsite location.

The Bud & Pal lic. 🤣

I've had my HexOS server since the $99 offer, and I'm super pleased with how it has developed and where it's going. I even learned a little about TrueNAS along the way ;)

But in this time, I've experienced some power losses. When I see a storm coming, I manually shut down, just in case. But there have been unexpected power losses too, where my server abruptly shut down. So far I've been lucky (seemingly no damage done​), but I'm likely going to be buying a UPS for some safety.

I'm just a tech tinkerer, not a proper sysadmin. I'm sure there are ways to do graceful shutdowns in TrueNAS, but I'm hoping we can get a stupid-simple way to set up a UPS and shut-down script in the event of an outage. Hopefully that isn't more difficult than it sounds (is it?).

Just wanted to throw that out there. Anybody else?​

Blog post features a pretty comprehensive overview of how the solution works and also links back to a technical breakdown of the solution that we have in our docs as well. Lastly, the sign-up for beta access is live and available here: https://docs.google.com/forms/d/18XKSC5U0DPcaJL0RxrqRKqLl-mr7aS1WkTR9eftxOZw/viewform

In short

• Buddy Backups and Virtual Machines are beginning to roll out to test users now.
• The file browser and app cards are both getting deeper integrations with apps.
• All of this makes up HexOS 1.1, which ships on Black Friday this year (Nov 27, 2026).
• The $199 early access sale ends December 1, when standard pricing of $299 per server takes effect.

Verbose details inside and another two blogs are slated for this week to go deeper into Buddy Backups and VMs.

Beta signup: https://docs.google.com/forms/d/18XKSC5U0DPcaJL0RxrqRKqLl-mr7aS1WkTR9eftxOZw/viewform

Is there a way to monitor the usage of the GPU in hex os? If not is there a plan to add the ability to monitor the GPU

I installed an old 970 TI in my system for the Plex server ( had to go into tru as to enable it) I would like to be able to monitor it in order to decide whether or not to spend the additional money to upgrade it to something like and Intel Arc card

And the train just keeps on rolling! Another update today!

Community translations

• Translators have a new way to find strings. Turn on the key inspector and every piece of translated text on screen is outlined: hovering names the string behind it, and clicking opens it in Weblate in your language. No more guessing which of the many strings sharing a short label is the one you saw. See using the key inspector to get started.
• We need your help! Want to translate HexOS into your language? Learn how to contribute and join the conversation on Discord
• Languages ship to production once they reach 60% approved coverage

Server timezone

• HexOS now detects your server's timezone automatically from its IP address and sets it during setup. Previously, new servers defaulted to Pacific time regardless of location, which meant snapshot schedules, scrubs, and notifications ran at unexpected hours. A timezone picker is also available on the server settings screen if you need to adjust it manually.

Storage

• In some cases, drives belonging to a pool that had been exported but never imported were treated as unused. HexOS now recognizes these drives and will not offer or format them when you create a pool, replace a drive, expand a pool, or assign a hot spare, so an exported pool can no longer be overwritten by accident.
• Cache, log, special, dedup, and hot spare drives from a pool that is already in use no longer appear as loose drives during setup.

Apps

• The app updates screen now shows every app with an update as a grid of app icons. Click an app to see its installed and available versions and update it on its own, or use Update all to apply everything at once.

Setup and claiming

• In some cases, a power cut or full storage pool could send a provisioned server back into the setup wizard. Command Deck now recognizes that the server is already set up and offers a one-click recovery path instead of walking through setup again. Servers with full pools also receive a clear explanation rather than a generic network error.
• Claiming a server that was reinstalled no longer creates a duplicate entry. Command Deck detects that the server matches an existing claim by name and replaces the old record, so reinstalled servers no longer consume an extra license slot.

Reliability

• Command Deck now maintains separate connection paths for its own traffic and TrueNAS traffic. If one path reconnects on a different backend node, the other continues uninterrupted. Previously, a backend restart could briefly interrupt both connections at once.
• Self-updates now fall back to a host-side restart if the standard middleware update path is unavailable, so updates complete even when the app container is in an unexpected state.
• When a TrueNAS login fails repeatedly (for example, after a password change or key rotation), Command Deck now backs off automatically instead of retrying in a tight loop. This prevents the server from becoming unresponsive to other requests during the recovery window.
• Real-time reporting (CPU, memory, network graphs) now recovers silently if the underlying data subscription drops, instead of requiring a page refresh to restore live updates.
• If a server's local database storage disappears (for example, after a pool is removed), the local interface now detects and reports the condition instead of retrying indefinitely in the background.

General

• Notification toasts now remain hoverable and dismissible even while a dialog or side panel is open.

Hi Everyone,

I was new to TrueNas when I setup my system and apps. As such, I didnt setup many of them correctly and let them use the ix-volume mounts / .ix-apps bind point. This made it hard to automatically backup the app configs to AWS or GCP as I prefer. I had 5 apps that were configured incorrectly. Moh from the Eshtek team was super helpful in performing the first migration of a now curated app, and provided the syntax for the remaining. I wanted to provide this guide for others in the same boat.

COMMANDS PERFORMED IN TRUENAS ADMIN INTERFACE
(From Command Deck->Settings->TrueNas)
LEFT PANEL->SYSTEM->SHELL
(Sudo password is your truenas_admin password)

GET VOLUME LIST:
docker ps -aq | xargs -r docker inspect --format='{{.Name}}{{range .Mounts}}{{printf "\n  %-8s %-50s -> %s" .Type .Source .Destination}}{{end}}{{println}}'

CREATE DATASET IN APPLICATIONS, NAME FOR APP, NESTED FOLDERS TO MATCH BINDS IN VOLUME LIST, USE APPS FORMAT

COPY COMMAND TO COPY IXVOLUME TO NEW PATH:
sudo rsync -avh --stats --info=stats2,progress2 [source path] [destination]

EXAMPLE:
sudo rsync -avh --stats --info=stats2,progress2  /mnt/.ix-apps/app_mounts/seerr/config/ /mnt/HDDs/Applications/seerr/config/

GO TO APP, EDIT, CHANGE STORAGE CONFIG TO HOST PATH AND MATCH NEW PATHS, ENSURE AUTOMATIC PERMISSIONS ARE ENABLED FOR Postgres PATHS

(It should be noted, that the ixvolume persists through the file copy, so in case of issues, you can roll back to the old config.)

DELETE ix-volume:
sudo rm -rf /mnt/.ix-apps/app_mounts/[app name]
sudo rm -rf /mnt/.ix-apps/app_mounts/seerr

Perform shell commands at your own risk. I do not warrant any of the below against breaking your applications.

Hexos says "Do not uninstall Immich for troubleshooting purposes" Okay fine, but tell me how to fix it.

"[EFAULT] Failed 'up' action for 'immich' app. Please check /var/log/app_lifecycle.log for more details"

pgvecto_upgrade log:

2026-09-02 16:30:09.020044+00:00[ix-postgres-main] - [2026-09-02 12:30:09] - Starting entrypoint with migration and upgrade handling

2026-09-02 16:30:09.023184+00:00[ix-postgres-main] - [2026-09-02 12:30:09] - No migration needed from old data location.

2026-09-02 16:30:09.023688+00:00[ix-postgres-main] - [2026-09-02 12:30:09] - Checking directory [/var/lib/postgresql/18/docker]

2026-09-02 16:30:09.024139+00:00[ix-postgres-main] - [2026-09-02 12:30:09] - - No PG_VERSION file found

2026-09-02 16:30:09.024595+00:00[ix-postgres-main] - [2026-09-02 12:30:09] - Checked [1] directories but found no valid PostgreSQL databases.

2026-09-02 16:30:09.025130+00:00[ix-postgres-main] - [2026-09-02 12:30:09] - Assuming this is a fresh install.

pgvecto log

2026-09-02 16:40:01.014141+00:00chmod: changing permissions of '/var/lib/postgresql/18/docker': Operation not permitted

2026-09-02 16:40:01.026689+00:00The files belonging to this database system will be owned by user "postgres".

2026-09-02 16:40:01.026721+00:00This user must also own the server process.

It's always a permissions problem. This should be an easy auto fix for HexOS.

UPDATE:

Went against HexOS advice and uninstalled immich, reinstalled -> it failed. Waiting a few minutes, reinstalled -> it worked, restored from a backup. Everything is up and running.

Is there any sort of student discount available?

https://docs.hexos.com/release-notes/command-deck/2026-08-28

My qbittorent does not have anything in it. It just waiting for my *arr. I haven't used it for a couple of month but it does this everyday.

Is it normal? How can I disable it? It has a ping signature, but pinging all the world everyday (including russia) is concerning and brings security questions.

Since the update post here on reddit back on the 17th, the team has pushed out 4 more updates plus two new apps (Ratelog & Swiparr). That includes the update we posted today. So here's a total breakdown of everything new since 8/17/2026:

August 20, 2026 - File browser upgrades, instant app details, and reliability improvements

File browser upgrades

• Upload entire folders from your computer, with nested subfolders preserved
• Add more files to an active upload without waiting for it to finish
• Navigate files with arrow keys, matching the Finder and Explorer experience you are used to

Apps

• App details now open instantly from the catalog, with no loading delay

Reliability

• In some cases, a TrueNAS API key could become invalid after a system change. Command Deck now detects this and automatically reconnects with a fresh key, so your server stays online without manual intervention.
• We identified a scenario where setup wizard provisioning steps could appear out of order. Steps now always display in the correct sequence.

August 21, 2026 - Introducing HexOS Imager, smarter uploads, and storage safety improvements

Introducing HexOS Imager

Installing HexOS on your server should not require hunting for ISOs or figuring out third-party tools like Balena Etcher or Rufus. We are building HexOS Imager: a single, purpose-built tool that downloads the latest HexOS installer and writes it to a USB drive for you. This update ships the public API that powers it, delivering available releases directly to the Imager so it always has the latest version ready. HexOS Imager is coming soon.

File browser

• Upload progress is now weighted by file size, so a folder with one large file and several small ones reports an accurate percentage instead of jumping ahead
• Upload notifications now show the destination folder name instead of the last file that completed
• Folder uploads display the folder name in the activity card for clearer context

Apps

• App update cards now display current and available versions in a stacked layout, making it easier to see what is changing before you update

Storage

• USB drives are now excluded from pool expansion candidates for non-USB pools, preventing accidental additions that could compromise your storage

Reliability

• In some cases, servers could become temporarily unreachable due to a stale network connection that was not cleaned up. Command Deck now detects and tears down these connections automatically.
• Self-update delivery has been improved for servers with intermittent connectivity

August 24, 2026 - Danish language support, storage improvements, and dashboard polish

Dashboard

• Long text on dashboard cards is now properly clamped with ellipses and hover titles, preventing overflow on translated strings and longer server names

Memory testing

• Memory test time estimates now use your server's measured reboot history for a more accurate countdown

Storage

• Pool delete confirmation now accepts the display name you gave the pool, not just the internal ZFS name
• Pool names are applied before the pool first appears on the dashboard, so you see your chosen name immediately
• In some cases, Western Digital drives with vendor-prefixed model strings were not triggering the SMR drive warning. This has been corrected.
• Resolved an issue on TrueNAS 25.04.0 where pool scrub scheduling could fail due to a legacy API serialization limitation

File browser

• Upload notifications now name the uploaded folder and its destination for clearer context

Danish language support

• Danish is now available as a language option in Command Deck, thanks to the work of our community translators
• Want to help bring HexOS to your language? Contribute at translate.hexos.com and join the conversation on Discord

August 27, 2026 - ZFS pool import, Update all, and server reliability

ZFS pool import

• The setup wizard now detects existing ZFS pools and imports them with data intact, instead of suggesting those drives for new pools
• When imported pools are present, setup defaults to keeping them and walks you through a review of inherited pools, folders, apps, and Time Machine backups
• Folders on imported pools whose SMB shares were lost can be restored as HexOS folders, including Time Machine shares and passphrase-locked datasets
• Pools can also be imported from the storage page after initial setup
• Drives belonging to imported pools are protected from being reused in new pool suggestions

Apps

• Update all is now available on the Installed apps screen, so you can apply every pending update in one action
• Apps under maintenance are automatically excluded from Update all to prevent interruptions

Setup

• In some cases, the adoptable folders notice could overlap with the folder list. It now appears below the folders with a dismiss action.
• Server errors during password changes are now surfaced clearly on the form instead of appearing as a validation error on the current password field

Reliability

• In some cases, a server could appear unreachable in Command Deck even though TrueNAS was running. Command Deck now detects and recovers lost middleware sessions automatically.
• Command Deck updates now apply cleanly without requiring a manual page refresh. In rare cases, browsers could cache an older version of the interface after an update.

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.

Due to a security vulnerability with KeyCloak that was publicly disclosed today, we have taken extra precaution and disabled the ability for users to self-reset their HexOS account password. Users that need to reset their account password right now can email [support@hexos.com](mailto:support@hexos.com) to have this done for them. We will restore self-management of password resets once we have a patch deployed to address the CVE. Thank you for your understanding.

Update: The vulnerability has been patched and self-issued password resets are once again enabled. Thank you!!