I’m having the same problem too. Other ways to access plex work besides my computer web app. I’m using Windows 11
Hello,
Same problem here, have you find an issue or we have to wait for plex solve this?
TY
Clicking on the plex app in the Windows taskbar gives me the “internal server error” dialog after asking me to sign-in. Going to app.plex.tv works just fine, but that doesn’t help when trying to stream through the app on my Apple TV.
Same issue here, cannot access Plex server but the server itself is working fine. My already logged in clients (apple TV’s) can still access but im unable to access it via any web browser from multiple PC’s.
Same here. Win 11. How come there is no fix for this after 1 week?
Has anyone found a fix yet?
I’ve had the issue until this weekend, found all the old threads and subscribed to this one just before it was solved.
What worked for me was to log out my server and then log it back in. After that it took a couple minutes for the issue to resolve. I’m not sure, though, if my action and the resolution are related.
So no fix in site for over a week now? My laptop refuses to connect. Thankfully my main PC is still connected. Mobile apps fine. Internal server error trying to connect directly via a 192.168 address. I’ve disabled every ad blocker in browser and PiHole no luck. Ugh.
EDIT: Finally got in. Brave browser. Disable literally any extension to do with adblocking . Then shut down PiHole. Login worked. I run an external port to access outside house as my NAS that hosts Plex (natively not docker/portainer) is sitting on Tailscale.
1 Like
Same here, all of a sudden it stopped working.
I was also able to get in after bypassing Pihole as my DNS. Can Plex tell us which sites are needed for logins now?
Environment:
Plex Media Server on Windows
-
Pi-hole running in Docker
-
Unbound configured as the upstream resolver
The Issue
When accessing Plex via https://app.plex.tv/web, the browser failed to connect to the local server.
Developer console showed errors such as:
[Servers] Failed to request resources through plex.tv
[Connections] All connections to [Bundled] failed
analytics.plex.tv:1 ERR_CERT_AUTHORITY_INVALID
clients.plex.tv/api/v2/user 500 ()
Disabling Pi-hole immediately resolved the problem.
The Cause
Plex uses hostnames like xxxxxxxx.plex.direct to reach your local server over HTTPS.
These names resolve to private LAN IP addresses — intentionally.
However, Unbound and Pi-hole include DNS rebinding protection, which blocks “public” domains that resolve to private IPs.
That protection is great for security, but it breaks Plex discovery.
The Fix
1. Tell Unbound to trust
plex.direct
Edit your Unbound config file (mounted in Docker, often something like 10-local-zone.conf or pi-hole.conf under /etc/unbound/unbound.conf.d/).
Inside the server: section, add:
private-domain: "plex.direct"
Example:
server:
private-domain: "local.lan."
private-domain: "plex.direct"
Then restart Unbound:
docker restart unbound
(or if Unbound runs inside Pi-hole: docker exec -it pihole pihole restartdns)
2. (Optional) Tell Pi-hole’s dnsmasq the same thing
Create or edit a file such as /etc/dnsmasq.d/99-plex.conf
and add:
rebind-domain-ok=plex.direct
Restart Pi-hole:
docker restart pihole
The Result
Once these lines are in place, Plex connects immediately through Pi-hole and Unbound — no more 500 errors or failed connections.
Why It Works
Those directives disable DNS-rebind blocking only for plex.direct, allowing Plex’s legitimate local HTTPS connections while keeping the rest of your DNS protection intact.
Summary:
If Plex fails to connect when Pi-hole + Unbound are active, add
private-domain: "plex.direct"
to Unbound’s config (and optionally rebind-domain-ok=plex.direct for dnsmasq).
Restart both containers — Plex works again.
1 Like
I have my Plex server running on Synology NAS. Been working fine for years. Today I cleared my Chrome browser cache to address another issue…and since then have been getting the “Internal Server Error…” nonsense on my Chrome browser. After several minutes of dealing with this, I logged in on my laptop using the Windows Plex App. Got in fine. After that, I was able to login via the Chrome browser without any problems.
Same here. It is utterly unacceptable to be unable to access your local webui server for your locally running client. Everything bad about Plex comes from the insistence on having a plex.tv account associated with servers. It’s fine that it is ALSO an option, but it should be secondary at all times.
They seems to have updated the password policy, had to reset the password and make a new one with 10 characters, upper, lower case and special case
Any news Plex ? We need a fix and an update from you
I can’t login on any web browser and it’s a need
It seems to be working now. At least for me.
