All Activity

I am experiencing the exact same issue for all my truenas apps installed via the truenas catalog. I can manually pull docker app updates for my custom apps installed via YAML though.

Exactly why I made this post - to encourage ongoing dialogue. (BTW - on MY media player just now happens to be a delightful mix of uplifting house transitioning to solid, German techno)

Replying to myself - likely an issue with the per app IP addressing that was released today on the current build. https://forums.truenas.com/t/per-app-ip-addressing-how-does-it-work/44818/20 Will update (and keep trying) until I get more info.

Went to upgrade a number of my docker apps today and got errors for all of them except Homarr. Seems like it s a common problem with the upgrade script: https://forums.truenas.com/t/latest-update-of-emby-today-fails/44853 Here is the error I received when trying to upgrade plex: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/middlewared/job.py", line 488, in run await self.future File "/usr/lib/python3/dist-packages/middlewared/job.py", line 535, in __run_body rv = await self.middleware.run_in_thread(self.method, *args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1364, in run_in_thread return await self.run_in_executor(io_thread_pool_executor, method, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1361, in run_in_executor return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 183, in nf return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 55, in nf res = f(*args, **kwargs) ^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/upgrade.py", line 62, in upgrade new_values = self.middleware.call_sync( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1651, in call_sync return self.run_coroutine(methodobj(*prepared_call.args)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1691, in run_coroutine return fut.result() ^^^^^^^^^^^^ File "/usr/lib/python3.11/concurrent/futures/_base.py", line 449, in result return self.__get_result() ^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/concurrent/futures/_base.py", line 401, in __get_result raise self._exception File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/schema_normalization.py", line 34, in normalize_and_validate_values dict_obj = await self.middleware.call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1626, in call return await self._call( ^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1457, in _call return await methodobj(*prepared_call.args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/plugins/apps/schema_validation.py", line 37, in validate_values verrors.check() File "/usr/lib/python3/dist-packages/middlewared/service_exception.py", line 72, in check raise self middlewared.service_exception.ValidationErrors: [EINVAL] values.network.web_port: A dict was expected More of an FYI than anything - in case anyone else runs into it.

having a similar issue: in TrueNAS I was able to see the server was not running and looked at logs seeing. Not sure how to fix this. 2025-06-02 13:02:07.473482+00:00microservices worker error: PostgresError: password authentication failed for user "immich", stack: PostgresError: password authentication failed for user "immich" 2025-06-02 13:02:07.473602+00:00at ErrorResponse (/usr/src/app/node_modules/postgres/cjs/src/connection.js:790:26)

Thank you so much. I had seen other treads with other ways to fix this issue, but they were convoluted. but this worked first go and was super simple. Thank you again.

Just a comment on the question itself, ”What new gear are you interested in?” I believe this topic by @Dylan will have eternal life. I compare this to a Swedish hifi forum I take part in, where a user in September 2005 posted the topic ”What are you listening to right now?” Two simple and innocent questions started it all. ”What’s rotating on your record player right now? What’s playing in Windows Media player at this moment? ” This topic is still active now in 2025 with new posts regularly. Hifi people always listen to music 😉 And in the area we’re in, there will always be new computer gear to catch your eye. Or new software, for that matter. I believe this was like hitting the nail on the head. A reflection on a Monday.

Yeah, and that method breaks HexOS dashboard which is not obvious, nor expected. Kind of important detail. It would be one thing if it was just something you had to (temporarily) do through TrueNAS, for it to show up. But it's quite the opposite effect.

@freid, please keep us updated. You are one of the first who can play with the WTR MAX! I am really curious about your experiences with this device.

yes Kinda sorta. adding a m.2 ssd as L2ARC will automatically cache. the most used files and speed up the performance when reading them. A special VDEV will also speed up the entire ssd to a certain degree especially when you have thousands of folders with thousands of files in them like what i'd expect from database workloads. However its not actually tiered behavior

Same Issue here

Thanks for the heads-up. From what I understand, unlike a typical Synology setup, TrueNAS doesn’t use SSDs for caching by default — instead, it relies entirely on RAM. So, if I want better performance, especially for read/write speeds, I should focus on adding more RAM. Is that correct? One of my intended use cases is running Docker containers with databases. If I install M.2 SSDs, would it be possible to combine them with my existing CMR HDDs in a way that prioritizes SSDs for high-performance data, like database workloads? Ideally, I'm hoping this can be handled automatically — does HexOS support that kind of tiered storage behavior?

Did this ever get resolved, I am having the same issue.

