In Chromes “Certificates View” (CTRL-SHIFT-i) under Secure Origins when I click on https://assets.plex.tv I see some Symantec ‘Vega’ log
So to me it seems like it’s on your side?
edited @sa2000 to remove image
Looks ok and the chrome dev console log does not show any error
The server RazorPlex is showing on plex.tv as not seen for 11 hours which is a bit strange.
Could you get me the server logs
So restart the server and then try again to access through Plex web
and then copy out the Logs folder and zip the copy and attach
and note down the time of attempting to connect to the server
Logs would be in C:\Users\xxxxxxxx\AppData\Local\Plex Media Server\Logs
Perhaps you could capture a video to show what actually happens when you open chrome and go to
http://localhost:32400/web
I did not ask = but may be there is an add-on / extension that is causing the problem
You could also test with staring incognito session
and also without extensions
and one more thing to check - to eliminate
Control Panel / Internet Options / Connections / LAN Settings
Is the Proxy Server box ticked ?
If it is, click on the details to see what is there
@sa2000 said:
Looks ok and the chrome dev console log does not show any error
so we must assume that “404 (not found)” as shown on the bottom of my last screenshot is no error from your perspective or at least you did not mean this kind of error?
The server
RazorPlexis showing on plex.tv as not seen for 11 hours which is a bit strange.
I did not ask = but may be there is an add-on / extension that is causing the problem
I have access now on https://app.plex.tv/desktop# (3.44.1) AND http://127.0.0.1:32400/web/index.html# (3.39.5) and PMS “RazorPlex” is online almost 24/7.
So it proves that whether my Windows system, nor my browser or any of its add-ons, nor my security software or anything else on my side is corrupted or incompatible or else what. Agree?
As soon as you changed the bundled (local) app version from to 3.39.5 it worked fine as it was a week ago and before. So why could it still be of interest what’s on my system?
@sa2000 said:
and one more thing to check - to eliminate
Control Panel / Internet Options / Connections / LAN Settings
Is the Proxy Server box ticked ?
If it is, click on the details to see what is there
No Proxy:
@RazorPlex said:
so we must assume that “404 (not found)” as shown on the bottom of my last screenshot is no error from your perspective or at least you did not mean this kind of error?
The 404 is ok - it is expected if there is no Plex Home (managed accounts)
@RazorPlex said:
As soon as you changed the bundled (local) app version from to 3.39.5 it worked fine as it was a week ago and before. So why could it still be of interest what’s on my system?
I am a bit confused with this statement. You are saying when we changed the version from 3.37.2 (bundled in 1.12.0.4829) to 3.39.5 (bundled in 1.12.2.4929 - actually as from 1.12.1.4871) then the problem went away. But you said before here
Updated to Server 1.12.2.4929 which still has Web 3.44.1 and the problem still persists.
That is actually not true as 1.12.2.4929 has 3.39.5 and not 3.44.1 and it is contradictory with the new statement
As soon as you changed the bundled (local) app version from to 3.39.5 it worked fine
@RazorPlex said:
The server
RazorPlexis showing on plex.tv as not seen for 11 hours which is a bit strange.
I did not ask = but may be there is an add-on / extension that is causing the problemI have access now on https://app.plex.tv/desktop# (3.44.1) AND http://127.0.0.1:32400/web/index.html# (3.39.5) and PMS “RazorPlex” is online almost 24/7.
So it proves that whether my Windows system, nor my browser or any of its add-ons, nor my security software or anything else on my side is corrupted or incompatible or else what. Agree?
May be it was unclaimed - and I mentioned the known issue that will be fixed in 3.41.2 for unclaimed servers.
May be some of the issues were to do with the server outages for plex.tv?
May be it was to do with changing user accounts ? what is this Plex-klno account showing on screenshot on your first post? http://forums.plex.tv/discussion/314787/there-was-an-error-signing-in
@sa2000 said:
@RazorPlex said:
As soon as you changed the bundled (local) app version from to 3.39.5 it worked fine as it was a week ago and before. So why could it still be of interest what’s on my system?
I am a bit confused with this statement. You are saying when we changed the version from 3.37.2 (bundled in 1.12.0.4829) to 3.39.5 (bundled in 1.12.2.4929 - actually as from 1.12.1.4871) then the problem went away. But you said before here
Updated to Server 1.12.2.4929 which still has Web 3.44.1 and the problem still persists.That is actually not true as 1.12.2.4929 has 3.39.5 and not 3.44.1 and it is contradictory with the new statement
As soon as you changed the bundled (local) app version from to 3.39.5 it worked fine
As you might have realized already, the whole problem can be very misleading. Even though my native language is turkish and german and therefore the english language may be trappy for me, in this case I think the epicenter is that users like me first of all had to understand, that there are different versions for what describes the PMS.
For most of the users like me, there is just their PLEX server - mostly on a windows non-server machine (maybe you have statistics about the users different kinds of OS platforms) - hosting the own movie library which can be watched from different PLEX apps and versions (TV app, iOS/android mobile-apps, other PCs and browsers and so on…) over network or on the own local PLEX server itself. And then there are different services to PLEX.tv which also provides other services like movie databases, agents and so on in order to identify and tag our movie libraries.
To put it in a nutshell, when I wrote:
As soon as you changed the bundled (local) app version from to 3.39.5 it worked fine as it was a week ago and before. So why could it still be of interest what’s on my system?
or
As soon as you changed the bundled (local) app version from to 3.39.5 it worked fine
I was confused about the different LOCAL versions of PMS, which as I presume are PLEX SERVER, PLEX WEB and PLEX BUNDLED APP. So as long as I couldn’t login to the LOCAL http://127.0.0.1:32400/web I could not know the version of it and confused it with the version of https://app.plex.tv/ and as soon as I could relogin again to LOCAL I thought the version has been changed in the background.
When I said
I have access now on https://app.plex.tv/desktop# (3.44.1) AND http://127.0.0.1:32400/web/index.html# (3.39.5) and PMS “RazorPlex” is online almost 24/7.
…and I hadn’t have access right after the update to PMS v 1.12.2.4929 but as soon as I restarted the server.
@sa2000 said:
May be it was unclaimed - and I mentioned the known issue that will be fixed in 3.41.2 for unclaimed servers.
May be some of the issues were to do with the server outages for plex.tv?
a week ago and since then to yesterday?
May be it was to do with changing user accounts ? what is this
Plex-klnoaccount showing on screenshot on your first post? http://forums.plex.tv/discussion/314787/there-was-an-error-signing-in
I changed my Plex name and the e-mail address in the screenshot manually to hide some “personal info” (if you check it exactly you’ll see it) but you know, it seemes like if we unsavvy users don’t watch out it might be that even security tokens can be captured while providing screenshots of chrome console logs.
Thank you by the way for deleting my last screenshot because of that threat.
Look, what you must know is, I didn’t manipulate or installed anything which could have caused the problem on my windows 10 machine which is my PLEX server. “Everything” just worked fine until somewhere around end of march where suddenly the mentioned LOGIN PROBLEMS appeared.
Today after updating to PMS v 1.12.2.4929 and restarting the server the problem has gone and it seems working as I expect it and it was a week ago and before. So you guys know best what exactly has changed with what version and the unclaimed server problem.
In spite of the time I had to invest on this case I thank you for the support and for enriching my technical experience concerning PLEX versions a bit.
Why do we have these 3 versions btw?
- PMS v1.12.2.4929 (Server/Main server version)
- https://app.plex.tv v3.44.1
- http://127.0.0.1:32400/web v3.39.5
more precisely why do we need 2. AND 3. and not just 2. OR 3.?
A graph showing the architecture of the whole PLEX build would be helpful - maybe as a sticky info?
What users (like me) expect is just: Never change a running system and that the PMS hopefully runs flawless. And I think that’s also what we payed for with the Plex Pass: a running system.
WE ALL LOVE PLEX <3 (when it works)
