I hope you can help. My trouble shooting has failed!
About 48 hours ago my server wasn’t reachable via the Plex IOS app. So i logged on to RDP to check if the service application had crashed. It hadn’t but the server was stating it needed to be claimed to stay secure. I clicked into settings>general and my plex account details had gone!
So i clicked claim and nothing happened. It I had to restart the server to get the system to claim it. Ever since then its been un-claiming its self every 1-2 hours.
I have tired all the network test, ports, firewall etc. I have also logged out of all devices on my plex account, that hasn’t helped either.
I have turned on verbose logging but I cannot see any entries that might explain (But i’m no expert)
Can anyone help? Even shed some light on what might be causing this?
I also see some curl failures in the logs going to plex.tv, it’s been happening since the last few days. My server will stay logged in and then decide to log itself out.
Mar 08, 2018 13:13:34.132 [0x7fb2d4bff700] DEBUG - HTTP requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxx4cpLJv
Mar 08, 2018 13:13:34.134 [0x7fb2d4bff700] ERROR - Error issuing curl_easy_perform(handle): 7
Mar 08, 2018 13:13:34.134 [0x7fb2d4bff700] WARN - HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxx4cpLJv (0, No error) (Failed connect to plex.tv:443; Connection refused)
Mar 08, 2018 13:13:34.135 [0x7fb2d4bff700] DEBUG - MyPlex: Did token exchange for claim (returnCode: -7)
Mar 08, 2018 13:13:34.135 [0x7fb2d4bff700] DEBUG - MyPlex: Got a token poked, let's act on it.
Mar 08, 2018 13:13:34.135 [0x7fb2d4bff700] DEBUG - Need to restart some processes because of a change to the security environment.
Mar 08, 2018 13:13:34.135 [0x7fb2d4bff700] DEBUG - HTTP requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=
Mar 08, 2018 13:13:34.137 [0x7fb2d4bff700] ERROR - Error issuing curl_easy_perform(handle): 7
I am running plexmediaserver-1.12.0.4829-6de959918.x86_64 however I also downgraded to each version prior to that.
I’ve had to reclaim several times, at one point claiming was failing as well:
HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxx4cpLJv (0, No error) (Failed connect to plex.tv:443; Connection refused)
Things seem ok for now, but this has been off/on the last few days.
I’m using a self-signed certificate however that has never been a problem before and I don’t see it being the problem. Each time I had to ssh tunnel to localhost to try and claim / set things up again via the web interface.
Is there a way we can get plex staff to take a look?
I only started having this problem when i updated to the newest version for my Linux headless machine (Centos 7)
@“hemen.mehta@gmail.com” said:
Is there a way we can get plex staff to take a look?
I only started having this problem when i updated to the newest version for my Linux headless machine (Centos 7)
I had this issue with these versions for what it’s worth:
I have not rolled back further than 1.11.3 but logs indicate there being a problem on the auth/network end of some service on the plex.tv side though I haven’t done any packet traces yet and right now on current 1.12.0 it appears to be working again (for now).
e.g.
Mar 08, 2018 13:13:34.132 [0x7fb2d4bff700] DEBUG - HTTP requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxx4cpLJv
Mar 08, 2018 13:13:34.134 [0x7fb2d4bff700] ERROR - Error issuing curl_easy_perform(handle): 7
Mar 08, 2018 13:13:34.134 [0x7fb2d4bff700] WARN - HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxx4cpLJv (0, No error) (Failed connect to plex.tv:443; Connection refused)
Mar 08, 2018 13:13:34.135 [0x7fb2d4bff700] DEBUG - MyPlex: Did token exchange for claim (returnCode: -7)
Mar 08, 2018 13:13:34.135 [0x7fb2d4bff700] DEBUG - MyPlex: Got a token poked, let's act on it.
Mar 08, 2018 13:13:34.135 [0x7fb2d4bff700] DEBUG - Need to restart some processes because of a change to the security environment.
Mar 08, 2018 13:13:34.135 [0x7fb2d4bff700] DEBUG - HTTP requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=
Mar 08, 2018 13:13:34.137 [0x7fb2d4bff700] ERROR - Error issuing curl_easy_perform(handle): 7
This was after PMS on both 1.12.0 and 1.11.3 would decide to log itself out or become unclaimed multiple times.
@seedbbox said:
The problem seems to be solved ! I pray ! We pray !
Aye, seems ok so far (crossing fingers). There was a staff post here that said there were database problems for about 20hours or so but it’s fixed and that corresponds with when I was seeing some of the issues, though it did happen once on Sunday 2018-03-04 around noon’ish BST/IST/GMT
@carsnacks Question: If the plex-service (refers to servers of the company, and not my home server) is having issues, why would it be impacting my home service ? Is it required to have access to external networks to be able to function? (please excuse my ignorance, I know little about how it all works)
@“hemen.mehta@gmail.com” said: @carsnacks Question: If the plex-service (refers to servers of the company, and not my home server) is having issues, why would it be impacting my home service ? Is it required to have access to external networks to be able to function? (please excuse my ignorance, I know little about how it all works)
I’m no authority here but my understanding was a change was made in the 1.1x. (or whereabouts?) plexmediaserver for associating your home plex server with a plex.tv user to provide sharing and ownership, so your home server would need to be “logged in” via a plex.tv user account.
I believe you could still operate it without any association but some of the functionality like accessing it through an IoS/Android App or plex.tv portal requires this or to inherit any PlexPass benefits.
Thanks
