Having your ISP do your port forwarding seems alien to me as that’s not the norm where I am. Since it seems like a standard thing where you are, you may run the risk of another ISP doing the same thing. Personally, if the price is right, I’d take the latency hit and get a VPS and route all inbound traffic through that via wireguard.

This is also dependent on who is running the server and how it’s set up. If it’s the matrix.org you’re using, I couldn’t tell you. If it’s someone hosting/you’re self-hosting, you need a STUN server for traversing NAT. It’s not part of the default Synapse docker install and I’m not sure about non-docker installs.

That’s an understatement. $300 for the TS3+. Holy shit.

I’m 100% sure that your problem is permissions. You need to make sure the permissions match. Personally, I created a group specifically for my NFS shares then when I export them they are mapped to the group. You don’t have to do this, you can use your normal users, you just have to make sure the UID/GID numbers match. They can be named different as long as the numbers match up.

Basically when you make a new group or user, make sure that the NUMBER that it’s using matches whatever you’re using on your export. So for example: if you use groupadd -g 5000 nfsusers just make sure that whenever you make your share on your NAS, you use GID of 5000 no matter what you actually name it. Personally, I make sure the names and GIDs/UIDs are the same across systems for ease of use.

Also, to add to this: you’re setup sounds almost identical to mine. I have a NAS with multiple TBs of storage and another machine with plenty of CPU and RAM. Using NFS for your docker share is going to be a pain. I “fixed” my pains by also using shares inside my docker-compose files. What I mean by that is specify your share in a volume section:

volumes:
  media:
    driver: local
    driver_opts:
      type: "nfs"
      o: "addr=192.168.0.0,ro"
      device: ":/mnt/zraid_default/media"

Then mount that volume when the container comes up:

services:
  ...
  volumes:
        - type: volume
        source: media
        target: /data
        volume:
          nocopy: true

This way, I don’t have to worry as much. I also use local directories for storing all my container info. e.g.: ./container-data:/path/in/container

links is pretty lightweight. All joking aside, I’d look at adding RAM to it if possible. That’s probably going to help the most.

Use a USB drive or otherwise download this on the Win side and get it over to your Ubuntu side: linky Install that package and you should be able to build your kernel module using dkms.

Of course it’s Missouri………

Kind of. I’m thinking something along the lines of sonarr/radarr/etc but with the ability to play/stream the podcast instead of downloading it. I tend to use web interfaces of stuff like that at work and can’t really use my phone. Maybe I’ll have to look into a roll-your-own solution using some existing stuff. Was hoping I wouldn’t have to.