Unable to Claim on Synology DS1520+. Observed PlexOnlineToken="" from other topic

Server Version#: 1.41.0.8930
Player Version#:

Relocated and set up system, lost library (no servers appeared in my list).

Confirmed Plex shares and users permissions were set to allow accessibility (already had, so no changes were made, but confirmed they were good).

Uninstalled / reinstalled Plex server app from Synology Control panel to no avail.

Uninstalled / reinstalled “with Claim ticket”, and the Plex Media Server appears, but now has yellow triangle and although it now appears in the list of servers, won’t allow me to claim it. When I click “Claim this Server” it thinks for a while and then just returns to the same screen, offering to let me attempt to claim.

I read in another article about PlexOnlineToken=“” being an issue, and my Preferences.xml contains that.

Any guidance appreciated.

DSM 7 or 7.2.2 ?

Uninstall + KEEP
Reinstall same SPK again – except Plex Claim Token option
Get Plex Claim token
COPY from the new tab back into the installer tab
continue the reinstall.
Observe it reporting claimed for you when complete.

Thank you for the quick reply!

That looks to be what I had done, but after following the procedure again to see if it would successfully claim (which it indicated it had “Claimed”) it is again gone from my list and I am back to displaying zero servers. Ugh.

I’ll try again for round 3 and see if it returns.

Tried two more times, with “Keep” as well as (what originally brought it “back” but unclaimable) “Keep but sign out and unclaim”, both times with claim ticket in an effort to reclaim.

Now it’s just back to gone from list again, though.

Additional info, perhaps useless, but for the sake of mentioning other details about the system and what I’ve tried.

Connected to the same network, adjacent ports on the same router. No VPN, firewall, etc… between devices.

When this started I was on
PlexMediaServer-1.31.3.6868-28fc46b27-x86_64_DSM7, updated to
PlexMediaServer-1.40.5.8921-836b34c27-x86_64_DSM7, somewhat reluctantly update to beta in hopes it was a known issue that had been resolved, so currently at
PlexMediaServer-1.41.0.8930-056c2ed26-x86_64_DSM7 (and still receiving notifications that a new version is available(? I suspect from the version available to DSM v7.2.2 which doesn’t apply to my NAS which is DSM v7.2.1 not eligible for DSM v7.2.2…?)

If this fails again.

  1. Stop Plex
  2. Make a ZIP of the Logs directory
    (FileStation → PlexMediaServer - AppData - Plex Media Server - (Right-click “Logs” → Compress to Logs.zip) Download and attach here

Attached.

Logs.zip (1.6 MB)

  1. DNS is not pointing to your modem/router. DSM cannot connect out by name to contact Plex.tv. Your network / modem-router change recently?

Sep 01, 2024 15:15:54.913 [140198930340664] ERROR - [DriverDL/icr] Component download failed: Request to ‘https://downloads.plex.tv/intel-compute-runtime/icr-e8d3b00e629bec95ae9f2c9a-linux-x86_64.zip’ failed with code -6
Sep 01, 2024 15:15:54.913 [140198935251768] ERROR - [DriverDL/ivd] Component download failed: Request to ‘https://downloads.plex.tv/intel-vaapi-driver/ivd-3fed72a7a10ce6a0f1ca0179-linux-x86_64.zip’ failed with code -6

  1. Strong recommendation, while you’re in there – BOND these into 1 adapter. Plex doesn’t like 2 adapters on the same lan (nether does the TCP/IP specification :wink: )
    – Control Panel - Network.
    – Select both eth0 and eth1.
    – The bonded adapter (bond0) will come back with ip address as eth0

Sep 01, 2024 15:15:47.802 [140199000984208] DEBUG - * 4 eth1 (192.168.8.3) (00-11-32-D8-EC-A5) (loopback: 0)
Sep 01, 2024 15:15:47.802 [140199000984208] DEBUG - * 5 eth0 (192.168.8.2) (00-11-32-D8-EC-A4) (loopback: 0)

Synology Knowledge base has how-to if you need it

After you get that part resolved, if you need help reclaiming the server,

I’m a bit confused by this, as DNS is already pointing to my router, and the link was working previously. I’ll see what the upstream modem address is and try that, though, too.

Created a bond. In my DSM there was no way to select both connections, but “Create” a connection was an option so I went that way and got it done. The router I am using doesn’t have 108.3ad capability, but it’s now a single connection (thought it was already, but perhaps changed with firmware update).

I’ll get through the uninstall / reinstall exercise again and report back. Thank you again.

It was able to claim it after creating the bond and redoing the uninstall / reinstall.

No changes made to the DNS settings, etc…

Fingers crossed this holds.

Thank you!

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