Problems with Plex Notifications & Sonarr - logs/traces included

cbgj · January 28, 2017, 12:03pm

Hello, i no matter what i try i cant seem to get Sonarr to talk to PMS for notifications. I have triple checked the username & password is correct.

Trace:

   3220 17-1-28 12:56:05.0|Error|PlexServerService|Unable to connect to Plex Server: Invalid Token - Update your username and password                                                                             
   3221                                                                                                                                                                                                            
   3222 [v2.0.0.4472] NzbDrone.Core.Notifications.Plex.PlexAuthenticationException: Invalid Token - Update your username and password                                                                              
   3223   at NzbDrone.Core.Notifications.Plex.PlexServerProxy.GetAuthenticationToken (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) <0x40fd2070 + 0x00237> in <filename unknown>:0                 
   3224   at NzbDrone.Core.Notifications.Plex.PlexServerProxy.GetPlexServerRequest (System.String resource, Method method, NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) <0x40fd1890 + 0x0009f> in 
   3224 <filename unknown>:0 
   3225   at NzbDrone.Core.Notifications.Plex.PlexServerProxy.GetTvSections (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) <0x40fd1380 + 0x0002b> in <filename unknown>:0                          
   3226   at NzbDrone.Core.Notifications.Plex.PlexServerService.GetSections (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) <0x40fd1240 + 0x0004c> in <filename unknown>:0                          
   3227   at NzbDrone.Core.Notifications.Plex.PlexServerService.Test (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) <0x40fd0fe0 + 0x00037> in <filename unknown>:0                                 
   3228                                                                                                                                                                                                            
   3229 17-1-28 12:56:05.0|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:                                                                                                                           
   3230  -- Incorrect username or password

I have Couchpotato & Plexrequests talking to the PMS server just fine, i just cant seem to find out what makes Sonarr not play nice

OS: Debian 8.7.1
Script: QuickBox.io
Sonarr: 2.0.0.4472
Mono Version: 4.2.3 (Stable 4.2.3.4/832de4b Wed Mar 16 13:19:08 UTC 2016)¨
Plex Media Server: 1.3.3.3148 (running at port 31400)

markus101 · January 28, 2017, 4:17pm

Not enough logs there (we’d need more than a snippet from the trace logs).

You’re also not running mono with the --debug switch so we can’t see which lines that error is coming from.

Do you have your Plex account set to only allow logins via your email address?

cbgj · January 29, 2017, 12:53am

Hm, im not sure how to run mono with --debug for Sonarr when its running via QuickBox.

I have tried my Plex username & my email, none of them work.

markus101 · January 29, 2017, 4:07am

It’d need to be set in whatever startup script starts it. Never heard of QuickBox so I have no idea what you’d need to do.

Regardless we’ll need to see the full trace logs including that error to advise any further.

cbgj · January 29, 2017, 8:54am

I found the systemd startup script, mono with --debug & trace-logs:

Debug:


17-1-29 09:35:51.7|Debug|Api|[PUT] /api/config/host: 202.Accepted (73 ms)                                                                                                                                          
17-1-29 09:35:52.0|Debug|Api|[GET] /api/health: 200.OK (1 ms)                                                                                                                                                      
17-1-29 09:35:58.3|Debug|Api|[GET] /api/notification/schema: 200.OK (61 ms)                                                                                                                                        
17-1-29 09:36:19.5|Debug|PlexServerService|Getting sections from Plex host: localhost                                                                                                                              
17-1-29 09:36:20.1|Debug|PlexServerProxy|Authentication Response: {"user":{"id":9336074,"uuid":"1aa5c35767d0e48d","email":"email@example.com","joined_at":"2016-05-15T20:09:01.000Z","username":"(removed)","title":
"netsensenpai","thumb":"https://plex.tv/users/1aa5c35767d0e48d/avatar","authToken":"valid but censored token","authentication_token":"valid but censored token","subscription":{"active":false,"status":"Inactive","plan":n
ull,"features":[]},"roles":{"roles":[]},"entitlements":[],"confirmedAt":"2017-01-23T17:45:48.000Z","forumId":0,"rememberMe":false}}
17-1-29 09:36:20.1|Error|PlexServerService|Unable to connect to Plex Server: Unauthorized - Username or password is incorrect                                                                                      
                                                                                                                                                                                                                   
[v2.0.0.4472] NzbDrone.Core.Notifications.Plex.PlexAuthenticationException: Unauthorized - Username or password is incorrect                                                                                       
  at NzbDrone.Core.Notifications.Plex.PlexServerProxy.CheckForError (IRestResponse response, NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x000e0] in M:\BuildAgent\work\6c3239faf2b92630\src\Nzb
Drone.Core\Notifications\Plex\PlexServerProxy.cs:266 
  at NzbDrone.Core.Notifications.Plex.PlexServerProxy.GetTvSections (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00032] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications
\Plex\PlexServerProxy.cs:45 
  at NzbDrone.Core.Notifications.Plex.PlexServerService.GetSections (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00016] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications
\Plex\PlexServerService.cs:69 
  at NzbDrone.Core.Notifications.Plex.PlexServerService.Test (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00000] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Plex\P
