Cannot Claim Server, Update Available Message Already Up To Date

Plex Media Server Desktops & Laptops
1

Server Version#: 1.16.6.1592

I just installed Plex Media Server on my Ubuntu server and I’m seeing a message in the general settings indicating that an update is available. I’ve tried downloading and installing the latest version manually, but it still says I need to update and when I try to claim my sever it just checks for updates again and nothing else happens.

2

Settings - Server - General ,

Put your Update channel setting to “Public”.

3

The only option available there is “unknown”.

4

Click “Show Advanced” (right side).

Notice on mine, I am using 1.16.4 which is behind the Public 1.16.6 so the update notification is correct.

Public update channel is at the bottom. If you aren’t seeing a choice of options where Public should be, Please download and attach the log files for me to look at. It sounds like something else isn’t working correctly

Screenshot%20from%202019-09-24%2012-43-10
Screenshot%20from%202019-09-24%2012-43-10772×648 260 KB

Regarding Claiming:

  1. Is the server local or remote?
  2. If local, what is the LAN IP address block?
5

The only option listed on mine is “unknown”. I’ve attached my log files. Thanks for the assistance.

image
image920×543 138 KB

Plex Media Server Logs_2019-09-24_12-49-55.zip (373.7 KB)

6

Sorry, I forgot to answer your other questions.

  1. I’ve tried claiming it on the local machine as well as remotely.
  2. The LAN IP of the server is 192.168.1.24.
7

Something isn’t making sense here:

  1. Server logs can only be downloaded by the server owner. If it’s claimed, you own it.
  2. Is there another server on the LAN available to be claimed?
  3. If so, how does it stand in relation to the server at 192.168.1.24 ?
8

Nope, this is the only server that I currently have set up on my LAN.

9

Ok, let’s break out the big hammer.

  1. Stop the server
  2. Remove the file “/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Preferences.xml” – We will force-reset the ownership it thinks exists.
  3. In your Plex/Web browser, upper right corner, Sign out of Plex/web if not still signed out
  4. Start PMS
  5. Open an incognito browser window
  6. In that window, open http://ip.addr.of.server:32400/web if it’s not running on the same computer as you . If it is on the same computer (on your workstation), use http://127.0.0.1:324000/web
  7. It will load the web browser interface
  8. It will present you with the “Got It” page
  9. It will now take you to the Sign-In page
  10. It will then take you to the Setup Wizard where you create Library sections.
  11. DO NOT CREATE new library sections if you have already created them. SKIP This
  12. Continue through the setup wizard, making any preferences and other settings as you wish
  13. When you finish, you’ll arrive at the Dashboard.
  14. Any previously created Library sections will be there waiting for you.
10

I’m still having the same issue after following these steps. I get an error stating that there was “a problem claiming this server” during the first step of the setup wizard.

11

Please stop plex

next, I would like you to grab and make a tar.gz of the entire “/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs” directory and then attach that tar.gz here for me to look at.

12

Here you go.
plex-logs.tar.gz (145.4 KB)

13

What I’m finding in your logs is that PMS is unable to contact Plex.tv

It isn’t showing DNS lookup failures so that much is working.
What I’m seeing is it timing out when asking for the features your account has.

I’m also seeing several devices advertizing SSDP capabilities but not responding with properly formatted XML. 192.168.1.4, 192.168.1.4 (TCL•Roku TV - 2N00HF459915)

At no point do I see your computer connecting to the server and authenticating which is highly unusual.

Somewhere, somehow, there is a network issue which isn’t clearly showing itself here.

This is behaving as if you have a LAN which is partially isolated from the internet. Is this possible?

14

This is the first time I’m seriously working with Linux, so if there’s anything special I need to do to allow Plex to communicate properly from Lubuntu then that may be it. Otherwise I can’t think of anything that could be causing a problem like that. I have access control turned on on my router, but I’ve tripled checked to make sure the system is allowed and I can access Plex.tv from the web browser on the same machine.

15

I’ve seen this behavior with Lubuntu and Mint before. Both are derivatives of Ubuntu and both have issues. Ubuntu is officially supported (PMS is compiled on it fwiw).

Is there an easy option of switching to mainstream Ubuntu 18.04 ?

16

Yeah, I’ll give that a try. It’ll probably take me a few days, but I’ll try to remember to come back and let you know how it worked out. Thanks for the assistance!

17

I seem to be having the same problem even with a new system and mainstream Ubuntu 18.04. Could it be a problem with my account? I was thinking about just deleting my account and creating a new one.

18

No, I don’t think it’s so much a problem with your account.

