Asustor AS5202T Plex Setup can't add local media

Plex Media Server NAS & Devices
,
1

Server Version#: 1.30.1.6497-5fc2e0894
Player Version#: NA
I just finished installing the Plex Media server on my Asustor AS5202T NAS. After installation when I clicked on the Plex icon, it opened up a new browser page and asked me to sign in to my plex.tv account which I did. Now plex shows me Live TV, Moves & Shows, Discover and Music, but nowhere do I see the ability to add my local media from the NAS.

There is a more button and clicking on it does show me a link that says “Your Media”, but clicking on the link takes me to the ‘get-plex-media-server’ page.

Also I had a working setup on this very NAS, but recently I started seeing messages on my plex app on my Roku devices that none of my local NAS media could be accessed. So I uninstalled Plex Media Server and reinstalled it, in the hopes that a newer version would fix the issue, but now this.

2

@ChuckPa would you have an idea why?

I’m having the same issues with my Asustor.

It’s as if the Plex Media Server applet on the Asustor platform refuses to see itself as a server. I regularly get ‘you do not have permission to access this server’ - when I get around it, as above, I’m greeted with the Plex homepage. I click ‘Your Media’, which it redirects to downloading the Plex Media Server app, as if it can’t see the server partition on my NAS. I can try and make a screen recording to demonstrate?

3

Try the User Credential Reset and Server Reclaim Utility

It will unclaim/re-claim your server…

1 Like
4

Thanks, will have a look - a bit beyond my techncial abilities I think, but have started nonetheless.
Given it’s never worked, and continues to do this even when I uninstall/reinstall Plex, is it still likely to be the issue with server claiming?

5

When things work correctly, you’ll get a prompt to login to the Plex server, followed by the setup screens. Since you’re not seeing any of that, and cannot reach the server settings, it means something is going wrong.

The credential reset utility starts the process over from the beginning. It also has a different claiming method, letting you enter a code from plex.tv/claim instead of accessing the server via a web browser.

You could also try Why am I locked out of Server Settings and how do I get in?. That also resets the claiming process, but you still login / claim the server via http://server_ip_address:32400/web.

The third alternative is to completely remove Plex Media Server from the NAS, including deleting the Plex Data Folder. The downside of doing so is that any existing libraries, sharing with friends/family, etc is wiped out. It is basically the “nuclear option” and usually the last thing recommended.


Some additional info:

When first setting up a Plex server on a NAS:

  1. NAS must be using RFC-1918 addressing
    NAS IP address: 10.x.x.x; 172.16.x.x-173.31.x.x, or 192.168.x.x
  2. NAS must have a solid Internet connection and ability to reach plex.tv.
    The claiming process registers the Plex server with systems at plex.tv. If the NAS cannot communicate with plex.tv, claiming will fail.
  3. System using to claim Plex server must be on same network as NAS
    If not, use an SSH tunnel.
  4. Using an incognito/private browser window, point the browser at the IP address of the NAS.
    Ex: If NAS IP address is 10.1.2.3, use http://10.1.2.3:32400/web.
    The incognito/private window bypasses any ad blockers, cookie cutters, etc that might interfere with claiming.

Those are the basics. That should let you claim your Plex server.

The process can still fail, especially if there are remnants of a prior Plex installation (an old Plex Data Folder) or if the server is accidentally claimed with the incorrect Plex account.

When claiming fails, the usual procedure is to manually un-claim / re-claim the server.

There is an older process involving editing the Plex server’s preferences.xml file: Why am I locked out of Server Settings and how do I get in?

For those familiar with the Linux CLI, the User Credential Reset and Server Reclaim Utility performs the same function. It also has an easier claiming process. Instead of #4 above, it prompts you for a claiming code from https://plex.tv/claim. You copy/paste the code and it claims your server.

6

Thank you, really appreciate the detailed response. I’ll give that a go tomorrow!

7

