I am unable to claim the server, despite logging in during the initial server setup, and being logged in. I’ve tried to claim it both from the local machine (localhost:32400/web), and from another machine on the same local network ([local ip]:32400/web), neither will work. It will spin when I try to click ‘claim server’, and do nothing.
It also says that an update is available, even though I literally installed plex media server today. The version is 1.18.2.2058, which is the current version. I am on ubuntu 18.04.
I have attached some logs.
Does anyone know why this is happening? It is incredibly frustrating, because I have done nothing except a fresh clean plex install, and I cannot even do something as simple as claim this server even from the machine itself.
This is the native package from plex.tv, installed from command line with sudo dpkg -i. It’s a regular ubuntu desktop installation, not a VM. I’m doing all of these steps from the desktop itself.
I signed out of my plex account on firefox, and restarted the plexmediaserver process. Opened an incognito window and went to that address, like before. It gives me the final step in the plex web setup, “Customize your Navigation”, and shows the one library that I created when I did the initial setup. I click “Finish Setup”, it takes me to my library, where I try to claim the server again. It directs me to log in, and then I go to claim server, and it says “There was a problem signing into plex” (even though I am already logged in).
Now, the server has disappeared from the sidebar and when I try to access it again, it says I do not have access to this server.
How could I have lost access to this server when it was never able to be claimed in the first place??
interestingly enough, after clicking around, it said my credentials have expired, and prompted me to log back in, where it seems to have worked and I have access to the server now.
Dec 07, 2019 16:46:04.720 [0x7efbef7fe700] ERROR - Error issuing curl_easy_perform(handle): 28
Dec 07, 2019 16:46:04.720 [0x7efbef7fe700] DEBUG - HTTP simulating 408 after curl timeout
Dec 07, 2019 16:46:04.721 [0x7efbef7fe700] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=408):
Above indicates either a bad gateway, double NAT, or most likely a bad/slow DNS
Start by checking default gateway, as well as you directly from the box can ping something on the internet, like ping-test.net and if so, switch DNS for a short test to Google DNS, aka 8.8.8.8and 8.8.4.4
It worked for a couple hours and then remote access stopped working, so I restarted the server. Now, it’s saying I don’t have access to the server anymore after logging in.
Claiming the server is not working again, just like in the beginning, even when using the secure=0 flag.
Can someone please explain why, when I am logged in to my account, ON the local network, even on the server machine itself, it does not let me access my server? Why does plex need to claim something when I am literally running the local copy of the web client?
Is there a more permanent solution to this? I don’t want to have to re-claim this server every time something goes wrong, if I can even figure out how to fix it this time.
Yes, I tried changing the DNS server to google’s, and it is still having the same issue. I’m able to ping ping-test.net, although it takes several seconds for the first ping to happen, then it behaves fine. pings to plex.tv don’t seem to be working though, but I can access those domains just fine through my browser.
The same behavior happens whether it’s google DNS or automatic DNS.
It seems to make me log in twice when I try the above-mentioned incognito and secure=0 steps. When I launch the browser, it asks me to finish the last step of setup, then when I click ‘claim server’, it takes me to the login. I enter my login, and it goes back to the same page, I click ‘claim server’ again, it goes back to the login page, and then spins on ‘claim server’ before saying there was a problem signing into the plex server.
I’ve attached another clean log of just doing that operation, I’m not sure if there is something different since the previous time it was working and stopped.
I haven’t made any customization to the installation, it’s a fresh install as of yesterday. Last night, I tried the incognito secure=0 process again, and it worked for several hours up until this afternoon, where it failed with the same issues as before.
I tried the steps you listed regarding the permissions, but it doesn’t change anything.
I haven’t done anything to specify packet size, so I’m not sure where I would have changed anything about that.
I’m still seeing the curl/http 408 errors in the logs, so it looks like it’s still timing out. Attached the logs after 2-3 restarts, incognito or not, still having the same issues with failing to claim the server.
There appears to be active interference occurring.
I can see where it does connect to Plex.tv and is able to authenticate.
I can see playback activity occurring normally.
Then, after a time, it loses its ability to connect to the same Plex.tv servers it previously connected with.
The only conclusion I can draw is the ISP / VPN provider is activity changing or even blocking Plex.tv
Do you think it could be something to do with my router or home network configuration? Or is it failing to authenticate my plex account with plex servers, so it isn’t able to recognize what servers I have linked to my account?
Alternatively, if not, is there anything I can do to at least make this work locally? I really don’t see why I should be unable to stream even locally within my own home. I’m able to log in to my plex account on my server - why is this not enough to associate the server with my account?
I’m not using the ISP-provided modem, I’m using my own. The server computer is connected via ethernet (motherboard ethernet, not a separate ethernet card) to a netgear router, which is connected to the cable modem.
I have configured my server to have a static IP on the router, and I’ve set up port forwarding on a static port to forward 32400.
I actually set up a VPN on my PC last night and that actually let me authenticate and claim my server, which seems to imply you were correct about plex server authentication being blocked. Remote access was also working fine last night (I’m asking a friend to help me test this out to access the server), but today it’s very slow on their end - it seems to be hard limiting the bitrate. Is this something that plex might throttle based on a network issue, or something I can configure based on the settings? I’m not sure why it was working fine last night and not today.
Overall, if it actually is my ISP blocking authentication to Plex’s servers, is there a way I can at least make it work on my local network without having to constantly re-authenticate with Plex’s servers? If I have to run the VPN constantly, I don’t have a problem doing that, but if I’m only going to use it locally (which I’d also like to avoid, but if it’s the only option that’s fine), I’d prefer if there was a way to not need the VPN.
I had this problem back in August. I ended up claiming it using the app on my phone of all the bizarre things. After that it worked fine using the web interface. Never did find out why it wouldn’t let me claim it in the browser (and I tried multiple browsers too to make sure it wasn’t a problem with Chrome or cache).