In most claiming problems, the key points to check are:

  1. Is the LAN network compliant with RFC-1918 addressing (IPv4) (192.168.x.x, 10.x.x.x, and 172.16.x.x-172.31.x.x)
  2. Both initiating (your workstation) and server are on that same LAN
  3. If the server is on your machine itself (use http://127.0.0.1:32400/web to claim it)
  4. The server must be able to reach the internet and be able to resolve DNS for plex.tv

Restarting the logs and attempting to talk to it via plex/web will generate what’s needed.

Then we can manually pull the logs by shutting it down and creating a tar.gz of “/var/lib/plexmediaserver.Library/Application Support/Plex Media Server/Logs” (whole directory).

Attach that tar.gz here and I’ll see what it’s complaining about.

19

Here you go.

plexlogs.tar.gz (19.0 KB)

20

There is a networking problem here.

PMS (the host) cannot communicate out to Plex.tv

Error 28 is a timeout error meaning it thinks it sent the message but no reply was ever received.

Oct 07, 2019 18:49:10.328 [0x7faeb5292700] DEBUG - NAT: UPnP, usable device <http://192.168.1.1:56688/rootDesc.xml> with private address <192.168.1.29>.
Oct 07, 2019 18:49:10.370 [0x7faeb5292700] WARN - NAT: UPnP, error mapping port 15491, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://192.168.1.1:56688/ctl/IPConn.
Oct 07, 2019 18:49:10.370 [0x7faeb5292700] DEBUG - NAT: PMP, attempting mapping.
Oct 07, 2019 18:49:10.621 [0x7faeb5292700] WARN - NAT: PMP, got an error: Not Supported by gateway.
Oct 07, 2019 18:49:10.621 [0x7faeb5292700] DEBUG - NAT: UPnP, attempting port mapping.
Oct 07, 2019 18:49:10.655 [0x7faeb5292700] DEBUG - NAT: UPnP, usable device <http://192.168.1.1:56688/rootDesc.xml> with private address <192.168.1.29>.
Oct 07, 2019 18:49:10.700 [0x7faeb5292700] WARN - NAT: UPnP, error mapping port 13367, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://192.168.1.1:56688/ctl/IPConn.
Oct 07, 2019 18:49:10.700 [0x7faeb5292700] DEBUG - PublicAddressManager: Mapping failed.
Oct 07, 2019 18:49:14.614 [0x7fae867fc700] DEBUG - DVR:Device: Discovering and refreshing all devices.
Oct 07, 2019 18:49:14.614 [0x7fae867fc700] DEBUG - DVR:Grabber: HDHomerun discovered 0 compatible devices.
Oct 07, 2019 18:49:14.615 [0x7fae867fc700] DEBUG - HTTP requesting POST http://127.0.0.1:32600/devices/discover
Oct 07, 2019 18:49:17.032 [0x7fae867fc700] DEBUG - HTTP 200 response from POST http://127.0.0.1:32600/devices/discover
Oct 07, 2019 18:49:19.275 [0x7fae9c9ce700] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.1.29:32469/DeviceDescription.xml
Oct 07, 2019 18:49:19.275 [0x7fae9c9ce700] DEBUG - HTTP requesting GET http://192.168.1.29:32469/DeviceDescription.xml
Oct 07, 2019 18:49:19.279 [0x7fae9c9ce700] DEBUG - HTTP 200 response from GET http://192.168.1.29:32469/DeviceDescription.xml
Oct 07, 2019 18:49:19.279 [0x7fae9c9ce700] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://192.168.1.29:32469/DeviceDescription.xml
Oct 07, 2019 18:49:19.280 [0x7fae9c9ce700] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.29 (Plex Media Server: Media-Server)
Oct 07, 2019 18:49:20.145 [0x7faeb5a93700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2019 18:49:20.145 [0x7faeb5a93700] DEBUG - HTTP simulating 408 after curl timeout
Oct 07, 2019 18:49:20.145 [0x7faeb5a93700] ERROR - Error parsing content.
Oct 07, 2019 18:49:20.145 [0x7faeb5a93700] ERROR - Error parsing XML: Error parsing file.
Oct 07, 2019 18:49:22.792 [0x7faeb4a91700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2019 18:49:22.792 [0x7faeb4a91700] DEBUG - HTTP simulating 408 after curl timeout
Oct 07, 2019 18:49:22.792 [0x7faeb4a91700] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=408): 
Oct 07, 2019 18:49:22.805 [0x7fae86ffd700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2019 18:49:22.805 [0x7fae7ffff700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2019 18:49:22.806 [0x7fae86ffd700] DEBUG - HTTP simulating 408 after curl timeout
Oct 07, 2019 18:49:22.806 [0x7fae86ffd700] ERROR - AutoTagging: unable to retrieve updated word lists
Oct 07, 2019 18:49:22.806 [0x7fae7ffff700] DEBUG - HTTP simulating 408 after curl timeout
Oct 07, 2019 18:49:22.806 [0x7fae7ffff700] WARN - [Analytics] Couldn't get analytics privacy settings. Trying again soon.
Oct 07, 2019 18:49:22.806 [0x7fae7ffff700] DEBUG - Running database fix-ups.
Oct 07, 2019 18:49:22.807 [0x7fae7ffff700] DEBUG - Database Fixups: Destroyed 0 transient items.
Oct 07, 2019 18:49:22.809 [0x7fae7ffff700] DEBUG - Running database fix-ups completed in 0.0 seconds.
Oct 07, 2019 18:49:22.810 [0x7fae7ffff700] DEBUG - HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=
Oct 07, 2019 18:49:25.806 [0x7fae877fe700] WARN - [Analytics] Attempting to send unrecognized metric (server:startup). Skipping.
Oct 07, 2019 18:49:38.335 [0x7fae7ffff700] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 07, 2019 18:49:38.335 [0x7fae7ffff700] DEBUG - HTTP simulating 408 after curl timeout
Oct 07, 2019 18:49:38.335 [0x7fae7ffff700] WARN - FeatureManager: Couldn't get features. Trying again soon.
Oct 07, 2019 18:49:38.336 [0x7fae85ffb700] DEBUG - DVR: Starting up.
Oct 07, 2019 18:49:38.337 [0x7fae85ffb700] DEBUG - Activity: registered new activity