Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. If you installed our curation of jellyfin the self healing function of HexOS may be bringing back those datasets. They are not created until you create them manually or install a curated app that uses those datasets it is not currently possible
  3. Today
  4. There is a built-in file browser in the deck already so that you can already now access your files from everywhere. Concerning remote access to the apps, this has already been requested on multiple occasions and it's currently being analysed IIRC
  5. Hi, Is there any feature of remote access planned for the future ? Not remote management but remote access to files (ala ZimaOS https://www.zimaspace.com/docs/zimaos/remote-access) or even access to application like jellyfin (a remote dashboard would be awesome). The goal would be to simplify remote access by removing all the tailscale, wireguard, port forwarding shenanigans that can be overwhelming for non experienced users (like me) to setup. Of course to be more privacy friendly I'm talking about something that would be direct between the user and their hexos home server. I don't think that all the photo backup / sync tool suite that Zima offer is necessary as apps (like immich) exist for that but I think that setting the remote access is a major point of friction that prevent less technical users from using them, and pushes them toward systems that offer those suites like Synology or Zima. Even with all my love for the Hexos project I know that i could not recommend it to my parent for exemple without remote access build in. Even though they have been using a NAS for years now. (a WD one).
  6. I have attempted it on the N5 Air but I had a bit of bad luck with my unit. I'll be trying again on the replacement unit.
  7. One additional thought: could this behaviour be related to HexOS's curated Jellyfin installation? I originally installed Jellyfin through HexOS, which I understand automatically preconfigures media libraries and storage locations. We subsequently removed the unused Media and Videos locations from Jellyfin itself. Could HexOS still consider those folders required by the Jellyfin curation and recreate them during its application-management or upgrade process, even though Jellyfin no longer uses them? Or does HexOS recreate any missing folders assigned under Settings → Default Locations, regardless of whether an application actually requires them? I'm trying to understand whether this is an application-specific dependency or a broader default-folder provisioning behaviour.
  8. Thanks for the suggestion. I found the Default Locations settings, and I can see that Media and Videos are both assigned to their respective datasets. What I'm trying to understand is what purpose these two default folders actually serve. HexOS already has separate Movies, Shows and Music folders, which I'm using, and none of my applications appear to reference Media or Videos. I also noticed that Documents and Downloads are listed as "Not Created." Why can't Media and Videos be configured the same way? If I change their default locations and delete the existing folders, wouldn't HexOS simply recreate them at the new destinations during the next upgrade? Ideally, I'd like to disable default folders that aren't needed rather than relocate them. Is that currently possible, or are Media and Videos required for some underlying HexOS functionality?
  9. Yesterday
  10. Can you check your settings > default locations try setting your default locations to somewhere else and then delete the ones you don't use
  11. I've encountered an issue where the default Media and Videos folders keep recreating themselves after being deleted through HexOS Command Deck. I originally removed both folders because they were empty and unnecessary for my setup. However, they reappeared the following day, complete with ZFS datasets (HDDs/Media and HDDs/Videos), permissions, and enabled SMB shares. I investigated the recreation using TrueNAS middleware audit logs. On October 20, 2026, at approximately 4:30 PM, both datasets were recreated through authenticated API calls. The operations included pool.dataset.create, pool.dataset.update, filesystem.setacl, and sharing.smb.create. Interestingly, these operations occurred within the same authenticated session that subsequently initiated upgrades for several applications, including Jellyfin, Immich, OpenCloud, Vaultwarden, and HexOS. I also verified that neither dataset is mounted by any Docker container, referenced in the inspected TrueNAS application configurations, or associated with any ZFS snapshots. Both folders were empty. I've now removed them again through HexOS, but I'm concerned they'll simply reappear during another application upgrade. Is HexOS intentionally recreating default folders during application updates or maintenance? If so, is there a way to permanently disable this behaviour for folders that aren't needed? If this isn't expected behaviour, could the team investigate whether folder deletions are being properly persisted? Happy to provide the relevant audit logs if useful.
  12. Last week
  13. Please add the iso date format as an option YYYY-MM-DD. I was so excited when I saw there were date options and then so disappointed it did not include the subjectively objectively best date format. Details can be found here: https://en.wikipedia.org/wiki/ISO_8601 Thanks
  14. We no longer share the Applications folder on SMB by default. I will float the idea of setting new system shares as private by default with the team.
  15. Hi everyone, I hope I didn't just misconfigure anything, but: Problem: On my HexOS, all folders/shares for Applications, Movies, other Media, and so on, were fully available to any anonymous user on my network. As a lot of the applications are meant to work with and store personal data, this is, for me, a security nightmare. It undermines any login or security measure configured in the app itself. In one of the recent updates, there was also a new folder introduced, which is again public, but worse, I can't modify it in the command deck. Suggested solution: By default, only allow the initially created user to access all the standard folders/shares and encourage the user to create new folders with access restrictions by default. I've already set all Manageable folders/shares to be private and all my apps seem to still work. Greetings funky33
  16. Earlier
  17. Just been on the github and see someone else reported it about 3 weeks ago. Has anyone else here given it a try?
  18. Just tried ratelog seems good but cant seem to change the admin password
  19. Two Command Deck updates open Buddy Backups and Virtual Machines to every HexOS owner, add a guided server setup, and keep private folders out of sight. Everything applies automatically; you may need to clear your browser cache. Open betas, guided setup, and drive and memory testing for everyone **Buddy Backups (open beta).** Back up your folders to a second server you own or to a friend's server across the internet, end-to-end encrypted over a private network. No sign-up or waitlist. **Virtual Machines (open beta).** Run Windows, Linux or Home Assistant directly on your server. Share a graphics card between apps and VMs, even a server's only card: apps pause while a VM needs it and start again afterward. **Guided server setup.** One decision per screen. Pick Most space, Balanced or Most protection and HexOS plans your pools, shows how many drives can fail without losing data, and changes nothing until you confirm. Existing pools are found and kept automatically. **Your apps drive, protected.** If your apps run from a single drive, HexOS keeps a nightly copy on a protected pool and walks you through restoring your apps if that drive fails. **Drive Certification and Test memory.** Test any new or used drive and get a plain-language report. Memory testing no longer needs Expert mode. **Health & Capabilities.** See your system, storage, app and VM readiness in one place, with every warning explained. **File browser.** Right-click menu, drag and drop, and undo. [Read the release notes] https://docs.hexos.com/release-notes/command-deck/2026-10-09?utm_source=reddit&utm_medium=social&utm_campaign=release-2026-10-09 Private folders stay private, smarter Custom VMs **Private folders stay out of sight.** Anyone browsing your server in Finder or File Explorer now sees only the folders they can open, so guests no longer see the names of your private folders. Requires TrueNAS 25.10 or later. **Custom VMs start their own installer.** HexOS presses the boot key only when the installer asks for it, and recognizes Windows installers automatically. **Safer graphics card switching.** An AMD card moved away from VMs returns to your apps at the next restart, avoiding freezes some AMD cards cause. Apps already using a card keep it. **Backups from your server's own Command Deck.** The Backups page now works there, and backups can be stored on a pool whose name contains a space. **Each browser tab remembers its server** if you manage more than one. [Read the release notes] https://docs.hexos.com/release-notes/command-deck/2026-10-13?utm_source=reddit&utm_medium=social&utm_campaign=release-2026-10-13
      • 1
      • Like
  20. Thank you so much!
  21. I have two servers that will run hex os, one serving as a NAS and the other backing up that NAS using HexOS buddy backups. I would like to have the backup server powered off most of the time and periodically power up to fulfill buddy backup duties, then powering down upon completion. It is my understanding that something like this should be possible if the backup machine as Wake On Lan functionality in BIOS. If so, is this a feature that does exist/ can be implemented into buddy backups? I do see users discussing this functionality within truenas, it would be great to see it in the HexOS front end. https://www.truenas.com/community/threads/automatically-turn-on-and-shutdown.95459/
  22. Yeah we are just as eager for TrueNAS 27 as well. We will likely roll out support for it after they reach their first minor patch post launch. There are some goodies in there for us too!!
  23. I don't have a concrete date date I can provide at this time but it will be after the official release of truenas 27
  24. We will be expanding buddy backup to other operating systems too but It will come at a later date.
  25. currently, I'm running 3 gpus in my truenas box: Intel ARC Pro B70 (VM) Intel ARC Pro B60 (VM) Nvidia 2080 Super (Jellyfin transcoding) I've been experimenting running local LLMs, the nvidia card is just taking up space and not very useful for modern LLMs since it only has 8gb of RAM. TrueNAS SCALE 25.10 does not support any Intel ARC cards, due to an older kernel version. what I want to do is: Intel ARC Pro B70 (VM, local LLMs) Intel ARC Pro B70 (VM, local LLMs) Intel ARC Pro B60 (truenas, jellyfin transcoding) - requires trueNAS I assume I cannot do this today because truenas 25.10 needs a gpu and is not able to use intel gpu's. my CPU is a AMD Ryzen 5900X, so I don't have integrated graphics build in.
  26. Buddy Backup will be possible to a TrueNAS server in the future, but no news on any other OS so far.
  27. Will Buddy Backup allow backups to non-Hex servers? e.g. I would like to backup to a folder in Unraid.
  28. Hi tetra we aren't currently adding driver support directly through HexOS. We have the same driver support as TrueNAS scale. If TrueNAS scale adds support, we will also support it. You may want to request they add support.
  29. Currently other Hailo devices are supported but the 10H kernel module and firmware have not been added, these are supported by Frigate and would be really useful to have on hand.
  1. Load more activity
×
×
  • Create New...