There was a problem claiming this server (v1.16.4.1469)

Plex Media Server Desktops & Laptops
1

Server Version#: v1.16.4.1469

Hi! I’m installing a fresh-new plex server (removed the previous windows-based server)

Fresh installed Linux Mint 19.2 and PMS v1.16.4.1469

In the wizard, after I chose the server name, I got a “There was a problem claiming this server” after almost 1 minute.
I tried to continue, and retried claiming it from the setup, and soft-restarted PMS as recommended PAChuck in several threads (renaming the Preferences.xml with the service down), but still having the error.

  • I have NOT a proxy or other agent in between other than a modem/router
  • have NOT a domain name assigned
  • My computer is NOT part of a domain which has a certificate attached to it

Tried removing all servers and start from scratch, and I get the same error.

I’m attaching my logs.

Please let me know if you need more info

Thankslogs-plex.rar|attachment (124.2 KB)

2

Hi, I’d like to jump in on this, same issue! Had an issue while trying to move stuff from one server to another, because of the issues I gave up and completely removed plex, removed package, removed startup scripts, removed all data. Started a fresh install with latest version, and I can’t find it at all. No option to claim it, is something wrong on your side? Only error is related to gracenote, the server starts and I can access it via localhost and see other servers.

3

I wiped the 1.16 install and did a fresh 1.14.1.5487 and still no option to claim.

No server option in authorized devices.

4

“Pleases do no hijack someone else’s thread.”, ChuckPA, feb 9, 2019 :laughing:

5

I have another thread for that issue which I’m marked as resolved. Since I have a new issue, I’m just tagging along for what appears to be the same issue. Is this not allowed? I can make another thread with this same issue.

Like I said in the rest of the message…

6

just kidding man; will be useful for the next one looking for help for you issue or mine :+1:

7

I personally am running on CentOS7 and after the RPM install, on first startup I had an error:

Aug 05, 2019 19:25:57.826 [0x7f7137bff700] ERROR - SQLITE3:0x10, 14, cannot open file at line 34876 of [fc49f556e4]
Aug 05, 2019 19:25:57.826 [0x7f7137bff700] ERROR - SQLITE3:0x10, 14, os_unix.c:34876: (2) open(/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache/gn_lists.gdb) - No such file or directory

Although it didn’t specify any error with the database, I figured it might have corrupted something during the failure. I 'touch’ed the file to create it at the path it was looking then I removed the Preferences.xml and all files in the Databases directory, and started PMS back up. I’ve tried accessing via http/https on 127.0.0.1/localhost/remoteip/remotehostname - I can reach the web interface on all methods but no option to claim server.

EDIT: My issue is resolved. After inspected my socks proxy/tunnel I realized (although I didn’t exclude localhost/127.0.0.1, it was ignoring the tunnel and staying local, where there is another plex server running, which is the web interface I was reaching) I corrected my tunnel and properly reach the server as localhost. Claimed!

8

Gracenotes can be safely ignored. Gracenotes isn’t used anymore.

9

Is the server claiming related to Gracenotes?

10

No. A portion of the PMS code is still looking for Gracenote even though Plex just transitioned to the new media provider.

Engineering hasn’t finished cleaning up all that.

11

OK.

Any idea why I can’t claim the server? Can you access the attached logs?

Thanks

12

Anything you upload here, which it accepts and converts to a URL, I can get.

13

You are attaching via email? Email attachments are not accepted in Web. I apologize.

You must Upload then here via the web browser.

Settings - Server - Troubleshooting - Download Logs.

Drag & drop the ZIP file into a reply window and let upload before pressing Reply.

14

Yes, I uploaded but didn’t work.
Will retry

Plex Media Server Logs_2019-08-06_11-45-54.zip (261.3 KB)

16

@luigimacedonia

Thank you. I got it now.

Aug 06, 2019 11:42:53.429 [0x7fd55f7fe700] ERROR - Error issuing curl_easy_perform(handle): 6
Aug 06, 2019 11:42:53.429 [0x7fd55f7fe700] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxd not resolve host: plex.tv)
Aug 06, 2019 11:42:53.430 [0x7fd55f7fe700] ERROR - Error parsing content.
Aug 06, 2019 11:42:53.430 [0x7fd570f10740] DEBUG - Opening 1 database sessions to library (), SQLite 3.26.0, threadsafe=1

Your server cannot see the internet. It cannot find host “plex.tv”

  1. Adapter configuration error
  2. Not connected.
17

wow, man. I can’t believe it.

Tried to ping plex.tv and took a looong time to resolve. Then all packets were lost, but the same happend with an online pinger (icmp filtered, I suppose).
I just added to my /etc/hosts the resolved IP to “plex.tv” and that’s it. Now is connected it like a charm.

The server was timing out trying to resolve plex.tv

Thanks @ChuckPa!

20

As an interim fix adding an IP to /etc/hosts fixes things here and now, but if plex.tv moves to a new IP your server setup will break again.

You should probably in the mean time look at fixing the actual name lookup for plex.tv as it sounds like your nameserver lookups are not working as expected.

So check if your servers in /etc/resolv.conf are working properly and that your server can actually use DNS’s on the internet.

A good nameserver is 1.1.1.1 cloud flares, or googles 8.8.8.8. Some ISP’s may block these so if they don’t work you may need to use your ISP’s DNS servers instead.

21

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