DSM 7.2.2 upgrade & plex fresh install - 'claim server' won't work

Plex Media Server NAS & Devices
1

Server Version#:1.41.1.9057-72009057
NAS: Synology DS920+
DSM: 7.2.2-72806

Hi - I’ve just updated to DSM7.2.2 and foolishly didn’t really think about the impact to Plex before I dd it. I was on 6.x previously and hadn’t updated DSM for ages and just thought it was long overdue that I ought to update it. Then I blundered around trying to update Plex from within the package centre and… anyway, I know I’m an idiot.

So then I decided it might just be best to do a completely fresh Plex Server install, so I uninstalled the current package and renamed the preexisting ‘plexmediaserver’ shared folder as ‘plexmediaserver_old’ and removed its permissions. Then I downloaded the latest package and installed it (on the same volume as my media, as directed), so far so good.

The problem is that now when I open the Plex console I can’t claim my server. When already signed in, I click the ‘claim server’ button under settings (advanced)>general but nothing happens - it appears to be doing it then just stops, with no error (claim server button still there). The only error message I see is if I try to claim the server when not already signed in, then it prompts me to sign in and appears to have done so, but then I’m taken to the settings(advanced)>general page, the ‘claim server’ button has the ‘in progress’ spinning wheel, but then stops and it gives the error message ‘there was a problem signing in to Plex’. It looks like it’s signed in alright, but the server just isn’t linked and the ‘claim server’ button is still there.

I’ve tried numerous stop/starts of the package.

Any help appreciated- as you can gather I’m no expert on all this so please be gentle :slight_smile:

Cheers
Dan

2

Tried restarting NAS - no difference when trying to claim server

3

The claiming problem, as you describe it, is usually network problems. The NAS cannot communicate with hosts at plex.tv.

Check network basics - IP address and mask and default gateway. Use a public DNS server - 1.1.1.1, 8.8.8.8, 9.9.9.9.

Also, sync the NAS with a public NTP server. If the NAS time is wrong, claiming will not work.

Question: Do you still have the /plex shared folder from DSM 6, with database files in the /Plug-in Support/Databases directory?

If yes, you can recover your old Plex server. See Struggling with migration from DSM 6 to DSM7 - #2 by FordGuy61.

4

Thanks for your reply. I’ll check out those things. The old shared folder was also called ‘plexmediaserver’ and yes i did keep it (renamed ‘…_old’) so should have those files. If i can recover the old one so much the better.

5

On DSM 6 systems, the Plex Data Folder is /Plex.

I thought you were having trouble updating Plex as part of migrating from DSM 6 to DSM 7.

If that is incorrect, then ignore the Struggling with migration… post. That applies only to a failed migration after updating from DSM 6 to DSM 7.

The rest of my reply, regarding networking and NTP, still applies.

6

I thought it was DSM 6 to 7, but the old folder is definitely named as mentioned above, so perhaps I was mistaken and it was an earlier DSM 7.x

7

IMG_0184
IMG_0184933×536 73.2 KB

I found this under Control Panel > Info Centre > Service - there’s no local port assigned to PMS and it does not say ‘allowed’ for the firewall as some things do.

Roon is a good example - it’s working fine after the update (so network connectivity seems fine) and I never had to configure those settings.

Should there be settings here for PMS? I did have a look and couldn’t see where to configure these things.

8

This is my DSM 7 example and my Plex install is working as it should. As you can see, there is nothing configured for Plex here:

image
image1399×581 28.3 KB

Note: I do not have the firewall enabled on my NAS, if you do have it enabled then you will need to allow Plex Media Server through.

Check this link for the port numbers needed:
https://support.plex.tv/articles/201543147-what-network-ports-do-i-need-to-allow-through-my-firewall/

Try rebooting your Modem/Router and everything connected to it, in order to rule out possible DNS cache issues.

Also, go to Plex Settings > Troubleshooting and download your Plex logs. Attach the .zip file to your post by dragging the .zip file onto the reply window and wait for the upload to complete before hitting the Reply button.

If you are unable to do that, then open File Station and navigate to /PlexMediaServer/AppData/Plex Media Server and right click on the Logs folder and select Compress to logs.zip.

Again, attach the .zip file to your post, thanks.

9

@trumpy81 thank you.

I’ve restarted modem, router, switch and NAS. tried again - same thing. Here are the logs.

Plex Media Server Logs_2024-10-27_09-59-18.zip (375.6 KB)

10

