search

jorenn92 / Maintainerr

Looks and smells like Overseerr, does the opposite. Maintenance tool for the Plex ecosystem
https://maintainerr.info
MIT License
754 stars 13 forks source link

Cant connect to Plex Radarr or Sonarr #1229

Open Vagenthar opened 3 weeks ago

Vagenthar commented 3 weeks ago

Did not change any settings the application worked fine and suddenly this happened.

2024/08/22 11:51:33 stdout [maintainerr] \  22/08/2024 11:51:33  [WARN] [PlexApiService] Plex api communication failure.. Is the application running?
2024/08/22 11:51:28 stdout [maintainerr] | 22/08/2024 11:51:28  [WARN] [PlexApiService] Plex api communication failure.. Is the application running?
2024/08/22 11:50:28 stdout [maintainerr] | 22/08/2024 11:50:28  [INFO] [CollectionWorkerService] Not all applications are reachable.. Skipping collection handling
2024/08/22 11:50:28 stdout [maintainerr] | 22/08/2024 11:50:28  [INFO] [CollectionWorkerService] Start handling all collections
2024/08/22 11:50:28 stdout [maintainerr] | 22/08/2024 11:50:28  [WARN] [SonarrApi] Couldn't fetch Sonarr info.. Is Sonarr up?
2024/08/22 11:50:18 stdout [maintainerr] | 22/08/2024 11:50:18  [WARN] [RadarrApi] Couldn't fetch Radarr info.. Is Radarr up?
2024/08/22 11:50:08 stdout [maintainerr] | 22/08/2024 11:50:08  [WARN] [PlexApiService] Plex api communication failure.. Is the application running?
2024/08/22 11:50:01 stdout [maintainerr] | 22/08/2024 11:50:01  [INFO] [RuleExecutorService] Starting Execution of all active rules
2024/08/22 11:49:55 stdout }
2024/08/22 11:49:55 stdout code: 'ECONNRESET'
2024/08/22 11:49:55 stdout at TCP. (node:net:338:12) {
2024/08/22 11:49:55 stdout at Socket.emit (node:events:531:35)
2024/08/22 11:49:55 stdout at Socket.socketCloseListener (node:_http_client:473:25)
2024/08/22 11:49:55 stdout Error: socket hang up
2024/08/22 11:49:55 stdout }
2024/08/22 11:49:55 stdout code: 'ECONNRESET'
2024/08/22 11:49:55 stdout at TCP. (node:net:338:12) {
2024/08/22 11:49:55 stdout at Socket.emit (node:events:531:35)
2024/08/22 11:49:55 stdout at Socket.socketCloseListener (node:_http_client:473:25)
2024/08/22 11:49:55 stdout Failed to proxy http://localhost:3001/api/plex/libraries Error: socket hang up
2024/08/22 11:49:50 stdout }
2024/08/22 11:49:50 stdout code: 'ECONNRESET'
2024/08/22 11:49:50 stdout at TCP. (node:net:338:12) {
2024/08/22 11:49:50 stdout at Socket.emit (node:events:531:35)
2024/08/22 11:49:50 stdout at Socket.socketCloseListener (node:_http_client:473:25)
2024/08/22 11:49:50 stdout Error: socket hang up
2024/08/22 11:49:50 stdout }
2024/08/22 11:49:50 stdout code: 'ECONNRESET'
2024/08/22 11:49:50 stdout at TCP. (node:net:338:12) {
2024/08/22 11:49:50 stdout at Socket.emit (node:events:531:35)
2024/08/22 11:49:50 stdout at Socket.socketCloseListener (node:_http_client:473:25)
2024/08/22 11:49:50 stdout Failed to proxy http://localhost:3001/api/plex/libraries Error: socket hang up
jorenn92 commented 2 weeks ago

Does this persist after a reboot?

Vagenthar commented 2 weeks ago

Yes.

jorenn92 commented 2 weeks ago

I don't really know what's going on here. You could try to use the latest main/develop docker image and enable debug logging to hopefully get some more info. On first glance, this seems like a network issue.