Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 11/14/25 in Posts

  1. Let's Talk About Immich If you've been running Immich on HexOS this year, you know it hasn't been smooth sailing exactly. We want to talk about what's happened, why it was so challenging, and how we're working to handle these situations better in the future. What Happened? Earlier this year, Immich deprecated their old storage configuration and required all users to migrate to a new structure. For users running Immich through docker-compose or other manual setups, this meant updating some configuration files and running a few commands. Annoying, but manageable. For some HexOS users, the migration was more involved. Because of how TrueNAS SCALE structures application storage, moving to the new configuration required either reinstalling Immich fresh (the simplest solution) or manually migrating existing data between datasets (a process that involved SSH access, rsync commands, and careful attention to permissions). But if you're choosing between "reinstall the app" or "follow a 15-step guide," neither option feels great when you chose HexOS specifically to avoid that kind of complexity. Why Was This So Hard? When Immich made this change, we had a choice to make. We could have built a comprehensive rsync-based migration tool using the TrueNAS API. It has those capabilities. But that would have meant dropping everything else we were working on to build what amounts to using a cannon to kill a mosquito: a massive, complex solution for what we hope won't be a regularly recurring problem with this particular app. Instead, our community stepped up in a huge way. Users like @forsaken and @G-M0N3Y-2503 created detailed guides (to move or rsync your data). These guides walked through the manual migration process to preserve existing data in Immich. They focused on helping users through the immediate problem, while we continue building the platform we need to handle situations like this properly. That platform is HexOS Local: a locally-hosted management application that will let us perform complex operations without being bottlenecked by the engineering overhead of building one-off solutions through the SCALE API every time an application throws us a curveball. This reduces the technical burden on our team and, more importantly, gives us the flexibility to automate maintenance tasks that previously would have required manual intervention or massive engineering investments. This same platform will serve the Local UI/UX feature we've committed to delivering as part of our 1.0 release. We'll be talking a lot more about HexOS Local in an upcoming blog post, but the key takeaway is this: we're building HexOS to handle whatever the open-source ecosystem throws at it, without having to choose between "drop everything and build a custom tool" or "make users SSH into their servers." What About Right Now? If you're currently running Immich on the old storage configuration and haven't migrated yet, you have options: The simple path: Reinstall Immich fresh with the new configuration. Your photos will need to be re-uploaded, but the setup is clean and straightforward. The preservation path: Follow one of the community migration guides to keep your existing data in place. These guides are more technical and require command-line access, but they work. Our recommendation depends on your situation. If you have a manageable photo library and good backups, the fresh install is probably your best bet. If you have years of photos, carefully organized albums, and user configurations you don't want to recreate, the migration guides are there for you. And if this seems to daunting, email support@hexos.com so we can schedule a time to assist you directly. Moving Forward The Immich situation showed us exactly where we need to invest engineering effort. We can't keep facing the choice between building massive one-off solutions or asking users to break out the terminal. That's not sustainable, and it's not the HexOS we're building. Immich is an incredible project. It's exactly the kind of self-hosted solution we want to make accessible to everyone. The team behind it recently released v2.0, marking their stable release with better upgrade paths going forward. We're committed to making sure that when the next complex maintenance task comes up, whether it's Immich or any other application, we have the infrastructure in place to handle it gracefully. That's the HexOS we're building. Thanks for your patience while we get there.
    17 points
  2. Hello all! We are excited to announce HexOS Local, powering the new local UI/UX for HexOS and capable of so much more. Read more about it on the Blogpost - Introducing HexOS Local
    13 points
  3. Forgive me, but I'm really confused by what you're saying, which means there is clearly a disconnect in our marketing language and understanding with customers as well and I want to get to the bottom of that. Let's try some clarification here: Buddy backup is a feature that will allow two HexOS users (customers) to backup to each other's server in an encrypted fashion. There is no reason you cannot be your own buddy with a second license (e.g. you buy a second server license and put a server at a secondary location). If someone bought two licenses during black friday under two separate accounts, each account can backup to each other just the same (and if they want to merge those two accounts, we can handle that for the user). With this sale, however, we are not allowing someone to buy a second license to transfer to another user (as it would open the door to reselling licenses which we don't support). I get that the term "buddy backup" may not clearly identify that you can be your own buddy, but we thought it would be fairly obvious that if you could backup to someone else on a separate account, you could also backup to yourself on the same account. I think we could loosen the "encryption" requirement in the case of backups between two servers owned by the same account, but that's more of a technical detail than marketing. Let me know what's still unclear or how we can do better on the language here. Sometimes we can be a little too close to the trees to see the forest, so if you can help give us a better perspective, we'll work to improve our messaging in the marketing. Thanks!
    7 points
  4. OMG, I totally see the confusion now. I have edited that post and reworded it to be more clear. TrueNAS has no built-in means to do backups as part of their OS unless you consider rsync cron jobs/replication tasks as "backup". They don't facilitate the connection between servers or even setup the SSH permissions for you (you have to do all of that yourself). This is where our solution takes things a step further. We intend to make the experience much simpler. First you "friend" someone else that is a HexOS user (if you're doing the "buddy" approach). Then you will grant that user "permission" to backup to your system (and set a quota). Then they accept the request and authorize the backup in return (if you're doing that). Then we do the rest (establishing a secure VPN tunnel between systems, creating appropriate SSH users and handling the key exchange, etc.). You'll definitely be able to leverage the buddy backup system between two systems licensed under the same account. That would be silly of us to prohibit or unnecessarily complicate. I get the confusion. Buddy backup is just the marquee feature name for our backup solution between two servers. Every server needs a license. So if you and a buddy want to backup, you both have to have your own licenses under your own accounts. If you have two licenses for two systems under 1 account, you can use the same "buddy backup" system to handle that job as well. Apologies for muddying the water on my initial response. I can see how that had some folks confused, but I hope this clarifies.
    5 points
  5. Buddy backup will definitely work with two licenses under the same account. You will be your own buddy 😉
    5 points
  6. It's hard to believe it's already been a year since we launched the HexOS Beta and the early access campaign. What a journey it's been! In today's blog post, we're going to provide a summary of this past year's accomplishments, a run-down of what's left to achieve our 1.0 release, what's coming next, an update on the AnyRaid project, and our HexOS Holiday Sale! Read all about it in our latest blog post: https://docs.hexos.com/blog/2025-11-26.html
    4 points
  7. Another mid-quarter update featuring: New curated app installations Update to the qBittorrent installation Read more about it on our docsite here at Command Deck Update - November 25, 2025 NOTE: This update was applied automatically. You may need to clear your cache.
    4 points
  8. To celebrate the holidays and thank our community for their continued support, we're excited to announce our HexOS Holiday Sale, starting today! Existing customers can purchase additional licenses for just $99 each, perfect for expanding your home server setup. New customers can take advantage of our special two-pack bundle for $298, with additional licenses available at the same $99 promotional price. Single licenses remain available at $199 until our 1.0 release in Q1 2026. This holiday pricing for additional licenses and the two-pack bundle is available through December 31st, so don't miss out on this opportunity to join or expand your HexOS experience. Please note: License transfers are not permitted. All licenses are tied to the purchasing account. Buy now from the HexOS Store!
    3 points
  9. Wait, so if I have two licenses under my account I can't put my second server at eg my parents home for a offsite backup and sync via BuddyBackup?
    3 points
  10. As of today, yes, you can access your server from anywhere using deck.hexos.com. I have a discussion planned with the team to allow you to disable remote access which would be as simple as us verifying the WAN IP of the client device being used to connect to the deck and making sure it matches the server's WAN IP. When HexOS Local arrives, you will be able to even further reduce your cloud dependency, but there are some features like installing apps/VMs, configuring buddy backups, and e-mail notifications that will require a connection to our deck. Thankfully that connection is outbound from your server, which doesn't require you to open any ports on your firewall and expose the system to the wider net. We also do have plans to implement oAuth and 2FA in the future to further enhance security and options.
    3 points
  11. We know about this problem all-too-well. The VM features will come in layers, but our plan is to try and get ahead of those kinds of problems by detecting hardware changes and automatically adjusting device ID mappings to your VMs before they start. This still needs a lot of R&D work and there are lots of potential gotchas, but I bet we can address a lot of common scenarios like what you've described. It gets more tricky when you have multiple GPUs in a system of the same make/model, as it's hard to know which one is which for assignment to VMs. I'd say that's a problem for after the initial VMs feature release for us to investigate further. Ultimately there will be some limits to what we can do, but we're going to do this as best as is humanly possible.
    3 points
  12. Def not cloud only. If your isp/network supports peer to peer, we can coordinate that and then get out of the way. That is what's included in a lifetime license. If we end up having to relay traffic for some users, that will require a subscription as we will have to pay for the relay traffic, but obviously it will still be encrypted.
    3 points
  13. Hey, Buddy Backup isn't currently available and Hexos doesn't offer anything to do a backup to another machine. However if you login to Truenas go to Data Protection and there to the Replication Tasks. You can setup a new Replication task there following this guide: https://www.truenas.com/docs/scale/25.04/scaletutorials/dataprotection/replication/ But this requires that you can connect to the other server, via tunnel or domain name or sth. Similar.
    3 points
  14. The difference is pretty big, while they do the same thing, they do it very differently. Immich just stores all the images in plain on the file system, all the processing is done on server side, you can connect an external library and if your Immich DB or installation becomes corrupted or breaks and there is no more support for Immich you just take the photos folder and move on. But the admin and everyone who's access to the folder can see all the photos of everyone, so privacy is not that great, but administration is easier and recovery in case of an issue is easy. Ente (FunFact: Ente is German for Duck) is all about privacy. The photos are all encrypted on the server and only the client side can decrypt/see the photos. This also means that the client side needs to do all the processing, but therefore the server can be very low spec (although this doesn't matter in our case, because Hexos needs to run in the first place, so HW specs is not really a concern in any way) and it needs S3 storage and requires more setup an administration. However if your Ente DB becomes corrupted or the Ente app breaks or the Ente dev stops and your app becomes unusable, you lose all your photos, because you cannot access it any other way. But until that happens only your client side device can access the photos and no-one else can.
    2 points
  15. Pretty disappointed with this limitation. I understand the reason to avoid unscrupulous reselling, but I do think there are better ways of avoiding that without these issues. There are probably a lot of people in a similar situation as me; wanting to get a license for a relative as the family tech guy, but not wanting to have to be the sys admin for everyone. I bought a license at release because I support the mission, with no intention of using it until the features got more flushed out (still on plain TrueNAS). I am in the process of building a NAS for my father, which I intended to set up with a HexOS license so he could use buddy backup and some apps as a relatively nontechnical user. The HexOS interface is simple enough I think he can grasp it. But if I have to be an admin for his NAS anyway I might as well just set up Tailscale and rsync on TrueNAS. I understand it's a sale price and I'll probably end up getting him his own but it just feels like a slap for people that bought in to support and I hate feeling like I'm throwing money away. I'm no business major but it seems like expanding the user base would be prioritized given the possibility of genuinely useful subscription features coming down the pipe. Anyways. Just my $0.02. Still love what you guys are building.
    2 points
  16. Just got off a call with a few of the Eshtek guys, they set me straight very quickly. Before I called them, I dove into what others here have done. Here is what fixed the router swap for me: Sign into the TrueNas Scale Web UI. Go to Network: Go to Global Config settings: Change Nameserver1 and IPv4 Default Gateway to the IP address on/of your router. My issue was that I kept changing the NAS IP address to the IP of the NAS, not the router. Essentially, I was signed into my router interface, looked up what the NAS IP address was, and kept changing the Nameserver1 and Default gateway to that IP, when I should have been setting it to the IP of the router. Once that is done, my NAS found the internet again, the HexOS deck found a server and I was set! I had to skip the initial setup in order to prevent wiping the drives, but I was saved. Thanks to Nick and Eric!
    2 points
  17. Thanks for confirming and apologies to anyone that was confused. If anyone bought another license at $199 on accident today, send an email to support@hexos.com and we'll get the difference refunded.
    2 points
  18. No its not over. We are investigating why the correct pricing isn't showing up for users. Stand by.
    2 points
  19. The backup stuff sounds great, any serious system should have the ability to backup and restore, especially when apps like Immich are being recommended, seeing away to back all this stuff up would make HexOS a serious contender in the networking and diy nas space, maybe even business
    2 points
  20. at this time your best option would be using the in app backup and restore functions and then reinstalling it if you would like to migrate. But i will be sure to let the team know that users are interested in migrating over to curated versions of the apps.
    2 points
  21. I would like to see first party support for placing any app behind some of the most popular VPNs (PIA, Nord, Express, Proton, Tailscale, etc), as well as custom VPNs (WireGuard, OpenVPN, etc). For example, you may install “The Lounge” IRC client and have all internet communication pass through a PIA VPN so that your home IP is not exposed while chatting. Traditional methods of doing this involve painful configuration of iptables or other firewall rules. I believe this is an area where HexOS could really simplify things: Install a VPN plugin, authenticate with it, and then simply assign an app to a VPN plugin via the app’s settings if desired. It would be fully accessible from the home network without going through the VPN, but all internet traffic would go through the VPN with a kill switch in case the VPN goes down. Thoughts?
    2 points
  22. Correct. The additional licenses is for users that want to setup multiple systems of their own, not for buddy backups. @Todd Miller rightly called this out as confusing. What I meant to say is that you just can't transfer the license to another user. You can use buddy backups (as a feature) between two systems that you own and control (licensed under one account). Sorry for the confusion! Carry on!
    2 points
  23. If there are still a plethora of users affected after Local is released, we would consider it. But if not, we would rather spend the time via support helping people up over this fence than engineer an entire solution for a handful of folks. Support@hexos.com is available to you at no cost.
    2 points
  24. That thought did occur to us, but to be perfectly honest we'd rather anyone not comfortable following the guides or having difficulty to just contact us directly for support. That's what you all paid for and we are gonna provide it. I don't want to start asking our users who aren't comfortable to navigate the TN interface.
    2 points
  25. I ended up having to reinstall Immich (twice, for some reason, the second seems less likely to be hexos related), so I appreciate you being up-front with acknowledging that it was… not fun. Daunting was probably the right word for it. I usually consider myself tech savvy so being so totally out of my depth was frustrating in a way I’m not used to. A suggestion: some folks might be having trouble completely uninstalling/reinstalling (I did) so a simple guide on how to do that might be helpful, even if it’s just “hey delete this dataset” - I’m sure the advice exists in the forum but there are a lot of things to search through to find it. If I remember right, uninstalling/reinstalling on the hexos deck didn’t fix the underlying issue or delete the underlying data. I’ve seen the pace of updates and the pace of communication improve over the last few months - which makes it easier to assume best intent. I look forward to what’s coming next (and hopefully no other apps break that bad)
    2 points
  26. Hey I just finished my hardware migration and I'm happy to report it was successful. These are the steps I did: Log into TrueNAS SCALE web interface Go to System > General Settings > Manage Configuration > Download File If you have encrypted datasets, go to Datasets > select your encrypted dataset > Export Key Shut down server and swap hardware Prepare HexOS installation drive and use it to boot Set up HexOS/TrueNAS SCALE, I left everything on default In your router settings, give the new hardware the same IP as your old one. Restart your TrueNAS server to grab the right IP. Go into TrueNAS SCALE web interface, log in Upgrade your version of TrueNAS. At the time of writing this post, the HexOS installation image is behind of what's was being supported/recommend by the HexOS web interface. Check the filename of the .tar that was created when you exported the configuration. It should have the version of TrueNAS that was used in it (i.e. 25.04.2.6). Select the same version from the upgrade screen and confirm that you want to switch upgrade train. Apply pending updates and the system will reboot. Go to Storage > Import Pool > find your zpool Got an error? Check step 9 again. Make sure you are using the same version of TrueNAS as your old boot drive. Go into System > General Settings > Manage Configuration > Upload File After reboot, go to Apps > Configuration > Unset Pool Restart TrueNAS Go back into the web interface, go to Apps > Configuration > Choose Pool Your apps should show back up and you should be able to start them. Go to the HexOS web interface. If you haven't already, unclaim your old server and claim the new one The hardware check screen should give you a warning about an existing pool. This is good, go onto the next screen and skip creating pool. Give your server a name and you should be good to go! Really hope that HexOS has an easily migration process in the future. I have learned so much about TrueNAS that it's making less sense for me to use HexOS.
    2 points
  27. Another mid-quarter update featuring: - Install Script v2 with interactive questions during app installation to support user preferences (eg. Plex claim code) - Fangtooth Support with full TrueNAS 25.04 compatibility and automatic pool upgrades - Enhanced User Management with better visibility and access to folder permissions Read the full release notes: https://docs.hexos.com/release-notes/command-deck/2025-11-06 NOTE: This update was applied automatically. You may need to clear your cache.
    2 points
  28. We now have one: Custom Install Scripts - HexOS Hub
    2 points
  29. So I cant speak on the uGreen HW but I can tell you that if you decide to find normal computer hardware plopping in the boot SSD and hard drives it will take off and run " NOTE depending on the network chipset you have" without any hitch. I am running the same SSD that I started HEXOS "since launch" and have tested about 12 different motherboard cpu combos and the only issue has been a network chipset that the underlying Linux os didnt like.,
    1 point
  30. I did about 8 or 9 times now. And while I have done a lot of volume testing I have everything backed up and continue to treat this experience as a beta test. I'm not sure we are far enough down the path to treat it as anything else. People are still yelling the Immich is broken and how can Eshtek have such a crap product. And when they find out it was actually a TrueNAS change you start to see complaints about how this product can't accommodate this type of change. Then the complaints asking for a conversion process from old to new but that was manual so it didn't work for everyone. So now people have partial changes from several tries and a broken product. Then guys like me who left the safety of the TrueNAS catalog and followed Docker install videos. so I am not making things any easier. I made a joke a while back that go-live would be everyone formatting their systems and all starting from the same point. I said it a second time not to long ago because of this Immich specifically because I wasn't joking anymore. Now I can't see any way around it. How do you explain to the support team everything that got you to the situation your in? They know that firestorm is coming. So I do apologise to responding with this doom and gloom post to your very simple and straightforward request. I sincerely hope that they have a way to help you because I had to reload 1.25 TB of images and almost 10TB of movies (with a few family vacation videos sprinkled in. Honestly, I thought that was why rsync was going to be the answer but I guess nothing is ever that easy. Best of luck, really.
    1 point
  31. there aren't any risks to unclaiming a server. whenever you reclaim it just be sure to use the skip setup button. seems like you have the bug discussed in this post Hopefully the solution there solves your problem
    1 point
  32. Thank you 2nd License bought 😈
    1 point
  33. This is now showing correctly for me. Thank you!
    1 point
  34. @wvienna @FangerZero can you guys check again and let me know if the discount shows up correctly for you now?
    1 point
  35. This would require the app data folders themselves to be encrypted. Not impossible to do, but may not be with the first iteration of buddy backup. Definitely something we could consider!
    1 point
  36. 1 system/installation requires 1 license. And Buddy Backup is between 2 systems requiring a license each. The owner doesn't matter all you need to have is 2 Hexos installations/servers therefor 2 licence in total and you are good to go for buddy backup.
    1 point
  37. Yes most definitely! We have the underpinnings for a language selector already in place, but we're deferring translation work until after 1.0.
    1 point
  38. At this time the recommended way to update the path is to uninstall and reinstall but you shouldn't lose any data if you uncheck remove app settings and data.
    1 point
  39. Great to see the progress being made compared to the early launch last year, I'm exited to see where it goes with the new upcoming roadmap. While I'll personally will be waiting till a few more curated apps will be available (such as Kometa and Bazarr) it seems at least a good solid foundation will be standing with the 1.0 launch. Keep it up guys!
    1 point
  40. It did. We wanted to build in a better solution to address this, but as I stated in the OP, it would have required a massive divergence of focus from our team to build a solution within the UI itself. We ultimately decided putting out this post and offering 1:1 assistance to those affected was the best course of action. We are offering 1:1 support to anyone that needs it. Just email support@hexos.com and we'll schedule a time. I mention in the OP our plans to be able to better address this in the future via HexOS Local.
    1 point
  41. 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.
    1 point
  42. It would be nice if there were features that allow TrueNas/HexOS to run in parallel like Proxmox and VMWare. Truenas has capabilities of running virtual machines, if we could have the ability of having those VMs switch from one host to another if one fails then I believe that this would be fully capable of replacing Proxmox/VMWare.
    1 point
  43. I haven't used Nextcloud or Opencloud but I imagine their file management solutions are similar to Google Drive. Paperless-NGX is like the "more advanced organization" option compared to Google Drive from my point of view. Paperless allows you to ingest documents through a variety of means (upload button, watched folder, reading emails and automatically saving attachments or the email based on rules). Then it tries to apply machine learning to extract the document date and other info like who the document is regarding, what kind of document it is, where it should be stored, all based on what you have manually added metadata for. If I have a receipts document type, it will learn what I consider a receipt and assign that automatically. It also OCRs all the documents and stores the text so it's searchable later. You can add custom metadata fields like a global document ID (I'm told). You can then search, view, organize, share these documents in the paperless web UI. You can customize how it stores all these documents on disk so you can still access them outside of Paperless if you want. There are a few apps that allow direct "scan to paperless" functionality with decent cropping. You don't scan documents so each page is a file. You ingest a PDF with multiple pages normally so you would scan with your phone or a scanner, then import to paperless. Though you can ingest images and other stuff.
    1 point
  44. I think if we are honest almost everyone would say they were disappointed in how this startup has gone including Eshtek. I don't think all of our disappointment is justified because it has nothing to actually do with HexOS. However, you have hit on two points that are hard to argue with. Why are we paying up to $200 to test this application? And TrueNAS what? As for the paying to test question, I guess I am starting to do the same (well kind of) as you because I have set it aside to wait for go live. Plex and Immich are the only current curated apps I would ever use and until the serious discussions on how to secure the NAS start my machine is just a giant backup drive. And as for the current absolute requirement to use TrueNAS to do ALMOST anything including troubleshooting curated app failures. Well, if I am going to have to hire TrueNAS support to properly setup all non curated and some curated apps, I'm probably better off buying beer for my current Unraid support buddy. Like many others, I saw the LTT video and thought "Holly crap, someone finally built a system I can manage myself. I got in at the Black Friday price so HexOS on a mostly recycles server is still cheaper that a Synology or Ugreen prebuilt server. Storage seems to be the biggest cost but I have to pay that either way. I'm sure I will keep checking in and looking at the officially curated apps to see if anything looks interesting but unless there is a solid security option, it's all pretty irrelevant to me. My problem is that if I had to pay $299 what would I need to pull the trigger? That may be a tough uphill struggle for Eshtek if they want to attract people who are not at least serviceable in TrueNAS. So instead of looking at an the app we have today and deciding what it must be going to look like in 1, 2 and 5 years, we can wait and see what 1.0 looks like. I doubt though it will ever just be point and click.
    1 point
  45. With LTT Official Folding Month VIII (Nov 1st - Dec 6th) coming up, It would be really nice to see a how to guide to get FoldingAtHome easily working from anyone who knows how. I just put a request out for help for anyone to provide a guide if possible. Here's hoping. https://hub.hexos.com/topic/3927-foldingathome-ltt-official-folding-month-viii-nov-1st-dec-6th-help-setup-hexos/
    1 point
  46. Could we get a forum section for install scripts? That way as a community we can post a thread for a specific app and people can share their scripts and ask for feedback? I think that'd be handy, but I don't think it needs to go in the normal Applications support forum because that might confuse people as it's definitely a more advanced thing at the moment! Thanks
    1 point
  47. I am not seeing 2FA/MFA, despite it being discussed as part of the Q1 release plan. Is there a way to enable this that I am missing?
    1 point
  48. It is a must these days to have TailScale support, especially for secure remote access. It is far too easy to mess up a WireGaurd/OpenVPN Config, if the goal is security and simplicity, Tailscale VPN access should be a high priority.
    1 point
  49. For detailed installation instructions, please refer to this thread: Illustrated Installation Guide - START HERE! =)
    1 point
  50. Sorry, if this has been asked before & posted elsewhere. Would be handy to have app support for steam caching, especially for big/medium family's/house hold share. I can understand this will not be on the radar as yet, while sorting other issues out/beta etc
    1 point
×
×
  • Create New...