Leaderboard

Sorry if this has been mentioned already. There needs to be a way to store a boot disk config or recovery file on one of the arrays to allow easy recover of a dead boot drive (all done within HexOS! I shouldn't have to go into truenas if I don't know what I'm doing). I did install on redundant boot drives but bought too cheap and they both failed simultaneously. The only way I could find to recover was a fresh install without the array drives connected, then plug them in and manually recreate the exact share folder names in the HexOS from the list in truenas. Also, I would love to see a way to transfer or transition the boot drive to another drive by simply connecting a new drive. That way if all you had for a boot drive was a 1 Tb but wanted to use that for something else later you could get a smaller drive and transition.

I can confirm that if you do a fresh install you can set up the folders again and have access to all data, but you need to do things in a specific order and with the array disks unplugged (if you try to set up a new array through HexOS interface it will wipe the drives). If you know all your folders now you won't need to go into into truenas. I really think there needs to be a recovery feature in case of boot drive failure. Here's a link to a thread with good instructions on how to recover, but it would work to "downgrade" as well, though kinda janky. I would assume cloning would work as well but haven't tried it. https://hub.hexos.com/topic/3227-restoring-hexos-from-a-dead-boot-drive/

The reason Tailscale gets recommended so often is because it (and VPNs in general) is the most secure ways to access your services remotely. It's also pretty easy to install and get running. Nginx, on the other hand, is a completely different approach. To make lives a bit easier, let's take Nginx Proxy Manager instead of plain Nginx. Installing it is the easy part. The real work starts afterwards. You’ll usually need a domain, set up a DNS token for the certificate DNS challenge, configure something to keep your public IP updated, and create and manage all your subdomains. And all of that just to make your services reachable from outside your network. Once you’ve done that, your services are basically exposed to the entire internet. That means any device online can try to reach them. Because of that, you also need to put additional security measures in place to protect them from people trying to access or exploit them. Therefore only expose what you absolutely need to expose.