this post was submitted on 13 Jan 2024
1 points (51.2% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54577 readers
222 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So I don't use overseerr but I do use jellyseerr with my emby setup. Both are just webservers that use a webpage/site that you can login to and add/search for content that will then be sent to your -arr stack and finally indexed into Plex/Emby. You can install overseerr on whatever machine you like, but to access it your other devices need to know where to find it (ie IP:port of hosting machine). You should really set up overseerr on a machine that runs continuously, so like others have said, likely the machine you run Plex on.
I personally take this a step further and use an internal custom domain name (ie. jellyseerr.mymedia.com) that can be accessed from any device on my internal network. I set my router to capture all domain requests for "mymedia.com" and redirect them to a reverse proxy (swag in my case) that will then forward the requests to different IP:port combinations based on subdomain. For example: emby.mymedia.com, jellyseerr.mymedia.com, radarr.mymedia.com, etc. This allows you to access all your services using easy to remember domain names instead of IP addresses.