All Activity

I'm digging that case

Sending you a DM.

After the latest update. I was installing a few of the latest curated apps. The first two installed fine (nextcloud and scrutiny) then all app installs after that started failing due to timeout. I also noticed that the folders tab and the locations in settings will not load. Everything else looks to be loading correctly. I have rebooted the server a few times now and it still isn't working.

Very cool setup! I like it alot

Thank you, wanted to make sure it was the same problem.

This is with the HexOS curated version of Plex. As far as I know, from previous threads, the TrueNAS Version configured using an ixVolume works because it has to do with a permissions error in the config. I just have Plex running on a different server and refuse to migrate it until the HexOS one-click app works as it should.

Hey there! For advanced uses you can set up the UPS functionality within trueness if you have a supported UPS (which is most modern - be with USB or network connected). While it is slightly more technical, can be done and it's not too hard. You can also setup Peanut which will interface with Nut in truenas and give you a nice GUI.

Hello guys! So, I’m new to the Homeland environment and I’m trying to install the Nextcloud AppApi so I can access the platform’s ExApps, but I’m having some difficulty because I’m not very experienced with this and I can’t get it to work. From what I understood, I need to install HaRP, but I haven’t found an “easy” tutorial to make it work. If anyone has a link or video that could help me, I’d really appreciate it! ”AppAPI deploy daemon AppAPI default deploy daemon "harp_proxy_host" is not accessible. Please check the daemon configuration.”

Is this with the HEXOS version of plex or the TrueNAS version with the "Plex Configuration Storage" Type on a ixVolume ?

I'm trying to set up and get going with immich, and the install goes fine. I have my google takeout in zip files, and a user-api key with all permissions. All of this works fine, however immigh-go rather quickly (after ~10 GB if data) runs into an error 500. Checking the server log from the truenas UI, I can see this is due to a permissions error, when immich is trying to copy a file. [Nest] 22 - 01/05/2026, 10:02:24 AM ERROR [Api:ErrorInterceptor~m4efv5f7] Unknown error: Error: EPERM: operation not permitted, copyfile '/data/upload/ce291ead-c9e1-433e-ba3a-de52c06d51bb/66/de/66de1127-26d4-435a-800f-0628803a8965.JPG.xmp' -> '/data/upload/ce291ead-c9e1-433e-ba3a-de52c06d51bb/82/5b/825ba53f-5e9c-456b-a96f-96b0ca3efc36.JPG.xmp' 2026-01-05 18:02:24.099069+00:00Error: EPERM: operation not permitted, copyfile '/data/upload/ce291ead-c9e1-433e-ba3a-de52c06d51bb/66/de/66de1127-26d4-435a-800f-0628803a8965.JPG.xmp' -> '/data/upload/ce291ead-c9e1-433e-ba3a-de52c06d51bb/82/5b/825ba53f-5e9c-456b-a96f-96b0ca3efc36.JPG.xmp' 2026-01-05 18:02:24.099097+00:00at async Object.copyFile (node:internal/fs/promises:621:10) 2026-01-05 18:02:24.099101+00:00at async AssetService.copySidecar (/usr/src/app/server/dist/services/asset.service.js:175:9) 2026-01-05 18:02:24.099104+00:00at async AssetService.copy (/usr/src/app/server/dist/services/asset.service.js:151:13) 2026-01-05 18:02:24.099112+00:00[Nest] 22 - 01/05/2026, 10:02:24 AM ERROR [Api:ErrorInterceptor~hsepvkht] Unknown error: Error: EPERM: operation not permitted, copyfile '/data/upload/ce291ead-c9e1-433e-ba3a-de52c06d51bb/ce/59/ce594961-1e68-4a6e-927a-e24886a53a97.JPG.xmp' -> '/data/upload/ce291ead-c9e1-433e-ba3a-de52c06d51bb/b5/48/b5488a04-5297-4252-9b9e-736b12c696d7.JPG.xmp' I have tried uninstalling immich and removing all folders associated with it, but this doesn't seem to help I have tried disabling the SMB share for the photos folder, but that's also not helping. Any idea where to look next for me?

