Server Version#: 7.1.4
Player Version#: 1.42.2.10156
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
Hi everyone,
I’m currently unable to claim my Plex server, and I suspect the issue may be related to the recent password reset prompted by the security breach. Like others here, I started experiencing problems shortly after updating my credentials. Initially, I lost intermittent access, but now I can’t claim the server at all—even for basic home streaming.
Here’s what I’ve tried so far:
Edited the Preferences.xml file manually
Ran the UserCredentialsReset.sh script
Retrieved and embedded the token from the Plex website during setup
I also rebuilt my entire network environment (I’m running OPNsense), thinking it might be a connectivity issue. The server worked briefly after that, but then dropped off again without warning.
At this point, I’m out of ideas. If anyone has suggestions I haven’t tried, I’d really appreciate your input. Thanks in advance!
Thank you for the follow-up. You’re absolutely right—I neglected to mention that I’m running Plex on unRAID as a Docker container. The container is configured with a custom bridge network and assigned a static IP address, which I can access without issue.
I’ve already attempted the step you suggested, but unfortunately, the server still reports as “Unsecure and Unclaimed.” This is particularly puzzling, as I’ve never encountered this issue before in all my years of using Plex.
To troubleshoot, I’ve exhausted the suggestions found across the forums and have also tried various modifications to both the Docker configuration and the appdata files, but the issue persists. Notably, this behavior only began after we were required to change our Plex account passwords. I’m not sure where the disconnect occurred, but something seems to have broken in the authentication or claim process.
For clarity, I’ve included screenshots that illustrate the current setup and the error message. Any further guidance would be greatly appreciated.
[SOLVED] Plex Server Won’t Claim on Unraid (Docker DNS Fix)
Problem
After setting up Plex on Unraid, I couldn’t claim the server. Clicking “Claim” would spin endlessly and fail. Plex also prompted for updates even though it was already up to date. The issue turned out to be broken DNS resolution inside the Plex Docker container, which prevented it from reaching plex.tv and related services.
Solution: Fix DNS for Docker on Unraid
1. Verify DNS Issue Inside the Plex Container
Open a terminal in Unraid and run:
bash
docker exec -it plex bash
Then test DNS resolution:
bash
curl -I https://plex.tv
If you see:
Code
curl: (6) Could not resolve host: plex.tv
then DNS is broken inside the container.
2. Fix DNS on the Host (Unraid)
Unraid controls Docker’s DNS via /etc/resolv.conf. To fix it:
Open Unraid terminal (not inside the container)
Run:
bash
nano /etc/resolv.conf
Replace the contents with:
Code
nameserver 8.8.8.8
nameserver 1.1.1.1
Save and exit:
Press Ctrl + O to save
Press Ctrl + X to exit
3. Make DNS Change Persistent
Unraid may overwrite /etc/resolv.conf on reboot. To make it stick:
Go to Settings → Network Settings
Set DNS Server 1 to 8.8.8.8
Set DNS Server 2 to 1.1.1.1
Click Apply
This ensures Docker containers inherit proper DNS settings.
4. Restart Plex Container
Back in Unraid:
Go to Docker tab
Click Restart on the Plex container
5. Test Again Inside the Container
Run:
bash
docker exec -it plex bash
curl -I https://plex.tv
You should now see:
Code
HTTP/2 301 Moved Permanently
This confirms DNS is working.
6. Claim Your Plex Server
Go to the Plex web interface and click “Claim Server.” It should now succeed instantly.
Result
Plex was able to reach its services, stopped prompting for phantom updates, and successfully claimed the server. The root cause was DNS resolution failure inside the Docker container, which Unraid’s default settings didn’t fix until manually updated.
