Carl

I’m somewhere in the middle, because comments like yours actually reinforce my concerns. A reverse proxy isn’t really doing anything to make you more secure, unless you’re using it for some sort of access control. It hides which ports you’re using, and allows you to encrypt your traffic with TLS… But it doesn’t add any additional security to the services you are exposing.

Maybe if you use it for access control, to add a secondary username/password to the services. But that breaks most legitimate things (apps, mostly) that try to reach the double-password-protected service. Because a user on a web browser may be able to type in two passwords, (one for the reverse proxy, and then one for the service itself) but an app will try to pass that info automatically using headers.

Any vulnerabilities in the services will still become potential attack vectors. Anyone who remembers the Huntarr debacle will know exactly what I’m talking about, because a single service being vulnerable can do a lot of damage. Yes, containerization does a lot to help mitigate damage by excluding access to everything except what you give it. But it won’t completely stop things from going wrong.

I see. I think you can do that, but it will need to be done during the initial setup. You could also try FileBot for the initial file renames, if you can’t get the initial file discovery and setup working.

Ah yeah, that’s because it will use the folder to store extra files as well, like subtitles, metadata, poster art, etc… Just dumping every media file into a single “Movies” library isn’t great, because you’ll have a ton of overlapping files. Separating them into their own folders allows you to store those extra files alongside the media.

My only guess is that they were trying to map their config/downloads/library folders to the same location. And yeah, that probably wouldn’t work.