All Activity

Just to clarify, I’m definitely not one of the people who has been 'squeaking' or putting pressure on the devs. I actually really appreciate the work they’ve done. My post wasn't meant as a complaint, but rather as a genuine attempt to understand the logic behind the current priorities. I totally get that with the 1.0 release happening right now and all the feedback the team is juggling, the timing of my post might have been poorly interpreted. I apologize if it came across as 'just another demand'—that really wasn't my intent. The main reason I brought this up is that an integrated cloud backup (using StorJ/TrueNAS) was actually mentioned in the initial 2024 blog post as a supplement to Buddy Backup. Since I haven't seen much talk about it elsewhere, I just wanted to restart the conversation and see where it stands on the roadmap. Again, sorry if this was misread. I really like the project and I just want to see it become the best version of itself.

Hmm. Try to take this in the nature I mean it but HAVE YOU READ THESE FORUMS? I bet you can't find five other people calling for cloud storage access. I'm not saying they don't want it, just they are the silent folks. The squeaky wheel has hammered the team for local UI, not web access, and buddy backup. We are going to give Jonp a nervous breakdown if we keep trying to prioritize the next important thing before we even let them finish the core. I think your question is valid and your overall safety and security is solid but if they did things in the order you wanted there should not have been any work done on applications until the 1.0 NAS was build. I have agreed with most of the questioning of how thing were done up to now. And I agree security and backups are critical to the point that needs to be shored up next. I'm one of the loudest critics this project has but I think it's time to step back, take a breath, let the dust settle and maybe celebrate a little. There is a forum topic for what apps should be looked at next. If you have a favorite put it in there. I might not ever use it but I am not arrogant enough t think my NAS/2 Local/2 Remote backup setup can't be improved or made simpler I'm going to personally step back and say congratulations team. I'm not in the first group so I haven't seen the 1.0 version but I know it was a lot of work. Reading through the forums overall, including posts like this, I can see there is still lots of work to do. And @jonpI am looking forward to shaking my head and second guessing every post like you are going out of your way to make my life more difficult, just like I have for the last year+. But for now, my hat if off to you. 😌

Hello, I hadn't updated my Immich instance in about two weeks and decided to login and run all my updates, all updated except Immich. I tried uninstall and reinstall, still failed. Then I went to the TrueNas UI and installed it from there and it worked fine (without binding any directories). I seem to be stuck since I do not know what the default postgres password was set to. I still have all of the config and images, but I wasn't aware I needed to do a migration until I looked at the forums today. Is there any way someone could help me get an Immich instance back up with all of my config and photos? Thanks,

I get that, but I think a NAS is about much more than just avoiding the cloud. For me, it's about performance and local services that a cloud-only setup can't handle. I need local storage for things like editing video files directly off the NAS, running Home Assistant, storing security camera footage, and using Cloudflare Zero Trust to access my setup remotely. That said, I still need a 'Plan B' for my most critical data (like 300GB of Immich and Nextcloud files). This is where the Buddy Backup/VM argument doesn't really work for me. At $6/TB on Backblaze B2, my offsite backup costs next to nothing. Renting a VM with enough storage to act as a Buddy node would be significantly more expensive, plus you have to factor in the additional HexOS license and the time spent managing the VM. To me, standard Cloud Backup is just the cheapest and most reliable way to protect important data. It’s also arguably more secure and durable than a friend's house or a DIY VM. But I know we all have a different usage for our NAS, so I'm curious to see how others are planning to handle this.

I think the reasoning is, if you're paying for cloud storage and happy with it, then you probably wouldn't bother with a NAS. Realistically, cloud alone is probably enough for most people. So I think they are targeting people who want to own their own data, so "buddy" back up is probably the easiest. Marketing aside, it's really just a 2nd license to HexOS you need, the hardware and off-site could be a VM in the cloud if you wanted.

Hi everyone, I’ve been thinking about the roadmap lately and I’m a bit confused by the focus on Buddy Backup over "standard" Cloud Backup (Backblaze B2, S3, etc.) with proper snapshot management. I get that Buddy Backup is the "cool" feature that makes HexOS different from every other NAS OS out there, but I’m struggling to see the logic in prioritizing it right now. HexOS is still brand new, and the user base is obviously still small. Most of us don't actually have "buddies" running HexOS yet, so for the average user today, that feature isn't very useful yet. On the other hand, almost everyone needs a reliable way to get their data off-site to a professional provider immediately. Having a solid, classic cloud backup integration feels like a "must-have" for any NAS, whereas Buddy Backup feels like something that becomes great once the community is much larger. I feel like the majority of us would get way more value out of a standard cloud backup feature in the short term even if I agree that buddy backup is the way to go mid-long term. Am I the only one who feels this way? I’d love to hear what you guys think—maybe I’m missing something about why this is being pushed so hard early on ? Big shoutout to the dev team, congrats for 1.0 and keep up the great work !

