This started happening again, just informing…
Sonarr version (exact version):
Mono version (if Sonarr is not running on Windows):
OS:
((Debug logs)):
(Make sure debug logging is enabled in settings and post the full log to hastebin/pastebin/dropbox/google drive or something similar, do not post them directly here)
Description of issue:
Sonar - 2.0.0.4409
Mono - 4.2.2.30-7
Both on Synology DSM 6
I just noticed the Sonarr was updated this morning, so I updated the Plex Media Server to the latest, was waiting for the PMS connect fix. I’ll see if this “Unable to check…” error still remains with PMS 1.3.
The Plex connect works fine now, by the way, thank you!
Is this log sufficient?
System.NullReferenceException: Object reference not set to an instance of an object
at NzbDrone.Core.Notifications.Plex.PlexServerProxy.Version (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x0004c] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Plex\PlexServerProxy.cs:102
at NzbDrone.Core.Notifications.Plex.PlexServerService.GetVersion (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00016] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Plex\PlexServerService.cs:99
at NzbDrone.Core.Notifications.Plex.PlexServerService.PartialUpdatesAllowed (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00000] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Plex\PlexServerService.cs:71
We’d need to see the ((debug logs)) (that include the error), possibly ((trace logs)) so we can see the responses from PMS.
The logs you PMed me aren’t debug logs and the only related error is from 5 days ago. If you see this again we’ll need to see ((trace logs)) so we can see the response from PMS as well.
I enabled the debug logging, will update if anything.
More than 24 hours past without any Plex errors. Perhaps there was a conflict between Sonarr and PMS versions which solved itself after the update.
Having the same issue, sent you a PM with logs
Your trace logs don’t include the time that the error happened so don’t tell us anything.
balls might have sent the wrong one https://paste.ee/r/Df1FT heres the one at the time of it, happened at 4:13pm on the big bang theory
Thanks, looks like we were trying to parse old responses as if they were responses for 1.3+. I have pushed a fix to develop.
1 Like
Some new errors now which i guess are related to the recent change, PM with logs
Ahh, thanks for the logs, looks like Plex sends an empty response and the new changes were trying to handle it and blowing up. Pushed a fix for it.
1 Like
Cheers 
Some new logs with new errors, sorry lol
No, that was my fault, I logged that the error was empty and to ignore it, but then still processed it. Fixed for real this time.
1 Like
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.