Reverse proxy entire Jellyfin instance or mount media remotely?

[schnappi]

Is it preferable to run an entire Jellyfin instance behind a reverse proxy with local disks or run Jellyfin locally (still using a reverse proxy) with remote connections to the media disks? More or less, which would work better? Currently running an entire instance behind a reverse proxy, but it doesn't work great. Not sure if this is completely due to the tunnel or not.

[crobibero]

Having the disks being local to Jellyfin is preferred since all data flows through Jellyfin.

[I-G-1-1]

As I don't want Jellyfin to directly manage my collection (folder structure, file names) I prefer to use local connection (only 1GB LAN) to the media disk using SAMBA and mount it as Read Only on the Jellyfin Server.

[ChosenOne]

Hello, new user and first time commenter.
I have Jellyfin library set up as read only in truenas just in case for the same reason.
I also have the main portal web facing with a duckdns subdomain working flawlessly. What’s not working great for you?
I’m assuming you’re able to create a new smb user with read only rights to that network file/drive and update on mount?

[schnappi]

Running Jellyfin on one network, but accessing it through an Nginx reverse proxy on another network doesn't work great. Haven't tried setting up Nginx caching yet on the reverse proxy. There are a lot of static image and .js files so this might make a difference.

[bitmap]

What doesn't work great? I've been running nginx and have several folks utilizing my instance remotely.

[schnappi]

Jellyfin is slow when the reverse proxy is on another another network from the server. It could be the connection between the reverse proxy and the server.