sct / overseerr

Request management and media discovery tool for the Plex ecosystem
https://overseerr.dev
MIT License
3.89k stars 449 forks source link

All requests to Add Movie to Radarr failing #3751

Open dmudgeau opened 10 months ago

dmudgeau commented 10 months ago

Description

All of a sudden all requests to Add a movie to Radarr are failing with the message "Failed to add movie to Radarr" in the Logs"

Issue has started happening after making no changes (except constantly updating versions of Overseerr and Radarr to the latest)

I can add a movie fine if I do it inside Radarr but Overseerr trying to add it gets the failed every time. TV Shows to Sonarr work fine

I have tried restarting Overseer Deleting and re-adding the Radarr Server Changing the Radarr API Key Restarting Radarr

(I found in Radarr I had an issue with malformed database and the Messaging Cleanup task would always fail and it seems thats the DB table that was corrupted according to the Radarr Logs) so I blew away the Radarr database and completely re-created it from scratch and now have no Radarr malformed DB issues however issue to Add movie from Overseerr still persists

Dont know what else I can try and the logs dont give much help from overseerr why it failed perhaps there is an API change required to Radarr?

Version

1.33.2 (Docker linuxserver.io)

Steps to Reproduce

Request a movie through the Overseer web page or Add to Plex Watchlist Movie Request Automatically Approved Movie Request Failed Radarr n 5.2.6.8376 Version 5.2.6.8376 (Docker image from linuxserver.io)

Screenshots

No response

Logs

2024-01-17T03:06:43.407Z [error][Radarr]: Failed to add movie to Radarr. This might happen if the movie already exists, in which case you can safely ignore this error.{"errorMessage":"Failed to add movie to Radarr","options":{"minimumAvailability":"released","monitored":true,"profileId":4,"qualityProfileId":4,"rootFolderPath":"/plexMedia/Movies/Backed Up","searchNow":true,"tags":[],"title":"The Devil's Advocate","tmdbId":1813,"year":1997}}

2024-01-17T03:06:43.406Z [error][Radarr]: Failed to add movie to Radarr{"options":{"minimumAvailability":"released","monitored":true,"profileId":4,"qualityProfileId":4,"rootFolderPath":"/plexMedia/Movies/Backed Up","searchNow":true,"tags":[],"title":"The Devil's Advocate","tmdbId":1813,"year":1997}}

Platform

desktop

Device

N/A

Operating System

Synology NAS Docker

Browser

N/A Through API

Additional Context

No response

Code of Conduct

dmudgeau commented 10 months ago

so I believe I found the root cause of this...

I have my Radarr running through a reverse proxy using nginx proxy manager

radarr is accessed via: radarr.mydomain.net at port 80, nginx then forces ssl for it and I have a certificate installed so it's secured

the reverse proxy points to my Nas IP port : XXXX where which corresponds to the port the docker container is listening on for the external port to them map to the port 7878 inside the container

ok so for the Radarr server inside overseerr it points to Radarr.mydomain.net at port 80 and when testing it, it is successful. It has always been setup this way as well since day 1. Sonarr is setup exactly the same way and it's not having an issue

I found if I changed the port to the port that docker is listening on while still keeping the Radarr.mydomain.net the issue is gone and movie requests are working again!

so perhaps there has been a change recently for overseeerr or Radarr where overseerr can no longer send requests to Radarr when it's running on a reverse proxy on port 80?

stale[bot] commented 6 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

heiko1988 commented 6 months ago

Hi, I had the same problem today. I was able to solve it and wanted to share it with you.

In Overseerr, I always had my domain for Radarr set with HTTP and port 80. When it stopped working, I tried a few things, and ultimately it was just one setting for me.

Changing the HTTP protocol to HTTPS and the port from 80 to 443. Now it accepts the requests normally again :)

By the way, I also use Nginx Proxy Manager.

dmudgeau commented 5 months ago

Hi, I had the same problem today. I was able to solve it and wanted to share it with you.

In Overseerr, I always had my domain for Radarr set with HTTP and port 80. When it stopped working, I tried a few things, and ultimately it was just one setting for me.

Changing the HTTP protocol to HTTPS and the port from 80 to 443. Now it accepts the requests normally again :)

By the way, I also use Nginx Proxy Manager.

Thanks for that. my issue was an error in my network for the dnsmasq in my router I was sending all requests to my subdomain to nginx unknowingly instead of just the subdomains I wanted fixed that and that fixed my issue