I recently updated from plexmediaserver_1.0.0.2261-a17e99e_amd64 to plexmediaserver_1.1.3.2700-6f64a8d_amd64 and am unable to claim my server.
When I originally updated the server, I was unable to login remotely to change any settings. I opened up Preferences.xml and added allowedNetworks= with my local IP and started the server. That allowed me to connect, but the web app said I needed to upgrade, although the version showed as Version 1.1.3.2700. I decided to sign out of the server and re-sign back in. Whenever I attempt enter my username/password and hit sign in, I get the message There was a problem signing in to Plex.
Watching my browser traffic, I’m getting a 500 response back from http://10.4.0.3:32400/myplex/claim and a 406 from http://10.4.0.3:32400/myplex/account. When I do hit sign-in although I see these errors, the Devices section shows up, but it doesn’t look like I actually claimed the server. I can’t enable things like remote access. When I look at devices, I see the old version of PMS on the 1.0.0 version.
What should I do? I’ve tried restarting PMS.
I have the same issue with PMS 1.1.3 on Drobo 5N.
This is becoming super frustrating. Downgrading doesn’t help as I cannot access the server locally because allowedNetworks isn’t respected on previous version when you have plex home enabled.
Sep 05, 2016 11:00:35.065 [0x7fa6767ff700] DEBUG - Completed: [127.0.0.1:42693] 200 GET /status/sessions (9 live) 0ms 255 bytes Sep 05, 2016 11:00:36.378 [0x7fa6767ff700] DEBUG - Request: [10.4.6.9:36595 (Allowed Network)] POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxxLgJ7so (9 live) GZIP Sep 05, 2016 11:00:36.379 [0x7fa66e7fd700] DEBUG - HTTP requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxLgJ7so Sep 05, 2016 11:00:36.381 [0x7fa66e7fd700] ERROR - Error issuing curl_easy_perform(handle): 7 Sep 05, 2016 11:00:36.381 [0x7fa66e7fd700] WARN - HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxLgJ7so (0, No error) (Failed connect to plex.tv:443; Connection refused) Sep 05, 2016 11:00:36.382 [0x7fa66e7fd700] DEBUG - MyPlex: Did token exchange for claim (returnCode: -7) Sep 05, 2016 11:00:36.382 [0x7fa66e7fd700] DEBUG - Need to restart some processes because of a change to the security environment. Sep 05, 2016 11:00:36.382 [0x7fa66e7fd700] DEBUG - MyPlex: Got a token poked, let's act on it. Sep 05, 2016 11:00:36.382 [0x7fa66dffc700] DEBUG - Stopping [com.plexapp.system]. Sep 05, 2016 11:00:36.382 [0x7fa66dffc700] DEBUG - [com.plexapp.system] Killing. Sep 05, 2016 11:00:36.382 [0x7fa66e7fd700] DEBUG - Sync: onMyPlexSignOut Sep 05, 2016 11:00:36.382 [0x7fa66dffc700] DEBUG - Starting file watcher for com.plexapp.system Sep 05, 2016 11:00:36.382 [0x7fa66dffc700] DEBUG - Plugin: not setting user token for plugin Sep 05, 2016 11:00:36.384 [0x7fa66dffc700] DEBUG - Spawned plug-in com.plexapp.system with PID 17654 Sep 05, 2016 11:00:36.384 [0x7fa66dffc700] DEBUG - [com.plexapp.system] Sending command: GET /:/prefixes
I see lots of this in the logs whenever I try to claim the server.
So I solved it. Yay. I thought it strange that plex was getting connection refused from plex.tv as per the log messages above. I enabled Allow Plex Media Server tokens in logs, attempted the claiming, grabbed the token and headers for the https://plex.tv/api/claim POST from the logs, and recreated the call on one of my machines. And that worked just fine.
Turns out my firewall had an entry (an incorrect one) for not allowing outbound traffic on plex’s subnet to any IP’s in Europe (and more importantly in Ireland).
After updating to allow Amazon IP’s, things have worked swimmingly.
tl;dr
User error.
