Plex Media Server - Not Authorized You Do Not Have Access To This Server

I have to join the frustration, sorry. Just installed PlexMediaServer-1.25.0.5246-cb2507e4d-x86_64_DSM7.spk on a new DS920+ with a claim token. I managed to see the web interface once, but now I keep hitting the “not authorized” wall.

Access is only internally on the local network.

Using the local machine name as in http://ds1:32400/web/ hits the wall

Using the local IP as in http://192.168.0.36:32400/web/ runs through the setup.

The DSM is not exposed to the Internet, not using quick connect.

Folks:

  1. When the server is ON YOUR LAN
  2. Turn QuickConnect OFF until AFTER PMS is configured

(DSM 7 changed the behavior. Notice how it’s a URL now and not the IP address ? The URL forces your LAN connection to be a WAN/Remote connection which Plex never allows before setup is complete)

Let me know if this doesn’t remedy the issue.

3 Likes

I’m joining. I’ve tried everything.

  1. I installed PMS(PlexMediaServer-1.25.0.5282-2edd3c44d-aarch64_DSM7.spk) on my
    DS420j with token. So when I login to https://app.plex.tv I can see the authorization listed, however I can’t see any servers there.
  2. I get “Not authorized You do not have access to this server” -like everyone else.
  3. I have logged out of Synology account, for QuickConnect, that didn’t work. I tried unregistering QuickConnect, and then log in to https://192.168.10.189:5001, and then I get this error instead: “Something went wrong An unexpected error occurred.” (and how do I register quickconnect, or enable it again?)
  4. I then REINSTALLED PMS again, with tokens but at https://192.168.10.189:5001 instead of quick connect, just in case. Same error: “Something went wrong An unexpected error occurred.”

Help?!

Is Plex is installed & running per Synology Package Center?

If so, point your browser directly at your NAS: http://192.168.10.189:32400/web. You might also try an incognito/private window to disable any browser add-ons.

You might see a message saying “This application is at 192.168.10.189 and is not hosted by Plex…” That is just a notice that you are logging directly into Plex on your NAS, not via app.plex.tv.

I tried now, and it said just that:
This application is at 192.168.10.189 and is not hosted by Plex.

But then logging in, same error:
Something went wrong

An unexpected error occurred.

So to answer your question: it might be running, but it isn’t set up.

So now what?

“not hosted by Plex” → The server is hosted by You. It’s an anti-phishing warning.

Click the OK - continue through it. It will remember.

I know, and I did. Else I wouldn’t have gotten the error that I got:
Something went wrong

An unexpected error occurred

Using FileStation, go to the Logs directory, Right-Click → Compress to Logs.zip

Attach that ZIP here please.

Logs.zip (102.0 KB)

@stefanw1337

I’m seeing the plex/web load but not seeing any authentication requests.

There are several load sequences, each with the plex/web closing the connection.

Do you have a JS blocker in the brower?

(Are there other logs there? It would be nice to see the previous ones – before updating)

I am also not seeing the server claimed.

Would you consider using the “Plex Claim Token” installation method?

Yes, I have uBlock Origin. But last attempt I went private browsing.

I did use the Plex Claim Token method, yes. But let me reinstall and disable all blockers, that might have balls’d it up when installing?

The Plex Claim token install method does the direct communication with Plex.tv using the claim-xxxx token you give it (your account).

If it responded with the “Claimed for: your account name” then the server is attached.

Let me go look at the IP addresses again.

Do you have any domain names involved ?

May I please have the rest of the logs (the rollovers ) ?

@stefanw1337

Check the Syno’s connectivity to the internet. I see NO traffic from Plex.tv

Everything in your logs states ‘unclaimed’.

Are you 100% certain the claim token install method showed Successful ?

Plex.tv and your logs do not show any sign of having been claimed.

Well, I managed to set it up now. By using private browser(pressing PMS from the menu in DMS did the same thing) even with all adblockers off.

So now it should be claimed and running. I need to get it online now, I suppose. Because it won’t accept a connection from the outside now. And it’s portforwarded both tpc and udp to the NAS at 32400. app.plex.tv shows the server now at least. NVM, works from the outside, forgot my VPN was on.

Yes, it installed successfully with the token.

@stefanw1337
yeah, the VPN will mess it up

@stefanw1337
THIS!!! Thank you.

Hrs of trying, updated to DSM7 yesterday. Followed tons of videos for tips on permissions etc. I even went nuclear and deleted my plex account. Set up new acc, same issue, no synology server found. I’ve since recovered my original account and with your method and some of the other tips above I got it to work.

Steps I took in case it helps someone:
On DSM logged in via quick connect - private browsing firefox (tbh not sure private browsing matters)

  1. uninstall plex 2nd option (keep files but unclaim server)
  2. reinstall plex with claim token. Select don’t have token when promoted. Paste token and install
  3. launch plex from DSM (opens new private tab still via quick connect)

On PSM (plex tab)
4) should present with login and now look to claim server
5) may hang “not authorised”. Delete all text in address bar after 32400 and hit return.
6) follow on screen prompts to connect to NAS and I selected one library as part of the process when prompted - just in case :slight_smile:
7) you’re done!

Dear plex. A migration/upgrade install instructions would be nice. It was simple enough but unknown process.

Note I had already set up permissions as per many video guides on YouTube so once I had reclaimed my server it all just worked. You may need to do the permission stuff once claimed (plex and plexmediaserver permissions)

Also FWIW at one point on DSM I had 2 plex shared folders “plex” and “plex media server”. As part of my nuclear attempt deleted both folders when plex reinstalled I only have “plex media server” folder so that’s likely the new one as part of DSM7 other is redundant.

Thank you all for posting. Would have been lost without this thread.

2 Likes

You mean these ?

Thanks for making a point. This is a lovely write up and I basically followed those instructions, I would still argue that having such instructions burried in a forum and not a read me to accompany the installation is a miss.

Initially after following those steps plex launched successfully, I got no errors etc. Unfortunately as per the issues other users faced (above) my NAS was not available. I could see it trying to connect with no success. The trick was to install plex and then to uninstall it using the 2nd option to make the NAS no longer claimed and to reinstall again with token to claim it. Or perhaps straight up install with token from the get go. If that was mentioned somewhere I missed it. I’m human after all.

Regardless I found this thread and the helpful community and was able to solve it myself without asking a bunch of questions. I was just passing on my solutions should it help someone else. Take it for what it is.

I’ve been fighting activation issues since October when PMS died on me. I’ve been trying to get this to work on my Synology and still can’t seem to. I tried other avenues as well and can only get activation to occur on a Windows based PMS.
I’ve followed some of the instructions above and haven’t had any luck on DSM 7. I get “Successfully activated” during the installation of the package, however once I navigate to the PMS link from within it says “Not authorized
You do not have access to this server” and eventually drops me to my Windows PMS server and it’s media.

Logs.zip (96.2 KB)

Point your browser directly at the NAS, http://10.0.10.95:32400/web.

Do not use app.plex.tv, quickconnect, ddns, the “open” button in Package Center, etc.

Once you’ve claimed the server, you can then use app.plex.tv, etc.