lexServerService.cs:169 
                                                                                                                                                                                                                   
17-1-29 09:36:20.2|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:                                                                                                                                   
 -- Incorrect username or password                                                                                                                                                                                 
17-1-29 09:36:20.2|Debug|Api|[POST] /api/notification/test: 400.BadRequest (751 ms)

Trace:

17-1-29 09:43:16.6|Debug|PlexServerService|Getting sections from Plex host: localhost                                                                                                                              
17-1-29 09:43:16.6|Error|PlexServerService|Unable to connect to Plex Server: Invalid Token - Update your username and password                                                                                     
                                                                                                                                                                                                                   
[v2.0.0.4472] NzbDrone.Core.Notifications.Plex.PlexAuthenticationException: Invalid Token - Update your username and password                                                                                      
  at NzbDrone.Core.Notifications.Plex.PlexServerProxy.GetAuthenticationToken (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00062] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Noti
fications\Plex\PlexServerProxy.cs:231 
  at NzbDrone.Core.Notifications.Plex.PlexServerProxy.GetPlexServerRequest (System.String resource, Method method, NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00026] in M:\BuildAgent\work\6c
3239faf2b92630\src\NzbDrone.Core\Notifications\Plex\PlexServerProxy.cs:216 
  at NzbDrone.Core.Notifications.Plex.PlexServerProxy.GetTvSections (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00000] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications
\Plex\PlexServerProxy.cs:40 
  at NzbDrone.Core.Notifications.Plex.PlexServerService.GetSections (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00016] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications
\Plex\PlexServerService.cs:69 
  at NzbDrone.Core.Notifications.Plex.PlexServerService.Test (NzbDrone.Core.Notifications.Plex.PlexServerSettings settings) [0x00000] in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Notifications\Plex\P
lexServerService.cs:169 
                                                                                                                                                                                                                   
17-1-29 09:43:16.6|Trace|NzbDroneErrorPipeline|Handling Exception                                                                                                                                                  
17-1-29 09:43:16.6|Warn|NzbDroneErrorPipeline|Invalid request Validation failed:                                                                                                                                   
 -- Incorrect username or password                                                                                                                                                                                 
17-1-29 09:43:16.6|Trace|Http|Res: 85 [POST] /api/notification/test: 400.BadRequest (14 ms)                                                                                                                        
17-1-29 09:43:16.6|Debug|Api|[POST] /api/notification/test: 400.BadRequest (14 ms)

markus101 · January 29, 2017, 7:28pm

We still need the full file, not the snippet.

cbgj · January 31, 2017, 1:01am

Ok, ill set it in debug mode again tomorrow, sorry. All the other errors are some miss-maped episodes that i cant get rid of in the log.

The logs are still there from the first time i ran debug and trace, so zipped em all down here: http://gofile.me/2w0D8/dSL3d8t3I

The link will only be active for 24hrs and the password is sonarr.

markus101 · January 31, 2017, 4:08am

<html><head>
<title>401 Unauthorized</title>
</head><body>
<h1>Unauthorized</h1>
<p>This server could not verify that you
are authorized to access the document
requested.  Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.</p>
<hr>
<address>Apache/2.4.10 (Debian) Server at localhost Port 31400</address>
</body></html>

Why is apache throwing an error here?
Are you using a reverse proxy?
Typically PMS runs on port 32400, not 31400 are you using the correct port?

cbgj · January 31, 2017, 5:51am

The QuickBox script obfuscates all normal access ports such as SSH, PMS and so on. So 31400 is correct, and works for other services such as couchpotato. So yes, its running behind a reverse proxy.

Every service under QuickBox is protected by .htaccess, thats just me typing the wrong password.

markus101 · January 31, 2017, 6:12pm

Wrong password for what?
Is your reverse proxy stripping the Plex authentication token before passing it Plex?
Sonarr is able to authenticate to Plex.tv to get a token, but it fails when communicating to the server itself.

cbgj · January 31, 2017, 8:50pm

Wrong .htaccess password, just me doing a typo when accessing the /sonarr url.

I do not know if it strips it or not. Could you copy out the relevant parts of the log so i can copy them to the QuickBox forum? If the problem is on their part i will continue my troubleshooting over there.

markus101 · January 31, 2017, 11:07pm

That response came from the request to plex though, that means the reverse proxy dropped the connection because the password was wrong, though Sonarr has no way to actually set it.

If Sonarr receives a 401 response it’s going to assume the username or password is wrong, so the token is invalid, but if your reverse proxy is throwing back the 401 and it’s not even reaching Plex Media Server Sonarr wouldn’t know any different and throw the same error back.

Either bypass the proxy and test or allow Sonarr to connect through without requiring authentication.

Not much in the logs beyond the error I posted above, I’m 99% sure this is a problem with your reverse proxy and not anything to do with Sonarr.

cbgj · February 1, 2017, 4:19pm

Ok, thank you very much for looking into the logs @markus101! I have started a thread over at the QuickBox forum to see if they can find the problem.

system · April 2, 2017, 4:19pm

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.