I did say BY end of April ;-). Truth is we have been pretty much right there aside from a few issues, but the big one was the availability of HexOS Local. But we decided yesterday that we can still call this 1.0 and roll out Local to everyone over time. The local project has to be rolled out more slowly as we have SSL cert issuance limits right now.

Hype, so keen for suib 5 second load times!

Well that was quick lol. Went from end of month to now! What happened that it didn’t need to be delayed anymore? No complaints here of course. Great job.

https://docs.hexos.com/blog/2026-04-02.html

https://docs.hexos.com/blog/2026-04-02.html

I appreciate the understanding. I'm actually in the process of approving the post right now. Had a full day packed so it had to wait until tonight.

Is the blog post going to be up today or do you need to push it back to tomorrow? I know how that sounds, but I am serious. Traveling can really mess with your biorhythm with jet lag on top of trying to do your regular day job as well as damage control blog posts.

I agree, I added a GPU to my HexOS server for the same reason and would love to have a tile for the GPU like we have for the CPU.

Likely unpopular opinion, but thank you!

I'm out of town right now but let me just state that I totally get the folks that are upset. Honestly, writing blogs is pretty stressful for me as we constantly are working on moving targets and I stress over communicating about things that are still in flux and getting the words right. Tbh, I stress over comms in general. It's nerve wrecking. It's why I am earmarking funds this year to bring someone in to handle this for us. I just didn't want to spend any money on non dev/support resources until we got to 1.0. Again, I get it and I am not gonna make any excuses for it, so if you want to be mad, please direct that anger at me, not my team. They are busting their butts to get this thing polished and rolled out.

I Linus was telling the truth Local UI was part of the original plan to him. I don't think he would have investor a quarter of a million dollars without it. He has listed to many examples of companies going under and the content he purchased goes away for lack of the "local" option.. I have said this so many times I am even getting tired of hearing it but... I have a professionally managed Unraid NAS at a cost but it is worth it to me. I thought this project would be my chance to take back control but I underestimated what that would take. So I now have a $99 NAS that my wife and I can load up and a $99 sandbox to use to look at Jellyfin, Plex, Immich and other apps in TrueNAS. I don't think I will ever use any long term within TrueNAS but I have a pair of long term Linux servers that could do the job. The first video Linus did where he and Jake marveled at how HexOS make the setup of the storage pools and security very easy got my attention. I can do that and set up accounts for myself and my wife that allow us access as needed without risking making unnecessary or possibly hazardous admin level changes. I've done that in Windows and HexOS in my testing and had to do full delete/reloads because of it. I already have everything I need and am fine with the cost. I don't know if I gain anything with the local UI so to me any other time taken is an unnecessary delay. For me (and yes I understand it is probably just me) release 1.0 should have been the core NAS itself. Then build off that for release 2.0 and beyond for all the apps and VM parts. I think the project could be run better from the customer standpoint but if @jonp DM'ed me and questioned why I fuss so much if I don't really care. It's a valid point but this is a slice of the market that needs to be filled and whoever fills it needs to understand this product in not for network/NAS folks who recognize progress. It's for folks who probably couldn't build a NAS themselves. Of for folks who have no interest in learning TrueNAS or they would just use that. Those types of people aren't going to sit quietly and wait for quarterly information dumps because that data means very little. Did Eshtek intend that to be their target audience? Probably not but they should actually be excited that group seems interested. That's group will be the most loyal if you treat them right and are the best beta testers because you can't predict the messes they can get into. I think we need to understand this experience is going to be the norm for HexOS. As I said above, if you want something from HexOS then say it. And since money will always be the main driver, if Eshtek can monetize it they may look at it for the future. However if you think this level of communication is not enough, you saw that from the beginning. The team didn't go radio silent in the last few months. This has been the norm. If your issue is now that they can't estimate a project like this one well ok. They may even agree but before you do that you should find another project with this kind of hype because of an outside force. What kind of attention you think we deserve for $99 might be an interesting discussion. If there is a mathematical formula I have probably used my time up a few times over. I'm pulling back from HexOS and the forums but if you want to continue pointing out the shortcomings like missed deadlines and lack of meaningful communication, be my guest. Just show a little respect and don't act like its something new. Everyone who reads the forums already knows and it must not matter to most folks. And thinking you can guilt the team into more meaningful communication or more timely updates you are just being silly. If you care about HexOS then join the test groups when they have them and try different things that may not be what you will use it for. If you no longer really care then step back and let others play. Don't completely disconnect though because if you miss updates you may be screwed and have to start over. Linus or Jake, if you are in these forums and are reading along, please keep your mouth shut and let HexOS stand on its own two feet!

