Expose Overseerr over HTTPS either from your home network or on a free VPS which has the tunnel into the home network where Radarr and Sonarr live. This is simpler for users to go to a website instead of having to also use a VPN.

This of course assumes you already have Plex or Jellyfin exposed to the public internet without a VPN.

If you're already forcing users to use a VPN for Plex/Jellyfin then hosting Overseerr locally and making it accessible over the VPN should be trivial.

Overseer runs on plex's media port? Plex has the media port 32400 NAT hole-punched, but none of my other webservices are exposed outside my VPN.

Do what I do and use the tautulli sqlite3 database to get the IP addresses of Plex users and then add them to an ipset filter in nftables/ip tables that whitelists them to access an nginx proxy serving Overseeerr on port 443. It's glorious. I'm sure any LLM can cook this up for you.

> How does Overseerr help

It's nicer to use than Sonarr / Radarr, and a single interface for people to learn. It has suggestions for people that need that. There's also MCP for it, so instead of setting up N MCPs for Sonarr / Radarr / The Next Arr, you set one up for Seerr.

You can also link people's Plex Watchlist. So the whole request / add to Sonarr/Radarr can be done from anywhere they use Plex.

Overseerr is a write-only access to your Radarr/Sonarr library, so e.g. the user cannot accidentally delete a movie or choose to download a lower quality version.

Sounds great, but if my family wanted to access a web-ui in stead of shooting me a message in natural language I could also give them the Radarr / Sonarr UI.

Currently the profile is fixed. I guess they can delete movies but I can re-downlaod in 5 min so not a massive problem. I'm on a rolling-delete schedule anyway as my hard drives fill up quickly.