Server refuses to be claimed

Plex Media Server Desktops & Laptops
1

Server Version#: 1.14.1.5488 up to 1.15.4.994
Player Version#: N/A

I’m currently running Ubuntu 18.04.2 LTS on the server and recently upgraded from 16.04 LTS. Ever since the upgrade, I have been unable to claim the server, or once it is claimed, somehow gets unclaimed. On perhaps an unrelated note, the server constantly thinks there is a newer version, even when I’m at the newest version. This is a screenshot from just this morning when I was trying to fix the issue.

version
version856×584 152 KB

Here are the log files: Logs.tar.gz (2.6 MB)

Things I’ve done to try and fix the issue: I’ve tried a soft reset (Deleting the Preferences.xml), and a hard reset, (complete reinstall of plex at the version 1.14.1.5488), to no luck. I’ve exhausted everything I know how to do, and need some assistance.

2

The next sized :hammer: is:

  1. Stop Plex
  2. sudo chown -R plex:plex /var/lib/plexmediaserver
  3. sudo find /var/lib/plexmediaserver -type d -exec chmod 755 {} \;
  4. sudo find /var/lib/plexmediaserver -type f -exec chmod 644 {} \;
  5. Delete Preferences.xml again
  6. Plex/web → Settings - Devices - Delete the old server referenced (Plex/web isn’t very smart)
  7. Plex/web → Sign out of your account
  8. Start PMS
  9. In browser, in an incognito window: http://ip.addr.of.host:32400/web
  10. Sign in & claim (both Plex/web and server now in sync
  11. It will want a normal setup. If you have Libraries already defined, SKIP that part. They will be waiting for you at the dashbaord
  12. Proceed through the wizard until done.
3

Completed Every step and it didn’t work. It won’t show back up in my authorized devices, and still has the same problems as above described. Here’s the Logs since it may be more helpful than saying it didn’t work…

Plex Media Server Logs_2019-05-10_12-49-44.zip (2.4 MB)

4

This device, which appears to be your router, is behind another router.

PMS isn’t happy with it. It can’t get outbound connections.

May 10, 2019 12:44:24.595 [0x7fddcaffd700] DEBUG - NAT: UPnP, found device <http://192.168.1.1:7777/WFADeviceDesc.xml> with private address <192.168.1.150>
May 10, 2019 12:44:24.595 [0x7fddcaffd700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.1:7777/WFADeviceDesc.xml>.
May 10, 2019 12:44:24.595 [0x7fddcaffd700] DEBUG - NAT: UPnP, didn't find usable IGD.
May 10, 2019 12:44:24.595 [0x7fddcaffd700] DEBUG - NAT: PMP, attempting mapping.
May 10, 2019 12:44:24.847 [0x7fddcaffd700] WARN - NAT: PMP, got an error: Not Supported by gateway.
May 10, 2019 12:44:24.847 [0x7fddcaffd700] DEBUG - NAT: UPnP, attempting port mapping.
May 10, 2019 12:44:24.847 [0x7fddcaffd700] DEBUG - NAT: UPnP, not an IGD: <http://192.168.1.1:7777/WFADeviceDesc.xml>.
May 10, 2019 12:44:24.847 [0x7fddcaffd700] DEBUG - NAT: UPnP, didn't find usable IGD.
May 10, 2019 12:44:24.847 [0x7fddcaffd700] DEBUG - PublicAddressManager: Mapping failed.

Two devices (192.168.1.1 behind 192.168.1.177) is incorrect subnet mapping / wiring.

The subnet on the “other” side must be different. Usually it’s your WAN IP.

5

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