Todd Miller

Were dates given for either of those things? If not it proves FangerZero's point and seem to justify their frustration. Is either Jellyfin or Templates in testing? If not then neither would seem to be ready by HexOS 1.0. And while I am on that subject, I haven't seen or heard any discussion on when that go live date would be. It would seem that if that were within a couple months we would have heard something and be finalizing our hardware purchases to be ready. For me HexOS is already prod. I wanted a simple NAS and when I heard LTT talking about his investment and requirements I thought I finally had what I was looking for. Yeah Plex is neat and Immich is cool and I'm near 60 so I really talk like that. The only way this ends badly is the company goes under before the local UI is created. If you don't see the frustration of your community regardless if it's a bug in HexOS, TrueNAS or the app being run, well then you have a much larger issue on your hands than whether the switches should be to the right or left of the descriptor text. Yes it's a beta test. Yes we knew that going in. But also "yes, this is coming or that is coming and we are also working on a new file system" is just more vagueness in an already vague picture as far as we know.

Did they ever say they would have more than two apps or just that there would be a template if someone wanted to add more apps?

Sorry I blew past this but I mean I couldn't setup the initial datasets as per this video. If the issue is the permissions he talks about later, I didn't try to sync to that because of the dataset error above. Maybe I need to do this out of order?

How were you able to setup the datasets he uses? I get an error when trying to create the Nextcloud dataset. I've no idea how to grant permission to the user or which user it is referring to. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/middlewared/main.py", line 211, in call_method result = await self.middleware.call_with_audit(message['method'], serviceobj, methodobj, params, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1529, in call_with_audit result = await self._call(method, serviceobj, methodobj, params, app=app, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1460, in _call return await methodobj(*prepared_call.args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 230, in create return await self.middleware._call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/main.py", line 1460, in _call return await methodobj(*prepared_call.args) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/service/crud_service.py", line 261, in nf rv = await func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 49, in nf res = await f(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/schema/processor.py", line 179, in nf return await func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/middlewared/plugins/pool_/dataset.py", line 714, in do_create verrors.check() File "/usr/lib/python3/dist-packages/middlewared/service_exception.py", line 72, in check raise self middlewared.service_exception.ValidationErrors: [EINVAL] pool_dataset_create.share_type: Filesystem permissions on path /mnt/HDDs/Applications prevent access for user "apps" to the path /mnt/HDDs/Applications/Nextcloud. This may be fixed by granting the aforementioned user execute permissions on the path: /mnt/HDDs/Applications.

I had trouble at first when I set the external IP to the IP of Tailscale. What I forgot was my phones wifi connection wouldn't use my external IP so the app kept reporting a false fail as I was setting it up. I ended up having to turn off wifi and use my phone connection/data. Then because my phone connection uses my external IP without issue, it worked. The IP switcher on Imich is pretty touchy.

I believe speedking456 gets credit for this one.

I'm not saying it is right for your situation but I have been using Tailscale for remote access to Immich and the NAS storage itself. I picked it because someone did a pretty good install guide and posted it. Again, I;m not saying it the best for you. I can say though that for someone who doesn't know squat about TrueNAS or Linux or Docker containers and the like, I can saw it worked first try. I am curious if anyone wants to volunteer some alternatives. I believe Cloudflare is sprinkled throughout the forum as well as the general concept of reverse proxy and port forwarding.

Do you also have a recommendation of reverse proxies? I know there are several but recommendations of peoples top three help a lot.

I only disagree with that statement because the web UI is all that loses connection. All other connections stay active. Has the team given you different specific direction? And to be more specific, I can access the HexOS URL. I just get an unavailable error through that URL.

Hmm. It sounds Mascot like you have the measure of this issue. I wonder if this will be solved or at least lessened with the local UI?

Right now I am getting the same thing but it is weird and may not be the same as others. I only reboot or shutdown the server when I have to. And that is once or twice a week (mostly just once) because of the server unavailable error. The thing I think is weird is only the wb UI is having a connection issue. My HD Homerun capture card stays connected and all my TV's still can either watch live TV but also movies and pre-recorded shows from the HexOS server. My windows drive assignments also maintain their connection to the server. I haven't tried the TrueNAS connection because honestly, I don't think of it fast enough. Is it possible something is happening at the developers end that only the web UI seems affected for me? It is an extremely annoying issue since it requires me to reboot the HexOS server. When I do I can connect again without noticeable issue.

Install guide are critical for the beta test to pick up more of the steam it had at the beginning. The "I can't get this o work" forum posts seem to outnumber the "Wow, this is great' posts. There are also few posts that show what people use and are bringing over from TrueNAS. And even less on how they did it. And for people like me I'm not even thinking about trying other apps on my own until I see more folks nailing down the initial install. Right or wrong, I saw a guide for tailscale and was able to use it to get remote access to Immich and the storage within HexOS itself. I'm slow to look at apps that cost though I have a Plex pass because getting the value of that app is within my skill.. It seems that if you put an install guide that the new to NAS folks can follow, you are helping to set the apps that will become the defaults in the near term. First dropbox type self storage apps with a working install will be way ahead of the other apps people like even if the HexOS devs chose a different app to list. As it is often said, one in the hand is worth two in the bush.

By community do you mean the original developer if they want their app ro run on HexOS and the developer takes responsibility to maintain compatibility? Or community as in folks like me ho will try to follow guides to get a working install, filling the template out as I go? Or something else I can't really imagine yet since we are early in this process? It seems the official templates need to be curated by HexOS to maintain the widest compatibility possible. But folks with more complicated hardware or the interest to load 20+ TrueNAS compatible apps will want a more custom template or don't want to wait for templates created on a established release schedule. Never a dull moment I guess.

I wonder if this is what's going on?

I wasn't at that time but that did work once for me later.