Try to claim server and it fails with no information.
Signed back into Plex client and tried again.
Tried running claimpms.sh on both NAS and laptop to claim server, and both failed.
I don’t understand why plex has a problem connecting to its server from my NAS, and I don’t understand the errors provided in the logs to debug. I’ve attached the logs. This issues keeps happening to me every other month or so, and with almost every plex update. Anyone have any ideas?
I can see where PMS is unable to communicate with Plex.tv.
“Host Unreachable” means there is a problem with the networking.
In this case, I recommend checking -
Default adapter
Gateway device
Confirm the NAS can indeed get to the internet.
Jun 26, 2021 13:06:39.571 [0x7fad8ab5cb38] WARN - HTTP error requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443: Host is unreachable)
Jun 26, 2021 13:06:39.571 [0x7fad8ab5cb38] DEBUG - [AutoUpdateRequestHandler] Using cached data for update channels
Jun 26, 2021 13:06:39.572 [0x7fad8ab5cb38] DEBUG - HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
Jun 26, 2021 13:06:47.021 [0x7fad8abc5b38] DEBUG - player cdk47gwxmhkwmlufq226gtbh was last refreshed 30 seconds ago
Jun 26, 2021 13:06:48.597 [0x7fad8ab5cb38] ERROR - Error issuing curl_easy_perform(handle): 7
Jun 26, 2021 13:06:48.597 [0x7fad8ab5cb38] WARN - HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443: Host is unreachable)
Hmm, I’ve checked the default gateway. It is set to the correct IP and it’s the same as the Plex Server is accessible at. How can I check the default adapter and gateway device? Can you provide some more details as to what they should be set to and how to check those values? I ssh-ed into the NAS and was able to curl an external website, but not sure if that is actually verifying the NAS can get to the internet. It seems like it’s connected.
Yeah I normally check things using the GUI. I’m comfortable with the command-line work. If you can me provide some steps to follow / things to check, I’ll go through them and report back.
So I’m getting an html 500 response status when I attempt the curl. Followed all the steps. Stopped Plex, deleted Preferences, restarted Plex, got a new token on the web from plex.tv/claim (after prompt to sign in). Then this
curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-[mytoken]'
<html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html>
It sits idle for awhile as you said, then returns a 500 status. I tried testing the curl against other sites and they return status ok. E.g. curl -X GET "https://httpbin.org/get" -H "accept: application/json" or curl -X GET "https:/www.google.com"
Hello @ChuckPa, I’m experiencing the same issue here. Following your steps, I get the same error as @havok2063 : Internal Server Error. How did you fix it? Sounds like the server can’t reach plex.tv endpoint but it’s very strange, it worked correctly yesterday and I did not make any modifications to the server or to plex configs. Thank you
I’m getting exactly the same issue. I’m using Synology, here’s the details from the logs about my system:
Aug 22, 2021 14:04:25.304 [0xb3902d90] INFO - Plex Media Server v1.24.0.4930-ab6e1a058 - Synology DS214play i686 - build: linux-x86 synology - GMT -07:00
Aug 22, 2021 14:04:25.307 [0xb3902d90] INFO - Linux version: DSM 6.2.4.25556-0, language: en-US
Aug 22, 2021 14:04:25.307 [0xb3902d90] INFO - Processor Intel(R) Atom™ CPU CE5335 @ 1.60GHz
Aug 22, 2021 14:04:25.307 [0xb3902d90] INFO - Compiler is - Clang 11.0.1 (https://plex.tv e0c29d5827bc4eaaa2ceb882cbeed224b0960173)
Not sure where the internal server error logs are being written. This whole claiming server business is a real PITA, I’ve wasted too many hours trying to get this stuff to work. I’m still using DMS 6.2.4 and have not attempted a DSM 7 upgrade.
Also, I upgraded to what I thought was the latest Server but the webpage still thinks there’s an update.
@ChuckPa@DevPan FWIW, I’m still having the same problem. Upgraded to plex 1.24.1.4931-1a38e63c6, still using DSM 6. Has there been any discussion on possible ideas of why I can’t manually reclaim the server with the curl command? I basically can’t access any of my media anymore via plex.
@trumpy81 I’ve tried that before, and already, and it doesn’t work. But I can try it again. The Claim Server button just spins and does nothing. I always get some sort of the following error in my log,
Aug 28, 2021 08:20:05.281 [0x7f3554fc9b38] ERROR - Error issuing curl_easy_perform(handle): 7
Aug 28, 2021 08:20:05.282 [0x7f3554fc9b38] WARN - HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443: Host is unreachable)
Aug 28, 2021 08:20:05.282 [0x7f3554fc9b38] WARN - FeatureManager: Couldn't get features. Trying again soon.
I’ve attached the latest logs to my last post. You can also take a look at the logs attached in my very first post to see the logs from a while back, to compare.
Ok, I can try that. I have/had custom rules set up on my firewall. Can you tell me what I should set for the Firewall rules to allow Plex through? In particular, under the Port - Custom settings, and which regions I need to check under the Source IP - Location settings? Currently, under Port-Custom, I have Destination Port set to TCP for 32400. Under Source IP - Location, I have the regions selected for U.S, Great Britain, and Ireland.
And for Port Forwarding, is it preferable to set that on my router, or in the Synology, or both? Normally I set it in my router, and don’t set it up as a rule in the Synology.
)