Leaderboard

Pushing out a small patch today. This release addresses issues with app installations and includes updates to the forums. Bug Fixes App Installation Fixed issue with long running app installs - App installations that took longer than 2 minutes were incorrectly marked as failed, even when they completed successfully. The timeout handling has been improved to properly handle longer running app installs. Forums Along with these small bug fixes, you may notice a few changes around the hub. We’ve added new sections for each curated app supported by HexOS. This update will help us stay organized and respond more efficiently to issues related to app curation. It also makes it easier for us to share announcements, provide updates on ongoing bugs, and post solutions as they become available. Immich Following our recent Q3 update, you may have noticed some issues with Immich. We’re aware of what users are experiencing and are preparing a guide to help address these problems, which should be available soon.

Appreciate the criticism and we take it in stride. I respect everything you and others post, both good and bad. Sometimes raw emotional responses can cause gut check reactions of "you're kicking my baby" but I don't let myself see it that way. You're obviously passionate about our project or you wouldn't be here pointing out all the ways in which we can do better. I also respect not wanting a refund and I look forward to the day when I see a post from you saying, "ok, this was totally worth it and I'm glad I bought." 💯 Agreed. Our CTO has a proposal for us this quarter to do exactly what you're talking about. It's premature to share but know that we are on the same page and intend to do this. We intentionally built the global HexOS messaging system for this back with the Q2 release. We now want to expand that to include notifications for app-specific issues like this. But keep in mind that was not the original plan for 1.0 so the scope is no increasing, which is fine, but we still have other projects and objectives to hit, one of which is the Local UI which is a much bigger project than I think anyone realizes. It's complicated by the fact that our actual footprint on the ISO today is very small and we do not want to bake any of our UI into that ISO either. Instead, we have to build a full container/app for this which we are doing, but it's a huge project and we have a senior dev completely focused on it right now. I feel like a broken record saying this, but a big part of our struggles this year is bootstrapping the business. Money doesn't solve everything, but it sure as heck would have helped to hire a lot more developers and app specialists right at the beginning of this year, but we opted for a more fiscally conservative approach to hiring to ensure we don't grow too big too fast and make commitments to employees we can't keep without proving our business model first. Expansion is a big part of our plans for 2026 and will help us get more focused on individual layers of the software. Sure, but that comes with its own set of challenges and problems. Again, everything is still in flux and user data is not at risk. The worst anyone should have to deal with is reconfiguring immich from scratch which of course isn't ideal, but let's be honest here, it's also not the end of the world or an unrealistic expectation given the beta nature of both us and Immich itself. Comms of course could be better, always. But we are doing the best we can with what we have for now and we would just ask people to be patient while we work through it. This was all part and parcel of participating in the beta and if that's not going to work for anyone, waiting to deploy until more polish is applied would be the right approach. I've already spent hours reading and replying here and the more we try to get ahead on comms, the less time we spend on building and getting to a release. Every hour is a choice and often there are no options that will satisfy everyone. Still totally understand the frustrations, but this is the last I'll be commenting on this today so I can get back to work with the rest of the team. Our new docs site is a great place for us to put a guide for immich issues and resolving them in the future. Stay tuned for more, but know that we don't have the ability to always drop everything we are doing to shift focus to an issue like this when we are in the middle of other projects. There can be a lag time and that is something everyone here will have to accept while participating in the beta. Again, if that doesn't work for anyone, wait for the polish to come before deploying.

Not affiliated with HexOS, but here's a quick analogy to explain what's actually going on behind the curtain for a layman. HexOS are assembling a car, which is being built on an existing Chassis (TrueNAS) that has over the past 12 months had some pretty significant structural changes. While the changes are good and will make the final car better, it means the development of the car is complicated because the way the seats bolt in, and the size of the windscreens are changing while they're assembling the car. HexOS said 'This car is still being built, you can use it, but if you need to drive for your job you should wait until HexOS is finished before selling your old car'. HexOS are in the process of upgrading the driving wheel, figuring out A\C, and putting in the car seats, which keeps them pretty busy. While the car drives, it's not really a production car just yet. The radio manufacturer decided to change the wiring requirements all of a sudden with the new model they released, so HexOS need to tweak the wiring so the radio keeps working. All of this is happening while thousands of people are driving the car, and asking when the A\C will work, or when the new seats will be available. You can fix it by taking the radio out and putting it back in yourself (re-installing Immich) Or you can wait until they have time to fix the wiring in the back-end, which they will do eventually. A car without a radio still drives. Again, this is a beta. Stuff will break, and until they reach 1.0, expecting everything to work 100% and non-critical issues to be fixed quickly is just a recipe to be disappointed.

We've discovered a handful of different issues with immich plaguing users. We are on the case and it's a priority issue for us!

Sept 29th or 30th the person who really administers my Unraid setup stopped over and we looked at HexOS. He said in his professional opinion, he could see what HexOS was trying to do but was surprised how much I needed to do in TrueNAS. To be clear, he says he has a functional knowledge in TrueNAS but is not an expert. I mentioned my security issues because I didn't think any apps but the ones I forced to use a certificate of any kind. We he asked for an example I chose Nextcloud. He timed how log in to to start the stopped app, how long it took to launch the app, and a couple of the addons. He mentioned the launch was slow especially since I logged in as me, not administrator. He questioned my Microsoft Office and the Talk app as they could slow things down. After removing those addons we did it again from server bootup and it wasn't any faster. He looked at cpu and memory numbers and said it was way more this server should need or use. I showed him that I had increased the CPU count and available memory Thinking that would help but not really. His general assessment was it was very slow for only two users and no internet intensive addons because copying/moving files was lightning fast. After a few more app demos he said I was right in worrying about security and when HexOS was live I need to secure every app to HTTPS at a minimum if I intended to continue running this NAS. But he also said the apps that were slowest were the ones I installed myself from TrueNAS so if HexOS gets a curated version it may noticeably improve performance. As an example he gave me what the company he was currently working with (that I retired from) launch and addon startup numbers were. They wouldn't accept an app that didn't start in half the time and while that is a full production tuned app, it has +200,000 users in the USA and another +50,000 worldwide.

