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

[zbm]

I’ve been using that link, I thought that was the issue early on and ruled it out. I’ve tried different browsers, private mode browsers, totally different machines to access it immediately after the new install, all bring me back to the same “Not Authorized” screen. The same happens if I attempt to use a docker container, seems to activate successfully but when you attempt to go to it the first time, it says Not Auth’d.

If I remove the “index.html#!/setup/99065e50932f7293f5c30efc700641726ef5dec9” after the link in the screenshot and hit enter, it reloads the page, buts that back in the URL and throws me back to the same screen.

[ChuckPa]

If I may suggest?

1. Uninstall the package with the KEEP option
2. Install the same SPK again using the “Plex Claim Token” option
3. Click the link to “Get Plex Claim token”
4. Past token in the installer menu window
5. NEXT → to complete installation
6. After a slightly longer install time (while it gets credentials), confirm it responds with your Plex Account name in the final installation message.
7. Now open the Synology by LAN IP to complete the “Claiming” process. Everything will be as it was.

If there the name is not present, a networking issue exists because DSM contacts Plex.tv to obtain the credentials.

This same lack of networking will also cause “Not Authorized” messages when attempting to access the server.

[codog180]

For whatever reason. The process of uninstalling and then reinstalling then accessing directly from ip address seemed to resolve my issue.

[ChuckPa]

@codog180

directly from ip address seemed to resolve my issue.

Using the IP address keeps you on the LAN and away from “remote” and “domain names”.

[codog180]

I had tried directly from ip several times before. So it was the combination of uninstalling / reinstalling then making sure the first visit was from the ip only.

[ChuckPa]

Yes, Using the IP is required. It’s unfortunate but how Synology works.

From the Synology FAQ

Synology FAQ - Questions, Answers, and How-To's

Synology Frequently Asked Questions Table of Contents Intro: Posting in the Plex Synology Forum DSM 6 & 7 FAQ Some of these FAQ apply equally to DSM 7 and 6. Others do not. Please read carefully before proceeding. Getting access to the Logs Have I installed the latest version…? Which version do I need, Intel or ARM? 3a. Using Plex’s package signing public key - DSM 6 LAN addressing requirements - RFC1918 specification for local LAN? First run & Setup Recommended Media Organization and A…

There is a dedicated First-Run and setup How To.

Installation & Setup of Plex Media Server on Synology

Creating Shared Folders If you don’t have existing shared folders for your media, follow these steps **If you already have your media stored how you want it, you can skip this step DSM 7 NOTICE: On DSM 7, “System Internal User” PlexMediaServer is used (change ‘Local User’ → ‘System Internal User’) when granting shared folder permissions. Open Control Panel Click Shared Folder → Click “Create” (at the top) Give it a name Decide if you want the Recycle Bin on or off. The recycle bin …

[ChrisUSC84]

Hello all,
For some this may be your issue. I found that when my NAS is connected VIA VPN it says Not Authorized, however when I turn my NAS VPN off it allows me to access my media.

[zbm]

I’ve done this as well. My issue happens on any device that isn’t a Windows desktop. I even borrowed a QNAP nas from a friend of mine and did an entire new setup with blank drives and fresh install and still after first login I get “Not Authorized to Access Server” after logging in. I always access using LAN IP and don’t use the plex.tv/launch app link etc.

So, I am assuming it’s gotta be something network related on the credential handling? What specifically happens with activation for Dockers and NAS apps that isn’t happening or happens differently than on Windows installs/activations?

[jSyn3Plex]

I feel I am either loosing, or have lost my mind. However, I have followed all instructions after deleting and conducting fresh install, with a claimed cert., to no avail. The closest I get is a page that states ‘Get Plex Media Server’.

How do I add my media?

“UPDATE”

Okay, so it was a user error (aka…me), I did not choose option 2 when deleting and reinstalling Plex on my Syn hence the handshake issue.

Be sure to choose option “2. uninstall plex (keep files but unclaim server)”

Tis obvious now, that if the server is still “claimed” you are unable to be authorised

[Stargate360]

FIXED: I was having the same issue but with Plex Server on QNAP. The fix was to simply clear browser cache. I discovered this after getting Not Authorized in Firefox so I copied the URL to Edge browser and it worked there. I went back to Firefox, cleared the browser cached and I was back up and running in Firefox.

[zieprus_hotmail_com]

Regarding “Not Authorised” I eventually fixed the issue myself. My local network is a 188.168.x.x would only work when I changed my whole network to a 192.168.x.x address. Not sure why as I have had a 188.168.x.x for years and all worked fine until moving to DSM v7 on the Synology. Will see how I go but I bought a membership for months hoping I was missing a feature somewhere but never worked. Anyway now that it is, will see how it goes I may puchase a membership again.

[zhangxn1112_gmail_com]

Like many others in here I too have issue with Plex after upgrading to DSM 7 on my synology ds920+
I did a manual install of the plex media server on my synology dsm using a token. Login to my account and I was unable to add my media files but instead prompted me to install Plex Media Server.
Not sure what I did wrong here or if I miss a step. Any help is appreciated. See attach for the log file. Thanks in advance.
Plex Media Server.zip (59.5 KB)

[theyonan]

Thank you! This did it.

[ChuckPa]

@zhangxn1112_gmail_com

Use the IP address of the Synology to claim it.

Don’t use the QuickConnect link button. It rejects it as remote until after it’s claimed.

Jan 21, 2022 00:54:21.928 [0x7f34f1169b38] DEBUG - Request came in with unrecognized domain / IP '192-168-0-119.anc2639.direct.quickconnect.to' in header Host; treating as non-local
Jan 21, 2022 00:54:21.929 [0x7f34f0966b38] DEBUG - Request: [192.168.0.125:5240 (Subnet)] GET /web/index.html (3 live) GZIP