Sonarr version (exact version): 3.0.1.418 Mono version (if Sonarr is not running on Windows):N/A OS: Windows 10 Debug logs: Description of issue: So i currently am running 2 PLEX Media Servers, PMS1 is on My Windows 10 PC (Main for others to use) the PMS2 is on my Nighthawk X10 (Backup in case main goes down) I have everything setup with PMS1 fine, but when i goto Settings>Connect and try to add the PMS2 with the ip of 192.168.1.1 i get a message “Unable to connect to Plex Server”. If i type 192.168.1.1:32400 it will open up for me in Chrome.
Is it because its brand new and updating content?
Is there something i else i need to do?
Each PMS has is own email that it connect to to be completely seperate from each other
Sonarr version (exact version) : 3.0.1.430 OS : Windows 10
Trace Log
[v3.0.1.430] NzbDrone.Core.Notifications.Plex.PlexException: Unable to connect to Plex Media Server
at NzbDrone.Core.Notifications.Plex.Server.PlexServerProxy.ProcessRequest(HttpRequestBuilder requestBuilder) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerProxy.cs:line 198
at NzbDrone.Core.Notifications.Plex.Server.PlexServerProxy.GetTvSections(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerProxy.cs:line 39
at NzbDrone.Core.Notifications.Plex.Server.PlexServerService.GetSections(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerService.cs:line 68
at NzbDrone.Core.Notifications.Plex.Server.PlexServerService.Test(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerService.cs:line 164
19-4-10 15:19:18.1|Trace|SonarrErrorPipeline|Handling Exception
19-4-10 15:19:18.1|Warn|SonarrErrorPipeline|Invalid request Validation failed:
-- Unable to connect to Plex Server
19-4-10 15:19:18.2|Trace|Http|Res: 4151 [POST] /api/v3/notification/test: 400.BadRequest (1340 ms)
Debug Log
19-4-10 15:17:21.4|Warn|SonarrErrorPipeline|Invalid request Validation failed:
-- Unable to connect to Plex Server
19-4-10 15:17:21.4|Debug|Api|[POST] /api/v3/notification/test: 400.BadRequest (1084 ms)
19-4-10 15:17:22.8|Debug|Api|[POST] /api/v3/notification/action/startOAuth?callbackUrl=https%3A%2F%2FTLD.EXAMPLE.TLD%2Foauth.html: 200.OK (7 ms)
19-4-10 15:17:23.1|Debug|Api|[POST] /api/v3/notification/action/continueOAuth?id=1379523069&code=bjzrvs317xmfnku8jeed0j41q&trusted=false&clientIdentifier=6ebefdc4-f047-465e-905b-26a160a7e09c&location=%5Bobject%20Object%5D&expiresIn=1799&createdAt=2019-04-10T20%3A17%3A22.396Z&expiresAt=2019-04-10T20%3A47%3A22.392Z&authToken=&callbackUrl=https%3A%2F%2FTLD.EXAMPLE.TLD%2Foauth.html: 200.OK (5 ms)
19-4-10 15:17:25.9|Debug|PlexTvProxy|Url: https://plex.tv/api/v2/pins/1379523069?X-Plex-Client-Identifier=6ebefdc4-f047-465e-905b-26a160a7e09c&X-Plex-Product=Sonarr&X-Plex-Platform=Windows&X-Plex-Platform-Version=7&X-Plex-Device-Name=Sonarr&X-Plex-Version=3.0.1.430
19-4-10 15:17:26.5|Debug|Api|[POST] /api/v3/notification/action/getOAuthToken?oauthUrl=https%3A%2F%2Fapp.plex.tv%2Fauth%2F%23!%3FclientID%3D6ebefdc4-f047-465e-905b-26a160a7e09c%26forwardUrl%3Dhttps%253A%252F%252FTLD.EXAMPLE.TLD%252Foauth.html%26code%3Dbjzrvs317xmfnku8jeed0j41q%26context%255Bdevice%255D%255Bproduct%255D%3DSonarr%26context%255Bdevice%255D%255Bplatform%255D%3DWindows%26context%255Bdevice%255D%255BplatformVersion%255D%3D7%26context%255Bdevice%255D%255Bversion%255D%3D3.0.1.430&pinId=1379523069: 200.OK (638 ms)
19-4-10 15:17:28.6|Debug|PlexServerService|Getting sections from Plex host: localhost
19-4-10 15:17:28.6|Debug|PlexServerProxy|Url: https://localhost:32400/library/sections?X-Plex-Client-Identifier=6ebefdc4-f047-465e-905b-26a160a7e09c&X-Plex-Product=Sonarr&X-Plex-Platform=Windows&X-Plex-Platform-Version=7&X-Plex-Device-Name=Sonarr&X-Plex-Version=3.0.1.430&X-Plex-Token=EAvLqD7uswmuMFzEhmzh
19-4-10 15:17:29.6|Error|PlexServerService|Unable to connect to Plex Server
[v3.0.1.430] NzbDrone.Core.Notifications.Plex.PlexException: Unable to connect to Plex Media Server
at NzbDrone.Core.Notifications.Plex.Server.PlexServerProxy.ProcessRequest(HttpRequestBuilder requestBuilder) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerProxy.cs:line 198
at NzbDrone.Core.Notifications.Plex.Server.PlexServerProxy.GetTvSections(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerProxy.cs:line 39
at NzbDrone.Core.Notifications.Plex.Server.PlexServerService.GetSections(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerService.cs:line 68
at NzbDrone.Core.Notifications.Plex.Server.PlexServerService.Test(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerService.cs:line 164
19-4-12 04:42:32.1|Error|PlexServerService|Unable to connect to Plex Server
[v3.0.1.439] NzbDrone.Core.Notifications.Plex.PlexException: Unable to connect to Plex Media Server
at NzbDrone.Core.Notifications.Plex.Server.PlexServerProxy.ProcessRequest(HttpRequestBuilder requestBuilder) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerProxy.cs:line 198
at NzbDrone.Core.Notifications.Plex.Server.PlexServerProxy.GetTvSections(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerProxy.cs:line 39
at NzbDrone.Core.Notifications.Plex.Server.PlexServerService.GetSections(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerService.cs:line 68
at NzbDrone.Core.Notifications.Plex.Server.PlexServerService.Test(PlexServerSettings settings) in M:\BuildAgent\work\63739567f01dbcc2\src\NzbDrone.Core\Notifications\Plex\Server\PlexServerService.cs:line 164
19-4-12 04:42:32.2|Warn|SonarrErrorPipeline|Invalid request Validation failed:
-- Unable to connect to Plex Server
Not seeing any debug messages there, this is just the error and a validation warning being logged.
Assuming Secure connections are allow on the PMS side (they are preferred by default) I don’t see any issues with this request, but unfortunately the logs don’t indicate if it failed due to an error response from PMS or something else, we’ll have to add more logging for that.