Leaderboard

Another month, huh? The least you could do is respect the people waiting with some communication ahead of time. Instead it's silence all day on release day and a last-minute delay notice as if it wasn't clear days ago this could happen. You created this self-imposed deadline,, nobody forced it. A delay with advance communication - fine. But the silence until 9 PM? That's just pure disrespect

This one is entirely on me. I am traveling today but I will be working on getting this blog post up tomorrow (April 2nd). I'm also planning to hire someone to take over marketing/comms this year as a full time position.

The teams working as hard as they possibly could on this and when participating in a beta delays, bugs and broken updates are to be expected. Personally I would prefer delays over broken updates.

1.0 should be out today. When will it be pushed out?

Working on a blog post with an update. We had to push back to April due to some issues with our health system that we've been tracking down since February. The plan is to both begin the rollout of HexOS Local and complete the health system upgrades and then release 1.0 by end of April. I was hoping to get a blog up today with all of this information, but it just didn't come together fast enough.

I messaged the user. Thanks for the shoutout!

@jonp @mill3000

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,

According to this picture found at https://nascompares.com/2024/10/04/jonsbo-n5-review/ , it seems like he has added the 4 SATA cables and 1 SATA Power cable to the board, no MOLEX. My best bet is that you can either use MOLEX or SATA Power, but don't need both.

"Working on a blog post with an update. We had to push back to April due to some issues with our health system that we've been tracking down since February. The plan is to both begin the rollout of HexOS Local and complete the health system upgrades and then release 1.0 by end of April. I was hoping to get a blog up today with all of this information, but it just didn't come together fast enough." -JonP "I am traveling today but I will be working on getting this blog post up tomorrow (April 2nd). I'm also planning to hire someone to take over marketing/comms this year as a full time position." -Jonp Link to discussion

Wow, Communication is a headache? That's a laugh. Well it looks like you have come to the right place. You only get very filtered communication when things are going really good here. And for anyone who actually was a developer you already know communication is critical. A lack of communication leaves you with a forum like this. Dozens of questions that get ignored. When did communication and coding become mutually exclusive? Right now the only people talking positive about HexOS are a few folks that depend on this product for their livelihood. Fortunately most people seem to not care or never took anything said up to this that serious. And looking at how many issues there still are unanswered in the forums and the length some of those have been around. Some issues have been able to celebrate birthdays. And if you want something to think about, riddle me this. If communication is like this now when we are in "BETA" and there is still goodwill stemming all the way back to the LTT video, What will it be like when we have HexOS 1.* and the product is release to production. Do you think the communication will get better then? The entire team has made it easy to get down on this product/project but if your going to be honest with yourself you still see the possibilities that attracted you in the first place. If you love the product and you are honest with yourself you see the cracks and holes that give you an uneasy feeling. Everyone in the middle is pretty meh in that it will do what they need but maybe not what they want. And just off on the horizon is the real issue we have been dancing around. A perfect HexOS is still just a skin wrapped around parts of TrueNAS. It will never be more than that and no matter how hard you look you were never promised more than that. If you don't want to learn TrueNAS then welcome to a sturdy and easy to setup network attached storage appliance. As Immich has shown us multiple times, the application curation process was just to make the initial install easier and more standardized. It is not to make Immich work or eliminate code product issues and design changes. What kind of communication do you expect when a new release of an app or perhaps TrueNAS itself wants to change something fundamental like their storage or security models. And from who? It's probably time we stop worrying about when production version 1.0 is coming and start trying to figure out what we are willing to do to make it work. Learn TrueNAS? Buy new hardware? Buy consulting services? Cut your losses and find something else? Regardless of all the rest , it seems you can't count on communication or timelines here. If you can't live with that no matter what you thought in your mind this journey would be, well sorry because this is just the start.