Great write up. I'd do it the same way Steps 1-6 is all that's needed (at this time) to reclaim a disconnected server using the same boot drive for anyone with that problem

I ran into the issue that my boot drive was corrupted and I had to restore my HexOS install from scratch. I found posts that said basically just reinstall it but nothing that explained the process. I had several issues, when I reinstalled HexOS it wanted to wipe my raid, once i disconnected the raid and went through the initial setup, I had no shares. So I wanted to document this so that others with this issue find a solution instead trying to rename and recreate shares and move data between datasets. This was done after I figured out a process for doing this so sorry if I missed any steps. Step 1. Remove the bad boot drive. Step 2: Disconnect the Raid drives. Step 3: Install your new boot drive and usb HexOS install media. Step 4: Follow the standard install process, including setting your admin account and claiming your server. When you finish the setup you will not have any disks so you will name your server and just continue. Step 5: Shutdown the system. Step 6: Reconnect your raid drives and boot up. Step 7: Log in to the TrueNAS gui by going to the IP address of your server in the browser and using the credentials you set up during install Username: truenas_admin Password: <whatever you entered at install>. Step 8: Go to Storage Tab and select Import Pool. 9: Select your pool from the drop down it should be named 'HDDs' and select Import. It will take a few minutes to import and complete. At this point the storage should be detected in HexOS and you should be able to start creating shares, but your existing folders and shares will not have returned. To get your shares back you must recreate them by renaming your datasets and naming them back as follows: Step 1: Under Datasets you can find all of your existing data on the RAID. Find the Dataset you want to restore in HEXOS and note the name. Step 2: Back in HexOS go to the Folder tab and select 'New Folder' Note: you may want to recreate your old users manually or create your folders with public access and recreate the users and add permissions later. Step 3: Create a new folder with the same name as the Dataset but add a 1 (In this case 'Plex1'). Make sure to keep the array the same 'HDDs; and give it the permissions you want (this can be adjusted later). Step 4: Back in TrueNAS go to Shares and select the edit button on the 'Plex1' share, depending on screen resolution you may need to scroll the horizontal scroll bar to the right. Step 5: In the side bar remove the '1' from the Path or use the drop down to select the original shared folder, then click into the Name field which should auto update and remove the 1. Step 6 Scroll down and click 'Save' and you will be prompted to restart the SMB service, do this and your share should be updated. Step 7: Navigate to the dataset tab select the 'Plex1' dataset and click delete on the right side. It will make you confirm by typing the whole dataset path. Step 8: When this is done you should be able to refresh the folders tab on the HexOS page and see the updated folder name (it took a minute to refresh for me). Redo this for each share that you wish to recreate. Once I did this and set up the users and permissions correctly, other servers I used to connect to my shares started working seamlessly. I didn't experience this but I can imagine you may run into some permissions issues since the new users in HexOS could have different IDs than before. Unfortunately you would need to manually adjust permissions on the files and folders. P.S. I imagine minutes after posting this someone will tell me I am dumb and should have done it this way, or someone else posted better over here. If that's the case let me know and Ill point to a better example, but when I needed help I couldn't find it.

Correct, but it is the only way currently until they push an update for HexOS that supports single drive pools. But good job pointing out the obvious.

Hey @freid What do you want to do with the cache drive? Please check this post from @Sonic for more information about cache in Hexos:

Exciting update! My AOOSTAR WTR MAX, which I ordered on April 2, 2025, has finally shipped as of May 29, 2025. I'm planning to re-use some existing hard drives, but for RAM and cache, I'm considering the following: RAM: Kingston Fury Impact 64GB (2x32GB) DDR5-5600 (Spec Sheet) Cache SSD: Crucial P3 Plus 1TB PCIe Gen4 NVMe SSD (Product Page) What do you all think? Are these solid picks, or would you recommend something better?

Noob here. Am i correct in saying that when I install hex os, i can also install AMP without installing a virtual machine to run/host games as a server like valheim and satisfactory?

I have the same problem

I think the core of your question is whether or not we have any type of revenue sharing agreement with iXsystems on lifetime licenses and the simple answer to that question is no, we do not.

Hi there and thanks for the questions! Long story short, we are not fundamentally changing the base of TrueNAS at this time which means that we are not offering a newer kernel version or different VM capabilities. With VMs in particular, can you walk me through what you are trying to do that isn’t currently possible with TrueNAS?

It's not recommended to run TrueNas updtaes since it can break HexOs.

Is it safe at this point to update or stay on 24.10?

in most cases its not but its also not making money like mining theoretically is.