I made a mistake…I went to install Ubiquiti Networks wireless controller software on the same server running my plex/nzbdrone/couchpotato/sabnzbd/transmission setup and…well the Plex web interface stopped working.
I had the same issue with transmission but removing it and re-installing it corrected that problem. I have already tried to uninstall plexmediaserver through apt-get (running ubuntu 14.04.5) and then reinstall with the latest plexmediaserver 1.2.7.2987 deb package with the same issue. I can still access the environment through the Plex app on my different devices but the web interface won’t load. I’ve also tried restarting the services, etc.
The only ERROR messages in the Plex Media Server.log file are:
Nov 16, 2016 11:30:14.543 [0x7f13a97fc700] ERROR - Network Service: Error in browser handle read: 125 (Operation canceled) socket=-1
Nov 16, 2016 11:30:19.630 [0x7f13a17fc700] ERROR - downloadContainer: expected MediaContainer element, found html
Nov 16, 2016 11:30:19.630 [0x7f13a17fc700] ERROR - IVA: Error downloading trailers for source 2.
Any thoughts? I don’t get why a re-install didn’t correct any problem and I’m not linux expert…just a linux wannabe.
As a side note all of the other services are working after removing the Ubiquiti software that I was attempting to install. This type of issue pushes me more and more towards a docker-based approach but I just don’t have the time to learn docker and the systems that are out there don’t appear to be documented well (at least for me).
EDIT: And a new finding, I can get to the web interface if i go through https://app.plex.tv/web/app; however, i can’t access it via ip:32400/web
are you able to get server settings through the hosted plex web app interface ?
If you are, please enable debug logging on the server (settings / server / general) and then restart the server
then try to access
You do have a pin and Plex Home - so it is important that the web browser session is signed in to the right plex.tv account
Take a screenshot of the web page and if you can with the login dropdown visible to show which account is signed in. Please do not crop so that one can see the displayed url and time when it fails to get to the server
and attach that together with the full Plex Media Server.log file
sa2000, i have the logging enabled already for the server (as well as the web portion). The connection doesn’t “fail” per say, it just loads forever and never completes when going to the direct link.
That said, I’ve opened the interface through the hosted plex web app and took a screenshot, i’ve also taken a screenshot of the time i tried to access the ip:32400/web link and then attacking the Plex Media Server log.
I can see in the log that you are accessing the server (which is on 192.168.0.9) from a PC with IP address 192.168.0.6
Did you try directly on the server through http://localhost:32400/web or http://127.0.0.1:32400/web - ?
what happens ? screenshot with log?
I would not expect http://192.168.0.9:32400/web to work from another machine because that is http and not https and the default for the web app is Never to fallback to http. You can change web setting / general / show advanced : to allow fallback to insecure connections to be always or on same network.
what would work - if you have no DNS Rebinding Protection blocking this on your router, is this url https:192-168-0-9.383761bf5b8243f5b967ca308647caee.plex.direct:32400/web
You can test for DNS Rebinding Protection in your default dns by doing nslookup 192-168-0-9.383761bf5b8243f5b967ca308647caee.plex.direct
and testing with google dns nslookup 192-168-0-9.383761bf5b8243f5b967ca308647caee.plex.direct 8.8.8.8
Something must’ve changed because I’ve always accessed the Plex interface from a standard http connection since I didn’t take the time to deploy SSL certs throughout my network and only having those self-signed certs in use.
Anyways, https is working as you’ve mentioned. As well as the DNS Rebinding method (which I have to look into why I’m allowing that on my firewall).
As for the local connections, those aren’t possible unless I were to try one of the CLI interpretation engines for web as I’m running Ubuntu Server in headless mode.
Thanks for taking a look at pointing out the solution.
There is a web setting that you can change in general settings - set it to always fallback to insecure connections or to fallback when on sane network
You can also change server network settings to disable secure connections. But web client would also need to have settings changed to fall back to insecure connections to be set to ALWAYS
