Frequently Asked Questions (FAQ)
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
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
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.
You can find the changelog for your version (stable/
develop) in the Settings → About page in your Overseerr instance.
Overseerr currently supports the following agents:
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.
- 1.Verify that you are using one of the agents mentioned above.
- 2.Refresh the metadata for just that item.
- 3.Run a full scan in Overseerr to see if that item is now matched properly.
- 4.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.
- 5.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:
- 1.Go to the media item in Plex and "Get info" and click on "View XML".
- 2.Verify that the media item's GUID follows one of the below formats:
- 1.TMDB agent
- 2.New Plex Movie agent
- 3.TheTVDB agent
- 4.Legacy Plex Movie agent
Permissions can be configured for each user via the User List or their User Settings page. The list of assignable permissions is still growing, so if you have any suggestions, 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.)
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.
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.
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-PolicyHTTP 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.