Claiming my server makes it inaccessible

[dnap941]

Hi,

Make a long story short, my computer that hosted Plex crashed on me. I re-installed Windows 10 Pro 2004 and installed the latest Plex Media Server. I’ve been having difficulty getting the plex server to connect locally, so I decided to “delete” my original server and re-add it. I wanted to start fresh.

Now I am stuck with the server not appearing after it is claimed.

For further details:
If I go to Settings>Authorized Devices and remove my Server and restart Plex, I will see my server listed on the side. However, Plex wants me to claim it.

Once claimed, my movies and music are no longer available locally from http://127.0.0.1:32400/web and it never works from plex.tv either.

Any help would be appreciated as I feel like I’m running into more of a Plex issue than computer/network issue at this point.

Any ideas?

Thanks!

Server Version#: 1.19.5.3035
Player Version#: 4.34.3

[OttoKerner]

Try a different web browser. Chrome or Firefox.

[dnap941]

Same issue

[OttoKerner]

Don’t load the web app from your own custom domain name.
use either http://ip-of-server:32400/web
or
https://app.plex.tv

[dnap941]

@OttoKerner

http://ip-of-server:32400/web

Ok, so just like the HOSTNAME, I’m presented with the logon screen that says “This application is at [ip address] and is not hosted by Plex. Continue only if you recognize this server and wish to grant access”
I proceed by clicking on “Sign-in” and am redirected to http://myIP:32400/web/index.html

Trying https://app.plex.tv gets me:

[OttoKerner]

Can you try and use this app to claim the server instead?
It shows a bit more diagnostic messages: https://github.com/ukdtom/ClaimIt/wiki/How-To-Windows

[dnap941]

Plex.tv or a local address directly to the server, I seem to be missing a ton of server options once the server has been claimed.

Options just go missing along with the server itself. The minute I deauthorize the server and restart PMS, and log in locally on server… I can see my libraries and whatnot. Still unusable through the apps and whatnot, but when I log into the direct server web address I can at least see some normalcy.

[dnap941]

Ok. Will give it a try. Hang on.

[OttoKerner]

What happens if you use http://app.plex.tv/desktop?secure=0 instead?

[dnap941]

Same

[OttoKerner]

What kind of router are you using?
Does it have a user-accessible setting for “DNS server”?
Does it also have a setting for “DNS rebinding protection”?

Are there other DNS filters in use, like Pi-hole etc.pp.?

[dnap941]

Just wanted to show you what it looks like after I deauthorize the server by doing this:

On the server itself, going to http://127.0.0.1:32400/web/index.html I now see:

And have somewhat of normal options:

All the other web links you gave me for the web player result in not seeing the server though.

[dnap941]

Just a regular FIOS router with nothing extra confiogured.
It does, but its defaulted to Verizons DNS.
It does not have a DNS Rebinding protection option.

This server is statically configure for Google DNS.

This server worked perfectly 24 hours ago other than the fact that it crashed on me and it was working fine for the last 5 years. No network changes, nothing.

[OttoKerner]

Which of these two did you actually try?

ukdtom/ClaimIt

http://app.plex.tv/desktop?secure=0

[dnap941]

Using the claim tool identified the issue. I was using an IP range that wasn’t suitable. Once I changed it and restarted my server for the new DHCP range, all is well.

Not sure why it worked all along, but you know what? I’ll take it.

Thanks again for pointing me in the right direction.

[OttoKerner]

Yeah, you better use a “private”-designated IP range, instead of some randomly-chosen range which may or may not be actually free.

Private network

[dnap941]

Correct. For anyone curious:

The Internet Assigned Numbers Authority (IANA) reserves the following IP address blocks for use as private IP addresses:

• 10.0.0.0 to 10.255.255.255
• 172.16.0.0 to 172.31.255.255
• 192.168.0.0 to 192.168.255.255