Started 2 days ago when I couldnt manage my server. Logging in via browser got me to an empty library. All my shares were gone. There wasnt a server to manage in settings. For all i knew my plex docker install was corrupted.
First thing I did was to restore from a backup from a couple days prior. I copied the entire appdata folder containing the PMS db and metadata files and overwrote the ‘corrupted’ files. Still the same behavior.
Next i tried a blank fresh install. I moved my appdata to a backup folder, and reinstalled the docker as if it were fresh. When I when to the serverIP in the browser, I got the startup screen. I attempted to see if a fresh library would work. But when I tried to claim the library, it gave the error ‘There was a problem sigining into Plex’. This is where I started to think the error wasnt my original plex install. But I still couldnt see it from the browser. Some googling and I found out that I could unclaim my server by changing the Preferences.xml. This worked and I could finally see my server in the browser, but now it wanted me to claim it. I tried the button but same error as above. I tried every option I could google: the plex-claim-script on git, the option PLEX_CLAIM in the docker options, even trying to curl the claim token on the docker console. Nothing worked.
I also read several threads that state my network is the likely cause, but I dont see how. Im getting to the server on a browser on the same network. This is the same computer that I have used for years to manage my library. Also I have not made any network changes to what has been working. I have no clue what about my network could have changed and affected this so abruptly.
I’m running Plex on unRAID and experiencing the exact same thing. It’s incredibly infuriating. I’ve scoured countless forums to no avail. Every suggested “solution” has done nothing for me. I’ve even tried setting up a new Plex server on a totally separate unRAID server. I came to the same conclusion that it must be network related, but again none of the solutions to that problem have been helpful.
Same, I tried from my backup Unraid install. Both are on the same network and same behavior there. None of my machines can claim the install on that server
same. att fiber. but i dont use their box other than for passthrough. i have my own router behind that. I cant get rid of theirs because of the fiber protocol they use
I have the same setup. I got my server working again! Here’s what I recommend trying:
Install nordlynx on your server (You’ll need a NordVPN subscription. I just paid for 1 month).
Follow these instructions to get your Private Key and enter it in the nordlynx container.
Also add a port to the nordlynx container and set the host and destination to 32400.
Edit the plex container and set the Network Type to “none”
Toggle to Advanced View and in Extra Parameters type in “–net=container:nordlynx” without the quotes.
If you’ve done everything correctly up until this point you should be able to go into the console of nordlynx and type in “curl ifconfig.io” (again without the quotes) and it should return an IP address through NordVPN that is different from your current WAN IP.
If you type the same command into the console of plex and see the same IP address then it should be routed properly.
At this point you should be ready to go to https://plex.tv/claim and get a claim code to enter into the plex docker settings. This is only valid for 4 minutes.
If the claim worked you should be able to go to your account at plex.tv and see the server.
Be sure to stop the nordlynx docker before the next steps on the 2 docker containers will be trying to use the same port.
You can then set the Network Type back to “host” in the plex docker and delete the Extra Parameters.
Now you should be able to access the local web UI for your server and it should still be connected to Plex.
YMMV but be patient. This was a huge pain to figure out. I got into a discussion on Reddit with one guy who figured out it was an AT&T issue and that was the only thing left to explore for me. Hopefully I didn’t leave anything out. Good luck!
Originally I tried using binhex-privoxyvpn but was unsuccessful in getting it working with PIA. Hopefully someone smarter than me can help you out there. If you can get that docker connected to PIA then theoretically everything else would be the same.
You can try skipping that step and move on to setting the plex network settings back and see what happens when you connect to your plex server locally.
Also you may have to remove some attributes from your Preferences.xml file before entering the claim code. Make sure you backup that file before editing it.
I tried going back to ‘normal’ to connect locally, it still behaves the same. The claim button is there but wont work.
I already cleared the Preferences.xml previously. Thats how I even got my server to show up. When the Preferences.xml is as it was days ago when working, the server doesnt show at all in Plex. Example, say my server IP was 1.2.3.4, when going to http://1.2.3.4:32400/web, I would get a userlogin, where id put in my pin like normal to get into my plex, but then id come in to an empty home, devoid of all my media. When going to the admin dashboard, the Account and PlexWeb sections exist, but my server info down below doesnt even populate.
So I made a backup of the Preferences.xml and cleared the 4 entries from the exact post you mention, and restart plex.
Now when I go to 1.2.3.4:32400/web and put in my pin, I see my media folders with the yellow exclamation icon over them, and in admin, I see my server info and options below the account and plex web stuff. In the General tab for my server, it has the claim button that wont work. But at least I can see my server info. But no method thus far has allowed me to claim the server.
So here is my solution. The issue appears to have been my pihole. Its been running for years and never been an issue but caused this. My solution (based purely on a hunch and trying to eliminate the factors on my network) was to remove it as the DNS provider in my router, and instead point to 1.1.1.3. Then after a few minutes, I went to plex and tried to claim my server again, and it worked.
TLDR; before nuking your install, settings, and configs, first try removing easy to unplug things from your network to reduce complexity.
Sorry I wasted your time with my solution. This problem seems like it can be caused by a number of different things so it’s difficult to narrow in on each person’s solution.
I have the same problem and have changed the DNS to 1.1.1.3. But I still can’t claim the server. I use a dockers container. Could it also be due to some certificates?
