This is a docker compose that I know works for qbittorrent behind gluetun.

I wonder if you are missing the “network_mode: service:gluetun” part?

‘’’

qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent2 network_mode: service:gluetun environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC - WEBUI_PORT=9090 - TORRENTING_PORT=6882 volumes: - /path/to/qbittorrent/appdata:/config - /mnt/JellyFinContent/Data/torrents:/data/torrents #optional

ports:

- 9090:9090

- 6882:6882

- 6882:6882/udp

depends_on:
  gluetun:
    condition: service_healthy
restart: unless-stopped

‘’’

Gluetun and mullvad works for sure but, yes, you do need to modify some settings in the compose file. At least I did to get it work.

Exposing your jellyfin on the Internet is much more difficult and requires knowledge of networking and security best practices. It is not as easy as “just giving someone a login” though for those with the know how I would easily recommend it over Plex.

4. Dont buy Roku :D

https://foldingathome.org/

Why does it matter if they add the option for ai? You have to configure a provider yourself or setup a local one (cool idea) so I don’t really see the problem with giving the option to those who want it.

Does the user running the jellyfin service have permissions to read the folder/files? You aren’t running jellyfin in docker by chance, right?

So when you go to create the library in jellyfin you don’t see the external drive but see your other drives as options?

Did you create a library in jellyfin?

Can you browse to the files via the mount point? Is the external drive listed at all?

From there you want to make sure you have the location listed as the library location in jellyfin. Then make sure the naming/file structure is correct according to the jellyfin documentation.

Yikes. Just hit em with the ol’ “<3” for privacy. Does not inspire confidence.