So looking into this, I seem to be falling at the first hurdle. I seem to be being blocked from accessing a Plex Server that doesn’t exist. I’ve never created a Plex Server before - instead installed the app and clicked on it, to log on. The manual user cred reset and server reclaim option would make sense, but I don’t think there’s a server to claim yet -or any ser creds associated with one.

When looking at https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/ - there are only 5 lines of text in my preferences.xml file.
Preferences (1).xml - Google Drive

I’ve tried deleting the Plex folders multiple times (no risk as no user files in there), but to no avail.

Is there any facility to get remote support from Plex? I can’t work out if this is a Plex setting issue, or Asustor (who will of course say it’s a plex issue)

8

So i got this resolved and hint was in something @FordGuy61 said:

“NAS must have a solid Internet connection and ability to reach plex.tv.
The claiming process registers the Plex server with systems at plex.tv. If the NAS cannot communicate with plex.tv, claiming will fail.”

In my case after the initial setup in September, I had set my Network Firewall to “Deny” any internet bound call originating from the NAS. I remembered this after reading that text from FordGuy61.

So here are the steps I undertook:

  1. Disabled the Firewall rule that was denying the outbound connection
  2. Uninstalled PMS from Asustor
  3. Deleted the “plex” share from my NAS
  4. Installed a newer version that was downloaded from the plex.tv site (as opposed to the one available from “App Central”)
  5. Waited for about 30 minutes (It downloads the entire contents of plex folder from somewhere)

So moral of the story, at least in my scenario is, when installing Plex Media Server, make sure your Plex Host can reach the plex.tv site. If it is unable to reach it, it does not realize it is a Plex Media Server.

9

Thanks, gave that a go (v1.30 on the Plex site, not 1.29 on AppCentral), deleted the Plex shared folder, reinstalled, waited 30 mins and still met with the ’ Not authorized You do not have access to this server’ message - even though no server has ever been created…

I’m at a loss… Checked the router firewall settings, opened more ports, even pinged plex.tv and IP address from my router, all fine.

I’m not authorised to access a server that hasn’t been created yet… How?

10

Rolled up my sleeves a got into shell scripting today.

Stuck on one thing… the curl, or path.

I’ve moved both the .sh file and the Preferences.xml into /volume1/Public, and while it is happy with the .sh file execution, it needs the path defined as per GitHub - ChuckPa/UserCredentialReset: User Credential Reset utility for Plex Special Usage cases.

I type in ./UserCredentialReset.sh -p "/volume1/Public/Preferences.xml, but it still can’t find it. I’ve confirmed Preferences.xml is definitely in ‘Public’, and that the path is correct. What am I missing?

Shell Scripting
Shell Scripting999×500 85.1 KB

11

@y46xm

Odd that root cannot find curl. It is usually in /usr/bin or /bin. Is it in either location on your NAS?

On my Ubuntu system:

root@osage:~# which curl
/usr/bin/curl

or

root@osage:~# ls -l /usr/bin/curl
-rwxr-xr-x 1 root root 260328 Oct 18 11:35 /usr/bin/curl

If it is not in /usr/bin or /bin, you can search for it. This searches the entire system, starting at the root directory, /.

root@osage:~# find / -name curl
/usr/bin/curl

Also, issue the echo $PATH command. What is displayed?

root@osage:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

You can add the location for curl to your path. That should let you run the reset utility.

For example, if curl is in /usr/abcd, use export PATH=$PATH:/usr/abcd.

root@osage:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin

root@osage:~# export PATH=$PATH:/usr/abcd

root@osage:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/usr/abcd
12

Thank you - Managed to complete the above, curl is now located in
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/volume0/usr/builtin/bin/curl

Does it matter that it’s in /volume0/? I can’t see this from a Linux UI level.

What I’m struggling with is how to add the curl location to the path, what instruction am I giving to the command line as part of the usercredentialreset.sh execution? I’m still getting the ‘utilty requires curl’ error message.

What does the command look like for run the entire request?

13

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