Server Not Authorized

Server Version#: 1.30.1.6497-5fc2e0894
Player Version#: All of them

I have the latest Plex Server running in the latest DSM7 on a DS920+.

My Server went missing from the media server list in my Plex account. If I tried to hit localip:32400, all the local options were missing from the LHS menu. I removed it from the authorised devices list, then could log into the local address again and see everything. When I try to Claim the server again, it signs in, then I get a “You are not Authorized” error, and everything returns to its previous state.

I’ve tried this from multiple devices and browsers to ensure it’s not a logon session issue, and I’ve even reset my plex account password to ensure that’s all fresh.

I’m completely stuck on how to proceed.

Help!

Uninstall the package with the “Uninstall Only” (KEEP) option

Reinstall the same version again EXCEPT

  1. Click “New or Lost servers” (Plex Claim Token method)
  2. Click “Get Plex Claim Token” hyperlink
  3. COPY the token from the tab which opens
  4. Return to the installation page
  5. PASTE into the box
  6. NEXT NEXT DONE.
  7. Let it finish and verify your username

Hi Chuck,

I was literally right then updating my post to say I’ve tried that process, which has failed with the same result.

Cheers

What did it fail with? A blank username ?

If so, Fix the DNS and gateway address network settings on the Syno

EDIT: Worst case,

  1. Stop PMS
  2. Make a ZIP of the Logs directory under Plex
  3. Download
  4. Attach here for me to review

The process completed but I still get “Not authorized
You do not have access to this server” after I sign back in. The server works until I claim the server through any method. Once it’s claimed, it fails.

Logs please, manually collected please with PMS stopped.

Hi,

Logs attached, I think this is the important bit, though:

Jan 07, 2023 08:17:14.063 [0x7f8a69631b38] ERROR - MyPlex: Error 403 requesting XML from: https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx
Jan 07, 2023 08:17:14.063 [0x7f8a69c5cb38] ERROR - MyPlex: Couldn’t get list of access tokens from myPlex.

PMSlog.zip (4.7 KB)

You turned off DEBUG logging. That hurts us – especially on Synology.

Now you need to do some editing.

  1. Install the Synology Text Editor app if not already installed.

  2. With Plex stopped –

  3. Filestation → PlexMediaServer/Library/Application Support/Plex Media Server

  4. Right-click “Preferences.xml” → Open with Text Editor

  5. Cursor down to the last line.

  6. As you cursor to the right, look for “LogDebug”. If you find it, change "0" to "1"

  7. Save and exit

ELSE

  1. If you don’t find it. continue to the end , stopping right before the closing />

  2. Add LogDebug="1"

SomePref="Value"  LogDebug="1" />
  1. SAVE and exit

Now go through the start, wait, stop, manually gather logs again cycle.

In the future, keep debug on please, You don’t save enough space or CPU to be worth it. It saves a TON of time and effort when problems do arise

I’ve enabled debug logging, and repeated the claim process, which resulted in the same failure, so that should all be in there.

debuglog with failed claim.zip (60.7 KB)

Got it.

Do you like being slapped with the left hand or the right hand? :rofl:

Jan 07, 2023 08:43:59.924 [0x7f7500d160d0] DEBUG -  * 6 ovs_eth0 (192.168.1.200) (00-11-32-E1-35-E3) (loopback: 0)
Jan 07, 2023 08:43:59.924 [0x7f7500d160d0] DEBUG -  * 7 ovs_eth1 (192.168.1.200) (00-11-32-E1-35-E4) (loopback: 0)

Look at the IP addresses

That’s the local server address. Which I can access, until I claim the server, then it all breaks, no local access, no app.plex.tv access, nothing.

This was working fine until yesterday.

What have I missed?

  1. That’s WRONG. You NEVER assign the same IP address to two adapters.

  2. PMS is looking for a reply on one but will NEVER get it. DSM will fail to deliver.

If it was working, it was pure luck because this breaks the rules.

If you aren’t using the Virtual Switch, you can turn it off.
If you want both adapters at that IP,

BOND the adapters into one virtual adapter bond0 (control panel - network - network interfaces)

All the packet routing and gateway info will be updated to reflect the new bond.

While I wish I had an explanation for why that was configured like that (I’ve never used the 2nd eth adapter) - I’ve fixed that, and tried again. and it’s still broken.

If I kick the server from the account, I can log on in the local address. Once I claim it, it breaks and I lose access from everywhere.

Now let’s go further.

Show me the rest of your LAN configuration please ?

I’m concerned with Gateway and DNS

It seems you have DNS working – There are no errors in your logs.

I am sending you server info via PM.
Please confirm.

In that PM - Also, please let me know if Remote Access is enabled and shows your remote IP correctly.

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