No I don’t have it enabled. I was just looking at that screen and trying to see what was different about Plex vs something like Roon which is working fine. I guess it can’t be that.

11

@DT79

Looking at your logs (thank you), PMS can’t perform DNS Lookups to resolve hostnames.

Oct 27, 2024 09:45:12.990 [140020381195064] WARN - [HttpClient/HCl#5] HTTP error requesting GET https://v4.plex.tv/pms/:/ip (6, Couldn’t resolve host name) (Could not resolve host: v4.plex.tv)
Oct 27, 2024 09:45:12.990 [140020383304504] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-6):

  1. Check your Control Panel - Network and EDIT eth1.

  2. You want to confirm
    – It’s the default gateway
    – DNS is pointing to the LAN IP of your modem/router
    – (if you don’t trust your ISP, use a public DNS like 8.8.8.8, 1.1.1.1, 9.9.9.9)

  3. After making the change, restart PMS.

For Reference, here’s my DS418 settings.
– Static IP assignment
– Points to my router
– I own my router so configured the DNS resolution in it (1.1.1.1, 9.9.9.9)

Screenshot from 2024-10-27 14-04-37
Screenshot from 2024-10-27 14-04-37778×643 41.1 KB

12

Thank you very much @ChuckPa . Will take a look at that and let you know how I get on.

13

OK, I’ve checked everything, and configured the IP manually. This is an already reserved IP address in my router’s LAN config (and obviously correct and there is no general problem with connecting to the NAS on my network). All the settings are correct for router IP/DNS etc.

I’ve attached new logs after the most recent attempt to claim the server.

The only potentially relevant thing I can think of, that checking the NAS network settings reminded me of, is that I have only LAN 2 connected on the NAS. I remember I used to have both LAN 1 & 2 connected and for some reason (can’t remember why now) needed to disconnect one of them so just reached behind and disconnected one which happened to be LAN 1. Everything carried on working fine including Plex so thought no more of it. I can’t see how it would be an issue now, but thought I’d mention it…

Edit - i reconnected LAN 1 and made sure it was configured correctly. I’ve just tried ‘preferred network interface’ eth0, eth1 and ‘any’ in the Plex network preferences - same result on all (after the attached log file),

Plex Media Server Logs_2024-10-27_19-04-20.zip (420.0 KB)

14

Just letting you know, If you have more than one Ethernet connection to the NAS, then you must Bond those connections, otherwise Plex can send on one adapter, but recieve the response on another adapter, which can sometimes lead to Plex failing to get a proper connection.

Open DSM Control Panel > Network > Network Interface > Create > Create Bond and then select the NIC’s you wish to Bond.

Alternatively, you can set up Link Aggregation in your router or managed switch (?), provided they support LACP and LAG.

Another solution is to connect to port 1 (eth0) on the NAS only.

From your logs:

Oct 27, 2024 18:47:59.019 [139949635259024] DEBUG - Network interfaces:
Oct 27, 2024 18:47:59.019 [139949635259024] DEBUG -  * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Oct 27, 2024 18:47:59.019 [139949635259024] DEBUG -  * 3 eth1 (192.168.1.25) (00-11-32-D9-7C-8A) (loopback: 0)
Oct 27, 2024 18:47:59.019 [139949635259024] DEBUG -  * 4 eth0 (169.254.223.202) (00-11-32-D9-7C-89) (loopback: 0)
Oct 27, 2024 18:47:59.019 [139949635259024] DEBUG -  * 1 lo (::1) (00-00-00-00-00-00) (loopback: 1)

I see that you are connected to port 2 (eth1) on the NAS. You should change that to port 1 (eth0) on the NAS and then reboot the modem/router etc.

In some cases, Plex can default to using the first port (eth0), especially when Preferred Network Interface is set to Any, even though it shouldn’t.

From your logs:

Oct 27, 2024 18:48:01.220 [139949572705080] 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
Oct 27, 2024 18:48:01.221 [139949572705080] 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

Code 6 usually indicates a DNS issue and that is currently effecting metadata downloading and driver downloading as well.

If you have not already, try switching to a Public DNS server, such as Google 8.8.8.8 or Cloudflare 1.1.1.1.

Reboot the modem/router etc. after making any changes.

15

Thanks very much, that worked. As soon as I bonded the Ethernet connections and rebooted the router the ‘claim library’ worked immediately.

Really appreciate your assistance and @ChuckPa @FordGuy61 who also took the time to help.

16

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