Replies: 4 comments 2 replies
-
I also have Overseerr running in Docker on a Synology NAS. I'm having the exact same issue and I'm not sure what to do. Overseerr was working perfectly fine until about a week ago and I'm not sure what happened. I didn't make any changes to anything and it just suddenly stopped loading trending stuff. Getting same errors in my debug log on Portainer. |
Beta Was this translation helpful? Give feedback.
-
with the cli command: 'docker exec -it [containerID] bash' you can go 'inside' the container, from there you can try to do some ping etc to check whether or not DNS and all is working. Perhaps good to use next time you run into issues. They seem network related. |
Beta Was this translation helpful? Give feedback.
-
and with: 'docker ps' you get a list of containers running and their corresponding ID's. |
Beta Was this translation helpful? Give feedback.
-
This happened with me and it was a DNS problem caused by my VPN dropping with the kill switch on. Fixed the VPN and it started working again. Hope this helps someone. |
Beta Was this translation helpful? Give feedback.
-
I've had Overseer running for over a couple of months now with no problems, until about a week ago, movies and series stopped displaying, it just says "movie not found" with the TMDB ID number, I'm able to log in to Overseerr in and outside my own network.
I'm running on a Synology NAS with a reverse proxy, it was working fine even without proxy support, I've now turned that on, it hasn't made any difference.
Example of some of my logs:
[error][Plex Scan]: Failed to process Plex media{"errorMessage":"[TMDB] Failed to fetch TV show details: connect ETIMEDOUT
[debug][API]: Something went wrong retrieving popular series{"errorMessage":"[TMDB] Failed to fetch discover TV: connect ETIMEDOUT
Beta Was this translation helpful? Give feedback.
All reactions