{% hint style="info" %} Content Filtering Fork - This FAQ covers the Content Filtering Fork of Overseerr with parental controls and content filtering features.
If you can't find the solution to your problem here, please open an issue on GitHub. {% endhint %}
Use a third-party update mechanism (such as Watchtower, Ouroboros, or Pullio) to keep the Content Filtering Fork up-to-date automatically.
Docker Image: Use larrikinau/overseerr-content-filtering:latest - see Docker Hub for available tags.
This Content Filtering Fork adds comprehensive parental control features:
- Per-user content rating restrictions (G/PG/PG-13/R/NC-17 for movies, TV-Y/TV-Y7/TV-G/TV-PG/TV-14/TV-MA for TV)
- Quality-based content filtering (minimum TMDB rating/votes)
- Enhanced content discovery filtering across all interface areas
- Server-side security enforcement that users cannot bypass
All upstream Overseerr features remain fully functional.
The easiest but least secure method is to simply forward an external port (e.g., 5055) on your router to the internal port used by Overseerr (default is TCP 5055). Visit Port Forward for instructions for your particular router. You would then be able to access Overseerr via http://EXTERNAL-IP-ADDRESS:5055.
A more advanced, user-friendly, and secure (if using SSL) method is to set up a web server and use a reverse proxy to access Overseerr. Please refer to our reverse proxy examples for more information.
The most secure method (but also the most inconvenient method) is to set up a VPN tunnel to your home server. You would then be able to access Overseerr as if you were on your local network, via http://LOCAL-IP-ADDRESS:5055.
Since Overseerr has an almost native app experience when installed as a Progressive Web App (PWA), there are no plans to develop mobile apps for Overseerr.
Out of the box, Overseerr already fulfills most of the PWA install criteria. You simply need to make sure that your Overseerr instance is being served over HTTPS (e.g., via a reverse proxy).
Currently, the Content Filtering Fork uses the same translation system as upstream Overseerr. For translation requests specific to content filtering features, please open an issue on our GitHub repository.
You can find the changelog for your version in the Settings → About page in your Content Filtering Fork instance.
You can alternatively review the release history and commit history on GitHub.
Overseerr currently supports the following agents:
- New Plex Movie
- Legacy Plex Movie
- New Plex TV
- Legacy Plex TV
- TheTVDB
- TMDB
- HAMA
Please verify that your library is using one of the agents previously listed.
When changing agents, a full metadata refresh of your Plex library is required. (Caution: This can take a long time depending on the size of your library.)
First, check the Overseerr logs for media items that are missing. The logs will contain an error as to why that item could not be matched.
- Verify that you are using one of the agents mentioned above.
- Refresh the metadata for just that item.
- Run a full scan in Overseerr to see if that item is now matched properly.
- If the item is now seen by Overseerr then repeat step 2 for each missing item. If you have a large amount of items missing then a full metadata refresh is recommended for that library.
- Run a full scan on Overseerr after refreshing all unmatched items.
You can also perform the following to verify the media item has a GUID Overseerr can match:
-
Go to the media item in Plex and "Get info" and click on "View XML".
-
Verify that the media item's GUID follows one of the below formats:
- TMDB agent
guid="com.plexapp.agents.themoviedb://1705" - New Plex Movie agent
<Guid id="tmdb://464052"/> - TheTVDB agent
guid="com.plexapp.agents.thetvdb://78874/1/1" - Legacy Plex Movie agent
guid="com.plexapp.agents.imdb://tt0765446"
- TMDB agent
Please see these instructions on how to locate and share your logs.
Content rating filters are applied server-side and completely hide restricted content from users. When a user has rating restrictions:
- Content above their rating limit is hidden from ALL interface areas
- This includes discover pages, search results, person pages, collections, and network browsing
- The filtering cannot be bypassed or overridden by users
- Only administrators can modify user rating restrictions
No. Restricted content is completely hidden from the user's interface. They have no indication that content is being filtered - it simply doesn't appear in their results.
Yes! Curated quality filters (minimum TMDB rating/votes) work alongside per-user content rating filters. Content must pass BOTH filters to be visible to users.
If you're a restricted user, content above your rating limit is intentionally hidden. If you're an administrator and content is missing:
- Check your Curated Quality Filters in Settings - you may have minimum rating/vote thresholds set
- Set both Curated Min Rating and Min Votes to 0 to disable quality filtering
- Follow the standard Plex content troubleshooting steps
- Go to User List and click Edit for the user
- Find the Content Rating Filters section
- Set appropriate Maximum Movie Rating and Maximum TV Rating
- Save the user settings
Example: For a child, set Movie Rating to PG and TV Rating to TV-PG.
Yes! As an administrator:
- Set all users' content ratings to the highest levels (NC-17 for movies, TV-MA for TV)
- Set Curated Min Rating and Min Votes to 0 in Settings
- This provides the same experience as upstream Overseerr
Please see the documentation for importing users from Plex.
Yes! Please see the documentation for creating local users.
Permissions can be configured for each user via the User List or their User Settings page. The Content Filtering Fork includes all upstream permissions plus content rating controls. If you have suggestions for additional features, submit a feature request!
Verify you are running v3 of both Radarr and Sonarr. Overseerr is not backwards-compatible with previous versions.
Yes! If you keep both non-4K and 4K content in your media libraries, you can link separate 4K Radarr/Sonarr servers to allow users to submit 4K requests. (You must configure default non-4K and default 4K Radarr/Sonarr servers.)
Please see the Services documentation for details on how to configure your Radarr and/or Sonarr servers.
Note that users must also have the Request 4K, Request 4K Movies, and/or Request 4K Series permissions in order to submit requests for 4K content.
Check the minimum availability setting in your Radarr server. If a movie does not meet the minimum availability requirement, no search will be performed. Also verify that Radarr did not perform a search, by checking the Radarr logs. Lastly, verify that the item was not already being monitored by Radarr prior to approving the request.
See "Some media is missing from Overseerr that I know is in Plex!" for troubleshooting steps.
If you configured a URL base in Sonarr, make sure you have also configured the URL Base setting for your Sonarr server in Overseerr.
Also, check that you are using Sonarr v3 and that you have configured a default language profile in Overseerr.
Language profile support for Sonarr was added in v1.20.0 along with a new, required Language Profile setting. If series requests are failing, make sure that you have a default language profile configured for each of your Sonarr servers in Settings → Services.
I am getting "Username and Password not accepted" when attempting to send email notifications via Gmail!
If you have 2-Step Verification enabled on your account, you will need to create an app password.
This may be an issue with how you are proxying your Overseerr instance. A good first troubleshooting step is to verify that the Content-Security-Policy HTTP header being set by your proxy (if any) is configured appropriately to allow external embedding of the image.
For Gmail users, another possible issue is that Google's image URL proxy is being blocked from fetching the image. If using Cloudflare, overzealous firewall rules could be the culprit.