Server Version#: 1.42.2.10156-f737b826c
Player Version#: 4.152.0
Since about five days ago, all the web browsers I use (Firefox/Chrome) cannot connect to my Plex Media Server. At first I see “No Content Available”, and when I try to connect, I get “app.plex.tv is unable to connect to [server] securely”. This issue affects all the machines on my network I have tried.
The apps I use–PlexAmp/Plex on my Android phone, the NVIDIA Shield Pro app, the Windows app, the iPad app–are all connecting just fine. I did some research, and one solution seems to be to change the DNS settings for my home router to use Google or some such. That probably won’t be an option at this juncture because I have an AT&T BGW320-500 router, and the configure page for its DNS settings currently comes up with a (custom) Page Not Found error. I would have to start a trouble ticket with AT&T first, apparently, to try such a solution. I’d rather not go this route if possible.
Chrome on the machine where PMS is running can connect just fine. I realize that’s a probably different matter because the URL is 127.0.0.1:32400 and not going through app.plex.tv, but I thought I’d better mention it since it’ll likely be asked. All the machines I’m working with, including the one running PMS, are using Windows 10.
So far I’ve tried clearing browser cache, using ipconfig to flush DNS, rebooting the PCs, and restarting the router.
DNS server settings do exist on pretty much all client devices as well.
I’d try to set it on one PC to 8.8.8.8 as a test. If afterwards connections work on this machine, you know what to do.
Or insert a second router into your home network. (One that you can configure like you want, and not how your ISP would like.)
However, if the router of your ISP cannot be set into a pure “modem mode”, you would have to create port forwardings on both routers in order to keep remote access to your Plex server functional.
(A DNS-based internet filter appliance like a Pi-hole can also take the role of the second router.)
Second thought: look for settings about “DNS rebinding protection” on your outer. I doubt you will find them in this model, but if you do, put the domain plex.direct into the whitelist of domains which are exempt from this protection.
Connect to your PMS using Chrome on the machine where PMS is running (which you said works) and be sure your Settings → Network → Secure connections = Preferred
If you change it, be sure to Save Changes.
Consider that there are two web based Plex players and possibly test how each works. I’ll try to explain. Let’s say you have a home network with the following desktop computers:
192.168.1.2 = a random Win10 desktop that can’t connect via web browser 192.168.1.50 = your Win10 machine that runs PMS
There are two browser based players Plex offers, and they load their code differently:
the Hosted Web App - v4.152.0 that loads its code from plex.tv.
the bundled web app - v.4.147.1 that loads its code from the PMS server v.1.42.2.10156
Imagine you sit down at the first desktop I listed, 192.168.1.2, the random desktop.
You can connect using several methods from a browser:
Using the hosted web app which is always a secure connection (https)
Using the bundled web app securely at https://192.168.1.50:32400/web
Using the bundled web app insecurely at http://192.168.1.50:32400/web
It’s worth experimenting to see which player connects, if any.
I’m curious what variables we can reduce. Player version is one.
Insecure vs Secure connections is another.
For testing note that any VPN or Firewall can interfere.
Following the excellent advice from @OttoKerner, you can also override your router’s DHCP supplied DNS servers inside Win10 Settings:
I took your suggestion and tried going to a desktop PC on my network, opening Chrome, and loading my PMS using the IP address and :32400/web. It worked! I was able to conect to my PMS, but without https. Insecurely only. I do have Secure Connections set to Preferred in PMS settings. Changing the DNS servers inside Windows 10 had made no difference.
Here’s the kicker and some good news, however. After forcing the bundled web app to load insecurely using the IP address, now the hosted web app works! I did this for both Firefox and Chrome on this PC and the issue is gone so far.
Here is the next mystery, though. This solution did not work on the 2nd PC I tried, just on the first one. Weird. The first PC is a desktop connected to the router via LAN, whereas the 2nd is a laptop connected via wi-fi. Both are Win10.
Seems like I’m experiencing some sort of local DNS problem. Yeah?
You’re welcome. Hard for me to say what it is, but possibly modify the DNS servers on the other comps too. Check that they are on the same subnet as the PMS server. And it’s safe to remove stale browsers from your list of Settings - Authorized Devices - Desktop, for example all the duplicates from before the password reset a month ago. There are ways to get detailed logs about the negotiations with Plex, but that’s sort of gory for a Saturday
Confirmed. Going about the same procedure on the laptop (changing DNS to 8.8.8.8 and forcing the bundled web app in the browser) has resolved the issue there as well. It seems I have a solution, even though I don’t understand the cause of the problem. To my knowledge it was not anything I did intentionally or accidentally. Perhaps a recent Windows update caused it.
I appreciate the help. I use Plex on just about every device obviously, and sometimes it’s really nice just having it there with my other browser tabs!
The problem keeps coming back, on both PCs. Twice in the past few days I tried the web app and it could not connect to PMS, just as before. Loading the bundled web app without security, going back to the web app, and then waiting a moment fixes the problem, at least temporarily. Meanwhile all the non-browser apps I use have been working fine.
I’m thinking the cause must be my internet router, which remember is missing the configure page for DNS settings and such. I’d have to start a trouble ticket with AT&T and tell them about my Plex libraries. etc. I’d rather not go down that road. Nor do I want to add a 2nd router or any other workarounds. I appreciate all the assistance so far because it has given me hope there is a fix!
There’s a small chance Plex’s authentication system is having transient issues. There has been some discussion of this on other topics confirmed by Elan. I would hold off making changes and see how it pans out over the next week.
When it happens, note the time of day, and do a Settings → Troubleshooting → Download Logs when you can. Check your Plex Media Server.log inside the zip for HTTP 500 errors, which are internal server errors on their end.