We are extremely close to releasing HexOS Local, our solution for accessing/managing your HexOS servers through a locally installed application on your server. Before we roll this out to all current users, we are looking for a handful that are able/willing to help us test the migration process. The requirements are pretty simple: 1) Users that agree to enroll in this early access test will have ALL of their servers migrated (we cannot apply the test to just a single server, so if you have multiple, it's all or nothing). 2) Users must have a discord account as those accepted will be invited to our new discord server for the purposes of bug reporting and support needs. If you are interested in helping us test this, please drop a DM to @mill3000 with the subject "HexOS Local Early Access" and be sure to include your Discord username in the message. Any questions, post them here! Thanks everyone!!

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

Well @vogam7did you get what you wanted? If you have read these forums there are more than enough accusations of terrible or completely lacking communication. I have been jousting with this windmill since shortly after the initial deployment. I've even talked about to many methods of communication that left each incomplete. I got a similar response it would be looked into. and I can say this was the only answer you could have expected. They are probably still a small team primarily of coders. There had been talk months ago of no marketing team, no support team, and only initial talks of ongoing funding. If we are thinking this communication level is the biggest issue we are going to face before this project stabilizes, we are seriously kidding ourselves. That LTT video is more of a curse than blessing because this project isn't ready for that kind of attention. This team isn't going to acknowledge they are having trouble. They just won't say anything, again. And there is nothing any of the paying beta customers can do about it. Watch and wait or don't watch, what's the difference now. It's to late to change the approach the team took, even if they have found that. And there is now reason to assume that's true. Did they take the right path to this development? Did they build the right team with the right leadership? Well, if you have a better plan then share it. If you don't like this approach how would you fix it? Communication alone means very little. Missing deadlines is a much bigger deal that not mentioning there are problems. And honestly, do you think this would be simple and smooth? Yeah right.

You aren't able to add Gluetun to a HexOS app, or a regular TrueNAS app. You have to either install the Dockge app in TrueNAS and then install the Arr apps through Dockge. Or you have to install them as a custom app in TrueNAS. I do hope HexOS will get a good way of routing app networking through a VPN, but I expect it won't happen soon. @Isaac7ski

Hey, yes unfortunately this seems to be normal for BX APC UPS. Those UPS are not the best ones and the driver does not work very well with them. The problem seems to be that the USB part of the UPS keeps disconnecting and reconnecting every couple of seconds leading to this messages. It's a known problem. My advice would be, if you can still return it, do so and try looking for an Eaton UPS or similar. https://forums.truenas.com/t/back-ups-bx1600m-false-battery-replacement-alerts/50688

from you screenshot it looks like you only have 3 of the 4 harddrives that the pool consists of installed into the system.

First, a huge thank you to @lnkd for posting the actual steps to do this. All I did was follow everything they said and take pictures, so really all credit goes to them. Original post here: Prepare TrueNAS for reinstall: 1. Login to TrueNAS web interface – go to deck.hexos.com and click Settings: Then click the TrueNAS icon: 2. Once logged into TrueNAS, go to System > General Settings > Manage Configuration > Download File: 3. Read the note presented when you click Download File: 4. Click Save: 5. If you have encrypted datasets, go to Datasets > select the encrypted dataset > Export Key: 6. Now it is time to shutdown the server. In the top right of the TrueNAS web UI click the power icon and click shutdown: 7. Make your changes to the hardware that you would like – for me I added a 10 GB network card to run off fiber. 8. Prepare the HexOS installation drive by following these steps: https://hub.hexos.com/topic/103-illustrated-installation-guide-start-here/ 9. In your router settings, give the new hardware the same IP as your old one, then restart TrueNAS to grab the correct IP. 10. Once rebooted you can confirm on the server the IP address is correct: 11. Login to the TrueNAS web interface with the username and password you set during install (username should be truenas_admin). 12. Confirm your version on the dashboard – if needed, apply the update to the server: a. To confirm what version you need check the filename of the .tar file you downloaded from your configuration. It will have the version number on the end of it. b. Select the same version from the upgrade screen and confirm you want to switch to that upgrade train. c. Apply the pending updates and the system will reboot. 13. Go to Storage > Import Pool > find your zpool: 14. I have two pools so I will import them both. 15. Go into System > General Settings > Manage Configuration > Upload file: 16. The server will reboot after the configuration is applied. Log back into the TrueNAS server once the reboot is finalized. 17. If, like me, you replaced the network cards you will need to login directly to the server and adjust the IP settings: 18. Setup your new interface with the primary IP in CIDR notation, then you can log back into the TrueNAS server. 19. To setup apps, you need to go to Apps > Configuration > Unset Pool: 20. Restart your TrueNAS server then go back into Apps > Configuration > Choose Pool: 21. Once the pool is set you will see your apps again and be able to start them. 22. Navigate to the HexOS Interface (http://deck.hexos.com), unclaim your old server and claim your new one: 23. I ran into an issue where no matter what password I input it would not take it: 24. Currently troubleshooting that to be able to claim my HexOS server in the deck. All of my apps and storage are up and running so I will report back here when I fix this issue.

This was a while ago so I am unsure. I do not remember having to reset any permissions on the datasets I had though. I'm waiting on a secondary Dell server to come in and am going to spin up my test HexOS machine again, so I can let you know on that one once I get all that setup.

Yeah, I’m pretty keen to see this as an app or container. Crosstalk stated they’ll look at those features once all the main stuff is sorted out

Dentro de la interfas de truenas, debes seleccionar la seccion de aplicaciones en la columna izquierda, dentro de la interfas de aplicaciones puedes ver todas las aplicaciones qie tienes instaladas, seleccionas la de imich y sale listado el puerto dentro de "workloads" o incluso puedes hacerle clic al boton "web ui", espero que te sirva!

@G-M0N3Y-2503I think we are going to have to agree to disagree, not for any points either of us brought up. But rather because nothing said here is going to make any difference. I guess we will have to wait and see what long term effect very little communication has, if any.

With the newest deck update that happened today, I'm guessing the actual big update is coming soon since today's deck update referenced prepping it for the update. 🤷‍♂️

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?

I will be having family use my server for backing stuff up and as we all know end users always end up accidently deleting things and then wanting them back. Luckily, TrueNAS has a recycle bin option and hopefully HexOS can add it in one day as a setting that can just be turned on. For anyone who finds this and wants to do it, here are the steps: Set up the folder in the HexOS UI and then in the TrueNAS UI go to: Shares > Click edit on the SMB you want to add the recycle bin too > Purpose = No Presets > Click Advanced Options > Scroll to Other Options > Check Export Recycle Bin Then you will want to set up a job to automatically empty your recycle bin: Navigate to Chron Jobs in the TrueNas UI (just search for it but it's under System > Advanced Settings). Click add then you can either enter this into the command field as ONE LINE or save it to a file find /mnt/HDDs/FOLDER/.recycle/* -atime +30 -delete; find /mnt/HDDs/FOLDER/.recycle/* -depth -type d -empty -delete; If you want to test to see what files will be deleted with this command run it without the "-delete" If you save it to a file (like I did) you will enter this as the command. sh /mnt/HDDs/PATH_TO_FILE/empty_recycle_bin.sh Then just fill out the description, run as truenas_admin, and how often you want it to run and you are good to go. Hope this helps and hopefully it can just be a 1 click type of setup in the future!! P.S. Here is what the commands do: The first command searches for files and directories in /mnt/HDDs/FOLDER/.recycle/ that have not been accessed in the last 30 days and deletes them. The second command searches for empty directories in /mnt/HDDs/FOLDER/.recycle/ and deletes them. Also commands were stolen from here