All Activity

Have sent in a request for VM testing :), have a lab ready for just playing around. Thinking about setting up a MECM lab using Hexos. Have been using **raid so far. but i like the way Hexos looks and feels more, it is the only reason i bought 2 licenses for Hexos. If the system breaks does not matter, have this lab setup just for VM tinkering. Been waiting since first beta of Hexos for this posibility. So look forward for the posibility for testing.

Ok

fixed the link, didn't realize they are set to automatically expire in 30 days. this one shouldn't do that

@Mobius The discord invite link has expired.

Doublechecking the documentation for 'sure' these values are supposed to be auto generated when you need them. have you tried going through with connecting to your financial institution?

Hi everyone, I'm trying to set up Sure (self-hosted) and I'm getting the error below about missing encryption keys screenshot attached. Could anyone help me figure out how to configure this properly? Also, is there a way to force the app to run over HTTPS, similar to how Actual Budget does it? Thanks a lot in advance!

@squijello Do you still have that notification? It should have been corrected.

Second this request

@mill3000 can you investigate this further?

https://docs.hexos.com/blog/2026-09-09 Buddy Backup is now in beta: back up your HexOS server to a friend's, fully encrypted, with no monthly cloud storage bills. Learn how it works, what your buddy can (and can't) see, and how to join the rollout.

sure is an app that uses postgres you might have to delete the sure dataset in /(HDDs or SSDs)/Applications/sure and then try reinstalling

This should have been in the update that went out a day or so ago.

Can't wait to test out the buddy backup. I've already filled out the form and I'm setting up my second HexOS Server tomorrow. Hope I get in. Keep up the great work. 😉

Trying to install Sure but it keeps erroring out. is this a common thing or a me issue?

In short Buddy Backups and Virtual Machines are beginning to roll out to test users now. The file browser and app cards are both getting deeper integrations with apps. All of this makes up HexOS 1.1, which ships on Black Friday this year (Nov 27, 2026). The $199 early access sale ends December 1, when standard pricing of $299 per server takes effect. Verbose details inside and another two blogs are slated for this week to go deeper into Buddy Backups and VMs. Beta signup: https://docs.google.com/forms/d/18XKSC5U0DPcaJL0RxrqRKqLl-mr7aS1WkTR9eftxOZw/viewform

Is this a NFS only dataset or a dataset without sharing option? If so, Hexos only shows datasets also supporting SMB. If it's a NFS only dataset can you try adding SMB to see if it's now visible in HexOS? Because I see every SMB dataset in Hexos but the NFS only not and I created all my datasets in Truenas :)

I’d like to see HexOS support adopting an existing TrueNAS dataset as a HexOS Folder without recreating, moving, or otherwise modifying the dataset. I recently ran into a practical example of this. I created an encrypted backup dataset directly in TrueNAS: HDDs/Backups I did this because I needed TrueNAS key-based dataset encryption so the dataset can remain available for unattended scheduled backups. HexOS’s current encrypted Folder workflow uses a password/passphrase, which was not appropriate for this use case. The dataset works perfectly and appears normally in TrueNAS, but it does not appear in the HexOS Folders section because it was created outside HexOS. It would be useful if HexOS could offer something like: “Adopt Existing Dataset as Folder” Ideally this would register an existing dataset with HexOS without changing: - Dataset path - Existing data - Encryption configuration - ACLs / ownership - ZFS properties - Existing shares - Quotas For settings HexOS cannot safely manage, I think it would be completely reasonable to expose them as read-only or mark the Folder as something like: “TrueNAS-managed” For example, my Backups dataset could appear in HexOS as: Backups Encrypted • TrueNAS-managed HexOS would not need to take control of the encryption key or convert the dataset to HexOS’s encryption model. It would simply recognize the existing dataset and make it visible within the normal HexOS interface. I think this would also be useful for people migrating existing TrueNAS systems into HexOS, or anyone who occasionally needs to use the TrueNAS UI for functionality HexOS does not yet expose. The main goal would be interoperability rather than having two separate views of the same storage depending on where the dataset was originally created.

Closing this thread as we are now LIVE with Community Translations via https://translate.hexos.com

We put out an update recently that should have addressed this. Please let us know if you are still seeing the "attention needed" on your server.

We are looking into it and hopefully we can get this fixed in the next week or two for everyone. Thanks for taking the time to write us!

Thanks for the bug report, I will forward it to the team.

Native Spanish and Galician

Repro steps: install app from catalog during setup rename app name i.e postgres-<VALUE> Navigate to hexos dashboard expected result: App name in hexos reflects the new name i.e postgres-<VALUE> Actual result: App name in hexos does not reflect the new name i.e postgres-<VALUE> it just shows postgres Note: This is working as expected with custom apps, this behavior is only being observed when installing apps from catalog.

You're welcome

For sure haha have to think about that, thanks for the information Gonna see if I can find anything about that Thank you so much for your help 🙂