I can't claim to be a layman in this, given I'm now nearing 30 years as a professional developer. I am, very intentionally, approaching this from a "regular customer" point of view, instead of as someone who is comfortable with a command line. That used to be what beta meant; feature complete but lacking content and polish. Then everyone started releasing alphas and calling them beta. At this point I suppose I'm quickly becoming the unreasonable one in having any expectations whatsoever of a beta, given there's a generation of developers now that have never known a beta to be anything but "some random stage between first successful compilation and full release". I hold you at no fault at all for the unfortunate timing of the Immich 2.0 release. It's the lack of communication and/or action for the months after the deprecation warning appeared, I'm expressing disappointment in and suggesting you need to reconsider your approach to. It's not the first time. A similar laid back attitude was present when all updates broke due to a TrueNAS update being required, that no one knew if was safe to perform or not. I think everyone would benefit greatly from a more proactive approach. My main point is that you have an ideal information channel to reach your customers: the HexOS interface. If an app is broken, make it show there. If manual action is needed, let the users know there. If there was no mechanism for doing that early on, perfectly understandable. But it should have become apparent long ago now that the information flow has not been working all that well. It does not seem unfair to say that it's not good form to leave an app broken for months without any indication in the interface that lists is as a recommended app. This should not be a thing nearly a year into selling the product, beta or otherwise. This is very much intended as criticism of the constructive kind. I just want to see improvements. That you are responding to this kind of criticism in a positive manner, is great. But, I haven't seen much customer-facing change over the months, which I find worrisome and I genuinely feel you (as a company) should as well. As for a refund, I appreciate the offer but it's not enough money to be worth an evening or more worth of hassle in reinstalling "just TrueNAS". I reserve the right to continue to be grumpy and disillusioned, but hopefully I'm succeeding in limiting my sharing to an endurable level. 🙂

😞 I totally get this disappointment. I don't even blame you. We are targeting a more casual user and I can see how users like yourself may have had a higher expectation closer to that of a video game beta, where it's really software that's functionally complete, but just testing integrity of the infrastructure for multiplayer and game balance. You might find a bug or two, but nothing too crazy because part of the purpose of the beta is to build hype for the game prior to release, as we just saw with Battlefield 6 Open Beta. All of that said, we did say this was beta and listed out all the risks in the very first post you read to get it downloaded and installed. Furthermore, we actually had a second fix in for th migration issue for Q3 but due to another immich update, it broke again literally the day before the Q3 release and we missed it because QA was the week prior. This was just a very unfortunate coincidence. It seems like you specifically may be very frustrated with us and not happy with your experience. If you would like, I will refund your purchase. We don't want anyone feeling raw about their transaction, so if you want to take me up on that, feel free to drop me a DM. We are a small but growing team and will speak to our plans to get even better about this for post 1.0. We will be building an Apps team that will be responsible for ensuring our curations remain solid and that we handle these types of issues better. This analogy was spot on. Appreciate you taking the time to lay that all out.

My Immich was warning about the deprecated storage configuration before then, and it still is now. I've seen no new notice of migration needs since then. That was always the issue, it's not a new one. There was a separate issue with people who did not attempt to update for a long time after HexOS launched, and were then unable to do so. Is that what you are referring to? I get that Immich was beta, and that HexOS is still beta. But you charge money for HexOS and Immich was supposed to be one out of a whopping two applications you claimed to offer some level of support for. I didn't have expectations of extreme levels of support, but I did expect _something_ in a timeline less than several months. But, as far as I've seen over the months, absolutely nothing was done. The only thing that's happened since that post, for me, is that after months of warning about the forthcoming deprecation, it was finally implemented and Immich will no longer update. Over those months there have been a number of posts by people with issues both installing and updating Immich, with no indication anything had changed. No responses of "we fixed this, here's how to implement it," as far as I've spotted. Was the Q3 update even supposed to support automated migration to the new storage structure? Or are you saying you implemented something prior to Q3? How? HexOS did not support app updates before then. Was something supposed to have been deployed silently? If a solution that required an action from me was implemented, why did not HexOS notify me of this over these months? Did I miss a bunch of forum posts? The only solutions I've seen have been community posts working through how to implement the manual migration tasks as indicated in the deprecation notice. I really have no idea what you attempted to do, or how to even have noticed it didn't work. And I have no idea what you have tried to do now with the Q3 update. All I know is that there's now an update button in HexOS, that appears to do exactly the same thing triggering an update in TrueNAS does, except HexOS takes hours to realize it has failed whereas TrueNAS reports it in a second or two. So, from where I'm sitting, nothing was done and what you're now saying, after months of silence, seems to be "this is news to us." I hope you can excuse my less than enthusiastic response to that, as misinformed as I might be.

25.10 is expected to go from Beta to General Release this month so that's good news.

im not 100% about rolling back but if you do upgrade to fangtooth make sure you don't upgrade zfs pool flags in the truenas ui if you do, you definitely can no longer roll back and still use the same storage pools

Having AMP (https://cubecoders.com/AMP) supported would allow users to get game servers up and running super fast and easy! I know my primary use cases for hexos is media streaming, image backups, and gaming servers. The first two are already covered with plex and immich. Just need a game server app for hexos and therefore recommend AMP!

Saw your post and I’ll add this to the list for us to curate. Seems like a good one!!