https://www.seafile.com/

Make sure your home server config isn’t mistaking this client as a remote user. Check your networking, etc

Doesn’t seem to be possible to self-host

In fairness, the lack of Enterprise OS connectivity is spelled out in the Pricing breakdown on their website.

While this post is in support of a self-hosting platform, the request itself is storage-related. I would recommend that you reach out to https://lemmy.world/c/zfs or https://discourse.practicalzfs.com.

Home assistant integration could accomplish this for you. Not sure if it’s less work than regular mobile clients, though.

I think fans of Nix and NixOS would agree.

Love another iOS option.

Right. You kind of want your bare metal OS as vanilla as possible. If you need to nuke and pave, you don’t need to worry about re-applying various configs. Additionally, on a theoretical level, if there’s a bug in something on the bare metal OS, the separation provided by VMs and containers should mean it doesn’t affect the the apps in those VMs / containers.

That seems easier - at least to me - than keeping track of configs in text files or even Ansible playbooks.

Have you considered searching the GitHub issues?

I love the Enbrighten stuff. It’s not WiFi, but it’s local.

Curious how this is distinct from SimpleX.

Would they have to be VLAN aware if the switch port was already tagged AND if OP doesn’t care to consider untagged traffic ?

With the disclaimer that Proxmox has nothing to do with this question, I’m forced to assume this is just a networking issue that happens to use OPNsense as the router. Because of that, I must advise that you seek help from a networking-focused community. There’s no clear link to self-hosting in this post, which is required per Rule 3.

If the connections are already tagged as you come into the Proxmox server, then you need only to create interfaces for them in Proxmox (vmbr1, vmbr2, etc). EDIT: if you’re doing PCI passthrough of the physical NICs, ignore this step.

Then, in OPNsense, you just adding the individual interfaces. No need to assign a VLAN inside OPnsense because the traffic is already tagged on the network (per your earlier statement).

Whether or not the managed switch that has tagged each port is also providing VLAN isolation, you’ll simply use the OPNsense firewall to provide isolation, which it does by default. You’ll use it to allow the connections access to the fiber WAN gateway.

You’ll need to be far more descriptive than “I can’t get it to work.” I can almost guarantee you that Fedora is not the problem.

https://perfectmediaserver.com/

I’m a little lost on how a container would mess with your boot loader (GRUB). That aside, most of what you’re explaining to do with the containers. These are OS-agnostic. What do the container logs tell you?