All Activity
- Past hour
-
juice902 joined the community
-
beneenja joined the community
- Today
-
Knightarmor joined the community
-
jfox40 joined the community
-
mdz joined the community
-
jamomud joined the community
-
Alright, maybe not the solution you want but it worked for me. I installed jellyfin through truenas. This guide will point you generally correctly, https://jellyfin.org/docs/general/installation/advanced/truenas/. The important bit is to add your 'Movies' and 'Shows' folders under Additional storage. Hope it helps!
-
thewedge joined the community
-
Potatoman joined the community
-
Easiest way to have network printer capabillity on HexOS/TrueNAS?
renesdk replied to renesdk's topic in Applications
Does anyone have any experience with this one? GitHub - KaiHongTan/truenas-printserver · GitHub -
I'm having the same issue, I checked the logs in truenas while the app is starting and get the following: 2026-03-22 10:50:51.995861+00:00Unhandled exception. System.UnauthorizedAccessException: Access to the path '/cache/.jellyfin-cache' is denied. 2026-03-22 10:50:51.995892+00:00---> System.IO.IOException: Permission denied 2026-03-22 10:50:51.995900+00:00--- End of inner exception stack trace --- 2026-03-22 10:50:51.995906+00:00at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirError) 2026-03-22 10:50:51.995916+00:00at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String path, OpenFlags flags, Int32 mode, Boolean failForSymlink, Boolean& wasSymlink, Func`4 createOpenException) 2026-03-22 10:50:51.995922+00:00at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, UnixFileMode openPermissions, Int64& fileLength, UnixFileMode& filePermissions, Boolean failForSymlink, Boolean& wasSymlink, Func`4 createOpenException) It seems like it cannot access the /cache folder. Will investigate further.
-
I was just about to start my journey into the HexOS/TrueNAS ecosystem until I realized I also use my current Media server/NAS as a network print server. The printer is a Brother HL-2035 connected via USB to the server, and then serving the printer as a shared printer on the network. Are there any easy ways to do that with HexOS/TrueNAS?
-
SilberComic joined the community
-
Sierra joined the community
-
I don't know if "many" are thinking that, @vogam7, but I'm not. As @G-M0N3Y-2503 says this is par for the course in software development. "Communication" is a lot more work and headache than you would think and their time is much better spent on making the software.
- Yesterday
-
It also could be the case that they've done a bunch of internal testing and are just gradually rolling it out. But In software development delays occur, and people will be upset. It's way better to phrase an initial role out as early access testing in case there is an unforeseen showstopper. Than say it's good and then be called out for buggy software. So really it's a matter of if they hire PR or a community manager or not. I vote that there are better ways to spend that money. Considering that roadmaps and timelines are just a guess to attempt to make people happy, from my perspective they've been about as inaccurate as I'd expect, so no red flags from my perspective.
-
I forgot to answer about the Hexos license transfer part: Yes, that is possible and even very easier. On the Hexos website you just need to unclaim your old server and can then reclaim your new server, but It might take a couple of hours until your license because available again after unclaiming it from the old server.
-
vogam7 started following HexOS Local - Early Access User Sign Up
-
I'll just say what many are thinking here.. you're launching a hexos local beta just 9 days before the promised stable release date. How could this be included in 1.0 and called stable in under a week of testing? Refunds seem to be the go-to response for anyone who expresses frustration in other threads.. but that's beside the point for those of us who actually want this project to succeed. Missed deadlines are frustrating enough, but the communication issues that still keep coming up alongside them make it worse.. and for a project that depends on people investing in hardware, that trust matters. Server memory and now drives have nearly doubled since the originally promised end of 2025 release date. Every delay has a cost beyond just frustration. A straight timeline update would go a long way. I don't think you meant it this way, but the timing of this post is pretty telling... are we in for another delay?
-
MyHomeStuff changed their profile photo
-
Mr Spock changed their profile photo
-
Hi i just got Hexos up and running with a few apps and wanted to start getting my media server up and running. I installed jellyfinn and the Arr apps and got gluetun setup through dockge. I think now i just need to add gluetun into the networking in the .yml file for each arr app. For the life of me i cant find the .yml files to edit as they are made through hexos curated apps. Any way to access them to add gluetun for networking?
-
- 1
-
-
All very good info. I already have a 1 Gbit PCI-e Intel NIC on the server because of bad experiences even on Windows with the realtek NIC that is built in😂
-
Hey, please make sure you motherboard does not have a Realtek NIC, if it does, there's a high change that it will not work. In that case, you should get yourself an Intel NIC. Yes, everything over 32GB for the boot drive is wasted space, since you cannot use the boot drive for anything else then the OS. Apps are typically installed on a pool, this would be your HDD pool if you are not going to create a SSD pool as well. So your 250GB SSD is fine as boot drive, if you don't have a smaller one. Additionally, there is no write cache as other NAS OS might have, there is only a read cache, which doesn't offer a lot or any benefit with your use cases. So no, you don't need a cache drive, and big boot drive is just wasted space. 🙂
-
cjmauler changed their profile photo
-
Before I take the plunge to HexOS on my current NAS server: Intel 4770K 24 GB DDR3 RAM LSI M5015 HBA (up to 8 disks) Boot drive: Samsung 850 EVO - 250 GB SSD 8x Seagate IronWolf 2 TB Windows Server 2022 When I move over the disk controller will change to a Lenovo 430-16i LSI 9400-16i SATA / SAS3416 HBA Controller 12G in IT Mode Right now the machine is used as my video and music media server via Emby, and that won't change when i move to HexOS. Services I will add will probably be: Immich NextCloud Is there anything I should be aware of when it comes to the boot drive? I read somewhere a cache drive is recommended and the boot drive should be at least 500 GB. Is that requirement or just a "nice to have"? When HexOS has been installed on the machine can you somehow de-autorize it from the machine so the license can be used on a new machine if needed in the future?
-
Yves Desjardins started following HexOS Local - Early Access User Sign Up
- Last week
-
Love this guys content!
-
- 2
-
-
-
I've reinstalled the OS before removing my server from the deck.hexos.com page. I've been trying to pull in my server into that page, but none of the suggested troubleshooting tips work. The truenas UI works perfectly fine. Does it expect a specific password for the truenas_admin user and that's maybe why it's being found in the deck page?
-
Will 1.0 launch this month as expected?
Blair Young replied to Anthem's topic in Roadmap & Feature Requests
It has gone rather quiet. I thought I would see more general discussion or the odd update. Unless I've missed something the most recent update has been a revision to the blog introducing hex OS local originally published 25th Nov 2025 and updated 23rd Jan earlier this year. I'm not complaining before anyone jumps on me. I've been happily running the beta since originally hearing about it on LTT and couldn't have built my NAS without it (not with my skillset at the time anyway). So far it's been running flawlessly, shares and apps have been a breeze to set up, and the minor jobs I've had to do myself such as setting up a VM in truenas for Homeassistant have been recognised and appear on the Hex OS dashboard. I know it's possible I might have to start again from scratch but fingers crossed there is an update path that doesn't break everything. I have on occasion had to re-adopt the server on the dashboard (probably my fault) but it's only happened a couple of times. To avoid wiping everything I just popped out my drives, re-adopted, shut down, popped the drives back in and everything came back when I restarted. If there isn't a simple update to 1.0 with any luck a similar workaround will prevent data loss. -
BACKUP YOUR DATA!
-
AJV started following HexOS Local - Early Access User Sign Up
-
At this point, just using HexOS to create folders, users, install apps, etc. just like normal. Use it both locally and remotely. That's really it. At this point, the main thing we're testing is that it works correctly, navigating you to the local interface when on LAN, and giving you remote access via the deck when away. If you can break your system (non-critical data only), there are a few specific cases we would like to see users test like destroying the pool used by apps (Docker) manually via TrueNAS, then renavigate to deck.hexos.com to see if you can remediate the issue. Obviously not asking anyone with real data on their systems to do this, but for those that have test setups, just beat the heck out it and see what breaks. We test internally pretty rigorously, but there's always edge cases that we can miss and this is the chance to find those as best we can.
-
What does testing all entail? Like is there a checklist to follow, obviously if any thing random comes up, but yeah? Would love to be useful since it sounds like my pools won't be affected. Is there a way to back up settings just in case the OS goes haywire?
-
Should be no risk to data loss at all. The biggest risk is getting disconnected from our deck for server administration. That's why we want users to be able to talk to us via discord so that we can quickly remediate those types of problems if they occur. The big switch here initially is going to be authentication. We're moving to key cloak and we set up a more robust infrastructure to enable us to migrate users between production and development environments very easily. While we've done a ton of internal testing on this, we just want to be extra cautious before doing a mass migration of thousands of users all at once. Technically this is still pre 1.0, but the only things that really remain for us are hexos local and some improvements to our health monitoring systems.
-
Can you clarify on the risks with the data on the pools if going in this HexOS Local beta ? Would the worst case scenario be loosing the truenas/hexos install ? Also, is this part of the v1 HexOS realease ? or are we still in v0.xx version ?
-
truenas ui says deploying but they don't, I am at a loss for what to do right now aside from a fresh install which I would prefer not to do. I did to a fresh install of immich multiple times as that was the one I was less concerned with messing with but that doesn;t work either. would prefer not to have to resetup jellyfin.