Issue claiming server

Yea, I ran into this twice… The first time, I was rebuilding PMS on a crashed server using the same hardware. The only difference was that I installed Windows Server OS instead of a Desktop OS. I wanted to take advantage of the NIC Teaming capability on the server OS. Anyway, I never did get the server OS to work despite trying 2012 and 2016 versions downloaded from Microsoft. Finally gave up and installed Windows 10 and was able to claim the server the first time. I really don’t know why but suspect it had something to do with the plex.tv site not being able to communicate back to my server despite the fact that I verified the local firewall was turned off.

The second time, I was building a new PMS Server on newer hardware with the intent of replacing the old one. I installed Windows server 2016 once again and worked on the assumption that return communications from the Plex website were not getting through. Apparently that was correct. I have Vonage and when I removed the Vonage box, everything worked. I was both happy and pissed off (haha) because I had the vonage box configured to pass everything (or so I thought).

So, if there is anything you can eliminate between your cable modem and your Media Server, do so. You may also want to make sure that you are using DHCP (until you get things working) to ensure your modem\router are working with an address they control.

Good Luck!

@taproom and @hockeyskater19_gmail_com Thanks for the information.

I fired up another machine with Lubunutu 18.10 and installed the latest version of Plex and ran into the same error.

I then loaded the latest version of Plex on my MBP running 10.14.3 and was able to claim the server successfully, so I am 0 for 2 on two different machines running two distros based on Ubunutu 18.10. I think this rules out my router or my internet as the issue.

@ChuckPa What are your thoughts?

Without seeing logs, it’s impossible to know.

Can you get me the debug logs (or just a tar.gz / zip) of the Logs directory ?

OS: Lubuntu 18.10
Plex: 1.15.2.793

Thanks again for all of your help!

Plex Media Server Logs_2019-04-03_13-52-47.zip (147.7 KB)

Log says:

Apr 03, 2019 13:49:54.295 [0x7f306b05b700] ERROR - Error issuing curl_easy_perform(handle): 28
Apr 03, 2019 13:49:54.295 [0x7f306b05b700] DEBUG - HTTP simulating 408 after curl timeout

So check your DNS and default router

Also log says:

Apr 03, 2019 13:49:40.081 [0x7f30597fa700] DEBUG - NAT: UPnP, usable device <http://10.0.0.1:56688/rootDesc.xml> with private address <10.0.0.27>.
Apr 03, 2019 13:49:40.106 [0x7f30597fa700] WARN - NAT: UPnP, error mapping port 19636, error: The port mapping entry specified conflicts with a mapping assigned previously to another client, controlURL: http://10.0.0.1:56688/ctl/IPConn.

So check your router NAT and UPnP settings, and compare with your PMS

Which Log file was this found in, so I can check on my main system?

The latest logs were from another computer I had and not the actual Plex server I am trying to use, was just seeing if I could get any server to be claimed.

I found no UPnP conflicts, but I cleared the list out anyway. Double checked port forwarding. And updated my DNS from CloudFlares 1.1.1.1 to my ISP’s DNS, but still no go.

In the PMS log, and for future ref, don’t ask a Q, and then upload logs from another device !

Understood, but I’m having the same issue on another machine, so I uploaded the logs to compare, wasn’t trying to confuse anyone.

So I am at a loss, I am trying not to be a pain in the ass, but I still have not been able to resolve the issue.

I have checked that I do not have a double NAT, UPnP is enabled, the Plex server has a static IP and I am forwarding 32400 and have verified that it is exposed to the Internet using https://www.canyouseeme.org/ I am using 1.1.1.1 and 1.0.0.1 for my DNS server.

The error I am seeing in the logs is:
Apr 05, 2019 20:24:04.939 [0x7f16837fe700] ERROR - Error issuing curl_easy_perform(handle): 28 and I am not sure how to resolve it.

Attached are my latest logs, again any help would be greatly appreciated.

Plex Media Server Logs_2019-04-05_21-00-17.zip (285.4 KB)

Please switch off verbose logging, reproduce, and upload new logs

Thank you for your help!

Plex Media Server Logs_2019-04-06_08-39-18.zip (580.8 KB)

Try and switch DNS to 8.8.8.8 (Google) for a short test

And if that also doesn’t help, try in a terminal on the PMS server, to type:

http://plex.tv/pms/:/ip

That should respond asap with your public IP Address

I updated my DNS to 8.8.8.8 and 8.8.4.4 as per Googles instructions and the plex.tv link gives me 69.216.108.255 sadly we are still no go.

Plex Media Server Logs_2019-04-06_11-46-21.zip (597.3 KB)

Same error in windows in PMS since last update, yesterday was working for me when i updated the server then movies remotely or the movies via web crash, with the message Play error, please check the file exist bla bla bla

Not related, please start a new thread

Then I sadly have no more ideas for now, except downgrade PMS

Do you have any links to previous versions? I’ve wiped the computer and don’t have the update files any more.

Zach

Sadly not.

It’s always good common practice to keep last working version, until new version is verified.

And I collect QNAP versions only :wink:

Time to look for an alternative then, thanks for your help!

Zach

I was able to locate a copy of plexmediaserver_1.14.1.5488-cc260c476_amd64 and installed it and got it to work. Thank you again for all of your help.

Zach

2 Likes