Got it online again had to update on TrueNAS the Network Settings and enable ipv6. since then it is online again. very strange

same here TrueNas is online. but no HexOS!

I had that issue today. I couldn't get Command Deck or online UI on multiple devices, phone and desktop, I powered the server off manually and powered it back on. Everything was back to normal.

Was really hoping that this update, including automatic GPU detection, would resolve the Plex Intel GPU issues that have plagued HexOS since the beginning. No luck :( Still seeing the same issues. Jan 05, 2026 13:47:09.614 [139751593986872] DEBUG - [Req#cdc/Transcode] Codecs: testing hevc (decoder) with hwdevice vaapi Jan 05, 2026 13:47:09.614 [139751593986872] DEBUG - [Req#cdc/Transcode] Codecs: hardware transcoding: testing API vaapi for device '/dev/dri/renderD128' (Intel Raptor Lake-S GT1 [UHD Graphics 770]) Jan 05, 2026 13:47:09.614 [139751593986872] ERROR - [Req#cdc/Transcode] [FFMPEG] - Failed to initialise VAAPI connection: -1 (unknown libva error). Jan 05, 2026 13:47:09.614 [139751593986872] DEBUG - [Req#cdc/Transcode] Codecs: hardware transcoding: opening hw device failed - probably not supported by this system, error: I/O error Jan 05, 2026 13:47:09.614 [139751593986872] DEBUG - [Req#cdc/Transcode] Could not create hardware context for hevc Back to uninstalling Plex and waiting for the next round of updates!

Yes, i'm in the eu. I decided to ditch the secondhand hardware and go for new. I have a I5-14600K on the way with a MSI MAG Z790 Tomahawk Max WIFI and 32GB Crucial Pro CP2K16G56C46U5. If you have any better idea's please share. The hardware hasn't left the wharehouse yet.

Hi all. I was not sure is this the right place to post this. So some time ago i stumble on https://thelounge.chat/ . It is an IRC Client, web based, the most modern one ive seen. Is it possible to be integrated as an app in hexos ?

Ah, that makes sense why my 970 isn't working after the update to Goldeye. It works fine for my needs so I don't want to update that HW, so I'll try Fangtooth for now. Thanks for the info!

Just a point of data: I updated and had no issues. Everything is working as it did before the update. -- Orion

Does power consumption matter? Amd I guess you are in the eu

I was not able to get my server to be discoverable on the new update, even with the method above. However, I was able to return to a functioning state by booting to the previous version by connecting a monitor and keyboard directly to the server and changing the automatic boot option from the default newest version to the previous stable version during the 10 second window it gives.

So after some digging, poking and planning I have NAS 2.0. Unlike my first nas that was built off of pure storage round 2 is planned on the fact that I have found a better way for my use case to use hexos. So moving to a newer cpu platform will give me more horsepower down the road swapping from a i3 8350k to an i7 10700. Moving to storage I will have 3 128g ssd as pool 1 for all my apps and vms. Next to that is 4 12tb drives that will be the main pool for storage. Setting up the next 6 8tb drives will be my once a month storage point "the drives will be spun down when not in use". As far as my old setup it will be getting 15 8tb hdds and will be colocated for in case things happen at home storage.

Hello, I bought n2 and I try to install pve with USB key at boot i am not able to Access boot menu or simply boot on USB stick Is there a trick ... Someone can help me ?

I got it to fix below is my step-by-step solution Select Unclaim Server Plugged in HDMI cable to server to a monitor Reset the Server I was not getting any output so I did a reset to get an output. There was a boot window upon restarting the server, I selected it Let it boot while my other/main PC was on the HexOS dashboard discovering After about 10~ min it was discoverable Boot up took a while to complete Followed the "start-up" prompts on the HexOS dashboard I skipped the Storage set up process because I already had them set up prior Everything was working like before, but it did NOT complete the update that caused this issue I am holding off on updating until there is a more stable release. Hope this helps someone!

Truenas Scale is adding a File Browser as seen on their T3 pod cast

Same, I tried resetting the server but I keep getting this message.