Since a week ago when I start my PMS locally over the taskbar icon as usual, the local address of PMS is called: http://127.0.0.1:32400/web initially, but after 1 second (attempting to load the start page of PMS) I get an error message:
[There was an error signing in]
Before the error occurs, the local address in the browser address bar changes to a humangeous address line of about 500 chars:
If I just call the first part of the address: https://app.plex.tv/
it’s OK and it loggs me in as usual and the address doesn’t change.
So I could always start the web page of PMS with https://app.plex.tv/ or even use a bookmark favorite to this but it’s a few unconvenient clicks more as I have to start the browser first and it’s weird why it should not work the way it used to a week ago and before.
Where can I change this behaviour? It seemes like a server internal routing like you know in the hosts-file (C:\windows\sytem32\drivers\etc\hosts) but my hosts-file is unmodified (standard).
So I assume it’s in the PMS web server config somewhere?
I remember this happening to me before. I believe I substituted the loopback address with the server address. I don’t think it should ask for authentication. however, in “Network” in server settings, you can identify your LAN networks and even add the own server’s address in the “List of IP addresses and networks that are allowed without auth” field. But that might be overkill.
Thx lanboyguyton.
I’m using Win10 x64 as PMS. So not really “server settings” there as it would be on a Win Server. I’m curious if there is such a setting on the PMS confug somewhere?
Yes, there is, that’s actually what I meant, sorry.
If you click the wrench icon in plex web then click on the server tab, that’s what I meant for Server Settings.
But, unfortunately none of the settings that I tried over the WebUI under [Server] - [Network] did solve the problem.
I tried putting 127.0.0.1, 192.168.1.50 (my local LAN-IP)
also tried own Web-URL: https://app.plex.tv/desktop in the appropriate section.
Of course SAVED settings and even restarted the PMS.
But everytime I try to call PMS WebUI over the ICON from the taskbar the problem persists. The same whenever I enter: http://127.0.0.1:32400/web in any browser - oh yeah did I mention - it’s the same problem with IE 11 / EDGE and CHROME. Vice versa https://app.plex.tv/desktop works on all mentionned browsers.
I am aware of a problem with the version of Plex Web that is bundled with Plex Media Server (the one that responds to http://127.0.0.1:32400/web or http://local-ip-of-pms:32400/web where if the server is unclaimed, there would be a request to authenticate to access the server. This will be fixed in bundled Plex Web 3.41.2 which is expected to be bundled into the next release of Plex Media Server (1.12.3)
I am aware of a problem with the version of Plex Web that is bundled with Plex Media Server (the one that responds to http://127.0.0.1:32400/web or http://local-ip-of-pms:32400/web …
I have version Web: 3.44.1 / Server: 1.12.0.4829.
Are there “unbundled” versions around that don’t respond to http://127.0.0.1:32400/web or http://local-ip-of-pms:32400/web or how do you meant that? Sorry my native language is german. Maybe I just don’t understand it right.
where if the server is unclaimed, there would be a request to authenticate to access the server.
When is a PMS unclaimed? Why? Why did this happen with this version? Why only me? Are there ways to reclaim it or only with the next fix?
This will be fixed in bundled Plex Web 3.41.2 which is expected to be bundled into the next release of Plex Media Server (1.12.3)
When can we expect Server v 1.12.3? Bundled with 3.41.2??? I already have 3.44.1.
So, when I get it right I have the hosted web app? Or more precisely I have the bundled AND the hosted Plex web and whenever the bundled one is called, the problem happens?
Would be great if you could explain all questions (if you can).
@RazorPlex said:
Updated to Server 1.12.2.4929 which still has Web 3.44.1 and the problem still persists.
There are two different versions of the web app
Version 3.44.1 is the one you get from the cloud hosted app available through url https://app.plex.tv and https://plex.tv/web
Version 3.39.5 is the current bundled version (one embedded in Plex Media Server and released with it) - it is used when you go through urls http://localhost:32400/web or http://127.0.0.1:32400/web or http://192.168.1.50:32400/web
I see in plex.tv settings for your server that you have added a Custom Server access URL of app.plex.tv - this would only complicate matters and troubleshooting issues and may actually be the reason you have issues - please clear the field (in Settings / Server / Network / Show Advanced) and save changes and restart the server
When is a PMS unclaimed? Why? Why did this happen with this version? Why only me? Are there ways to reclaim it or only with the next fix?
A server is unclaimed if settings / server / general shows it as not signed in to plex.tv
So, when I get it right I have the hosted web app? Or more precisely I have the bundled AND the hosted Plex web and whenever the bundled one is called, the problem happens?
Would be great if you could explain all questions (if you can).
Once the http://app.plex.tv or https://app.plex.tv is removed from your server Custom Server Access URL - then we are in a standard configuration and can take it from there. I do not know the implications and impact of having that in the custom access url field. It was not intended to have this but to have your own domain or perhaps a vpn ip address
The reason why I set a custom URL is because the tip of @lanboyguyton above - so after the problem. Before I had nothing in there (standard config).
@lanboyguyton said:
I remember this happening to me before. I believe I substituted the loopback address with the server address. I don’t think it should ask for authentication. however, in “Network” in server settings, you can identify your LAN networks and even add the own server’s address in the “List of IP addresses and networks that are allowed without auth” field. But that might be overkill.
Now I changed it back to standard configuration, which of course didn’t change anything concerning the problem.
Would any logfile give more insight to the errors source?
I now activated IPv6 as DualStack on my Router just to see if it helps and then restarted all.
Now the URL in the browsers address bar stays unchanged as initially called: http://127.0.0.1:32400/web/index.html
but a new error message with an exclamation mark within a triangle is saying (translated from the german error message):
PLEX is not available due to maintenance.
But no worries it won’t take long.
status.plex.tv
…which is a false negative because I can still call my PMS over https://app.plex.tv/desktop and it’s also reachable from PLEX apps outside my LAN.
Find attached the console-output from the Chrome browser after reproducing the error:
@RazorPlex said:
I now activated IPv6 as DualStack on my Router just to see if it helps and then restarted all.
Now the URL in the browsers address bar stays unchanged as initially called: http://127.0.0.1:32400/web/index.html
but a new error message with an exclamation mark within a triangle is saying (translated from the german error message):
PLEX is not available due to maintenance.
But no worries it won’t take long.
status.plex.tv
…which is a false negative because I can still call my PMS over https://app.plex.tv/desktop and it’s also reachable from PLEX apps outside my LAN.
Find attached the console-output from the Chrome browser after reproducing the error:
It is unfortunate that there was an outage today - see the chart for the plex.tv application on http://status.plex.tv
Could we repeat the test now and get fresh dev console log from chrome
May be this is the issue but need to see if it is present when the plex.tv site is operational
Looks like some Symantec check on certificate
main-1-5e147fb05f10a421c106-plex-3.39.5-cafe702.js:2637 [Servers] Found all servers = plex.tv
index.html:1 The SSL certificate used to load resources from https://api.webtest.net will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See https://g.co/chrome/symantecpkicerts for more information.
2main-1-5e147fb05f10a421c106-plex-3.39.5-cafe702.js:2610 Refused to get unsafe header "Location"
(anonymous) @ main-1-5e147fb05f10a421c106-plex-3.39.5-cafe702.js:2610
See whole Chrome console log N°2. I’m starting to feel like a labour rat testing some undocumented features and I wonder, if I’m the only one who turns in circles or am I the one at all.
Restarted PMS and now it works back normal as I have the bundled web version 3.39.5 now with Server version 1.12.2.4929.
Even though I’m happy that it works as usual again and being thankful for the support (finally after a whole week!) I must wonder what you guys are experimenting in the background. I mean when will be the next time you screw up a working system just to let your users scream for help and waste their times?!
It’s not to you personally @sa2000 but your managing brainies and their understanding of customer satisfaction.
See whole Chrome console log N°2. I’m starting to feel like a labour rat testing some undocumented features and I wonder, if I’m the only one who turns in circles or am I the one at all.
I am more concerned about this
The SSL certificate used to load resources from https://api.webtest.net will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See https://g.co/chrome/symantecpkicerts for more information.
What security product do you have running?
Just wondering if it is using its own certificate
Could you check what certificate shows up when you go to plex.tv
Could you get screenshots of the security certificate info
that error in the log is explained here https://dzone.com/articles/chrome-distrusts-ssl-certificates
But the plex certificate is not issued by Symantec and so I am wondering if you have some software that is interfering with the certificate
