Server Version#: 1.32.5.7328-2632c9d3a (App was updated Jul-27-2023 and has worked up until recently)
Iphone Plexamp Version#: 4.8.2 Plex Media Server log.zip (3.3 MB)
Assustor NAS and it is runing the same version as listed in App library.
My media files are no longer listed in Library and it acts like I don’t have a media server even though I accesses Plex Media Server icon on my NAS home screen. When I click on Your Media it wants me to download a Plex Media Server to the App that is the Plex Media Server. I think I’m missing someing.
Media is visible and present on the NAS file explorer, but content is not visible within Plex. I haven’t re-installed, because if that’s first step is there a way to maintain the libraries and metadata from the Plex Media Server.
I see all the correct devices on the authorized devices screen on my online account. On Plex Amp the Source show’s ‘???’ and it doesn’t see any media servers. Home on the app shows me text of my recenly accessed and new music and other, but no images or icons. I can play my downloaded music on my phone.
I seem to have the same problem with Plex running on my Asustor AS5304T. The problem seems to have started after I recently upgraded Asus ADM from 4.2.2.RI61 to 4.2.3.RK91. I see the libraries, but they are greyed out and not accessible. Error messages seem to indicate that I’m not authorized on the server. In another forum post I found a reference to a script named plex-claim-server (for a different NAS type). But it’s a bash script and there’s no bash installed. Before I venture further into this script and bash, I’m wondering if anyone can explain how to reclaim server ownership on Asus NAS. uname says it’s running Linux 5.13.x. Plex clients (like on a Samsung smart TV) can still access the libraries just fine. I just can’t get access to the server. Thanks much.
Very interesting, I also am using Asustor AS5304T and I also recently upgraded to 4.2.3.RK91. I only see my libraries on my music library in my PlexAmp library on my phone, but all images are grey. I wonder if Asus is not give me access to the Plex library too. Thanks for sharing your commonalities.
I seem to have made some progress in my troubleshooting, but haven’t found the final fix yet. Following the advice in Not Authorized / Unable to claim server - FreeNAS I was able to get the Plex server to a point where it actually tells me ‘This server is unclaimed and not secure’ and shows me the ‘Claim Server’ button. However, clicking ‘Claim Server’ doesn’t do anything. Going into the server log file, I see requests going out to plex.tv using an old IP address: ‘Request: [192.168.1.245:58262 (Subnet)] POST …’ 192.168.1.245 used to be my server’s DHCP provided IP address a long time ago, until I changed it to fixed address 192.168.1.21. Now I need to figure out, where the server on my NAS pulls this old address from and how to fix it. Anyone have a pointer? I hope that is the actual problem.
@dbirch Thank you very much, it may be to the weekend until I have enough time to firgure this out. As you’ll see, I’m a novice, but can you advise how we would typically access a terminal window on a NAS?
So how do I claim the server? Not sure if I’m on the right track with the IP address thought. Here’s the log file snippet that I get every time I try to claim it.
Sep 06, 2023 18:53:06.624 [140533899615032] DEBUG - [Req#ff/HCl#34] HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
Sep 06, 2023 18:53:06.682 [140533920746296] WARN - [HttpClient/HCl#34] HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443 after 57 ms: Couldn't connect to server)
Sep 06, 2023 18:53:06.682 [140533899615032] WARN - [Req#ff] FeatureManager: Couldn't get features. Trying again soon.
Sep 06, 2023 18:54:38.713 [140533922872120] DEBUG - Request: [192.168.1.245:58262 (Subnet)] POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxxXtwNUA (3 live) #101 GZIP
Sep 06, 2023 18:54:38.713 [140533922872120] DEBUG - [Req#101/HCl#35] HTTP requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxXtwNUA
Sep 06, 2023 18:54:38.768 [140533920746296] WARN - [HttpClient/HCl#35] HTTP error requesting POST https://plex.tv/api/claim/exchange?token=xxxxxxxxxxxxxxxxxxxxXtwNUA (7, Couldn't connect to server) (Failed to connect to plex.tv port 443 after 55 ms: Couldn't connect to server)
Sep 06, 2023 18:54:38.768 [140533922872120] DEBUG - [Req#101] MyPlex: Did token exchange for claim (returnCode: -7)
Sep 06, 2023 18:54:38.797 [140533922872120] DEBUG - [Req#101] MyPlex: Got a token poked, let's act on it.
Sep 06, 2023 18:54:38.797 [140533922872120] DEBUG - [Req#101/HCl#36] HTTP requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=
Sep 06, 2023 18:54:38.997 [140533920746296] WARN - [HttpClient/HCl#36] HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443 after 199 ms: Couldn't connect to server)
Sep 06, 2023 18:54:38.997 [140533922872120] DEBUG - [Req#101] [Analytics] Using cached data for privacy preferences
Sep 06, 2023 18:54:38.998 [140533922872120] DEBUG - [Req#101/HCl#38] HTTP requesting GET https://plex.tv/api/v2/release_channels?X-Plex-Token=
Sep 06, 2023 18:54:39.198 [140533920746296] WARN - [HttpClient/HCl#38] 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 after 199 ms: Couldn't connect to server)
Sep 06, 2023 18:54:39.198 [140533922872120] DEBUG - [Req#101] [AutoUpdateRequestHandler] Using cached data for update channels
Sep 06, 2023 18:54:39.198 [140533922872120] DEBUG - [Req#101/HCl#39] HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
Sep 06, 2023 18:54:39.398 [140533920746296] WARN - [HttpClient/HCl#39] HTTP error requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443 after 199 ms: Couldn't connect to server)
Sep 06, 2023 18:54:39.398 [140533922872120] WARN - [Req#101] FeatureManager: Couldn't get features. Trying again soon.
Sep 06, 2023 18:54:39.399 [140533954435896] DEBUG - Completed: [192.168.1.245:58262] 500 POST /myplex/claim?token=xxxxxxxxxxxxxxxxxxxxXtwNUA (3 live) #101 GZIP 686ms 522 bytes (pipelined: 1)
Sep 06, 2023 18:54:39.464 [140533884906296] DEBUG - [Req#101/MediaProviderManager] we had 0 cloud providers online, we now have 0
To get the UserCredentialReset.sh script to run, I had to put a link to /volume0/usr/builtin/bin/curl into /usr/local/bin. But then the script failed with ‘ERROR: Could not get credentials from plex.tv (Error: 7)’ after I entered my claim token.
The Plex claim-xxxxxxxxx token expired before using it in the script.
( The token is only valid for 5 minutes from the time it’s given to you… Think of it as “4 minutes” safely )
That’s the problem. WAN IP shows as – and I get the error ‘Unable to obtain ASUSTOR ID’. I’m working with Asustor Support (I have two tickets open with them, one for the Plex problem and one for the WAN IP problem). The initial steps they provided to fix the WAN IP problem did not resolve the problem. Waiting for next steps now. Initially Asustor Support said that the Plex problem was unrelated to the WAN IP problem. Hence I worked on that before resolving the WAN IP problem. Thanks for confirming the relationship. Now I’ll work on the WAN IP problem first.
Thanks for the tips. Yes, the router can reach plex.tv just fine. The problem started right after the NAS upgraded ADM automatically from 4.2.2.RI61 to 4.2.3.RK91. Asus support stated that multiple users had reported that their NAS could not connect to the Internet anymore after this upgrade. But the first set of steps they provided to fix the problem didn’t work. Now I’m waiting for next steps. Unfortunately it always takes a day to get a response, since they seem to be located in an Asian timezone. I hope they can either provide steps to fix or determine that this is a bug in this new ADM version.
Hello Group, Thank you to all. I believe my problem was a NAS to internet problem. I followed the steps in the below Asus link to verify my internet. Everything looked okay, but I clicked though the configure steps and a few minutes latter everything was showing and present in my Plex Server. So I’m theorizing that Plex couldn’t get to the internet to verify my credentials.