I can say ALL of my NAS builds have been done with Used drives from ebay and other retailers. I have had a small batch os issues but were dealing with drives that had a LARGE amount of time on them. if you are expanding and want to keep price down used could be a great alternative for you

I am a purple and gold guy

I got this working by doing a manual install of the docker compose file found here: https://docs.coolercontrol.org/installation/docker.html To manually install it, in TrueNAS go to Apps, Discover Apps, then click the three dots in the top right corner and load Yaml. You can leave the compose as is and it will work. You need to follow the guide below to setup the hardware for it. Specifically for TrueNAS that is running this command in shell and following the prompts: sudo sensors-detect To setup everything prior to that follow the guide here: https://docs.coolercontrol.org/hardware-support.html

The nuance I see is: Guesstimate for initial release, end of 2025. Oh shit, people want a local UI? Guess that's fair but that's a tone of extra work... but here's hoping... (I like many assumed the local UI was a part of the original plan) End of 2025: So it turns out the local UI was a tone of extra work, but we have a better guesstimate, Q1 2026. 1 Week before the end of Q1: Ok beta-beta release, If this goes flawlessly we might just make it... End of Q1: So transitioning X all at once is a massive migration that you can't really test for that well, so we'll have to do it gradually so we can cater for the inevitable fallout. Maybe we can do that over a month? Obviously I'm completely guessing (see, lack of communication) and could be completely wrong, but the general rule I've seen is go off the magnitude of the guesstimate, the longer the period the less accurate it is.

So just to be clear... The initial deadline (end of 2025) got delayed. The self imposed new deadline (Q1 2026) got delayed. The blog post about the delay got delayed (and still not out). The extent of the communication in the meantime on they delay is a random comment buried in a random forum thread. Radio silence on the official comms (reddit, twitter, newsletter). Hard to see how that could be considered acceptable / consistent / reliable. What's the level of goodwill here to assure that even end of April release will be met? The track record so far now is the opposite - the self imposed deadline means nothing.

Yeah they work for a display card. I have a 1080 in mine and its fine. Immich seems to be able to use it for some things. 🤷

Don't get me wrong, the communication is at what i would call a minimum, any less and I'd guess it was abandoned. But, it's a consistent and reliable minimum so far. I check the forum every other day, so would i appreciate more details, definitely. But would i trade anything for that outcome, probably not. So with the minimum communication and knowledge of the software development process patterns, I'm content enough. But that's not an expectation for others I have either. If you'd trade a license for that outcome and the team decide that they should improve communication because of it, hey, that's good too,

The people saying everything is fine have got to be software developers who see this only from one perspective. Hate to break it to them, most people we'd expect soon to pay full license fee to keep the project going aren't, and those are exactly the potential customers we'd lose with this laid back mindset to weak areas of this project. Those won't be beta expectations anymore and there will be a lot to prove to doubters of this project to justify the price. Imho plex & immich was genuinely exciting to watch grow naturally, and backing them early felt like a bargain especially towards stable launch. Was it perfect? No, there were delays too. But none I recall having such communication meltdowns close to stable release. I'll be honest, some of the responses here concern me as much as the delays and comm issues themselves. Some say I knew it's part of the process "when I read Q1 2026 I think Q3 2026" maybe, but not this far into this beta with no updated written delay comms. Others react confused when I try to hold the team to their own deadlines. 'I'm glad they're not communicating, that means time is much better spent on making the software...' really? Good teams do both and I'm not asking for daily extensive blog posts of what and why went wrong, just a sentence update across all hexos communication channels setting new expectations. I recall people on this very forum calling out poor communication back in July and October, and the team acknowledging it and promising to improve. Yet here we are. Traveling or not, I still don't understand how the whole team forgot the most anticipated day of their own project, or couldn't break the news of a delay at least the night before. Now whether April Fools or not, yesterday would've been the first day after stable launch with customers paying $300 for a license, needless to say the most expensive nas os on the market. At this point, if the team still offers a refund option, I'd happily take it.. this just isn't for me anymore