it is either a bug somewhere or some browser cache
Or may be the order in which the steps are done is important?
After you delete the pin from your account -
If you now login to plex.tv/web and select settings / users
do you see multiple managed users or a pin on the master account?
If more than one account showing then delete the others leaving only the master account / unlocked without a pin
then delete the 4 registry keys and relaunch Plex Media Server and claim it
If the problem comes back - need to try different browser - one without any cached information - or try same browser but after clearing cache / cookies
Deleted the other managed user I had so I only have my master account with no pin. Accessing Plex Media Server via web browser takes me directly to my library with the server accessible and I’m signed in and it’s claimed. Yay!
With this, I added a managed user to test. As soon as a managed user is added the server vanishes. Deleting the managed user, logging out and logging in the server re-appears and is still claimed.
So, having managed users seems to cause issues with server accessibility.
@SuperDiogenes said:
Deleted the other managed user I had so I only have my master account with no pin. Accessing Plex Media Server via web browser takes me directly to my library with the server accessible and I’m signed in and it’s claimed. Yay!
With this, I added a managed user to test. As soon as a managed user is added the server vanishes. Deleting the managed user, logging out and logging in the server re-appears and is still claimed.
So, having managed users seems to cause issues with server accessibility.
Creating a managed user should not affect access - however signing in using the managed user would lose admin access
Is this Plex Media Server version 0.9.16.3 and local Plex Web App version 2.5.9?
Followed those instructions - deleted the 4 entries again. Signed back in. Server unclaimed. Claimed it, server still live and accessible. Added managed user, server vanishes. Delete managed user, sign out, sign in. Server live and accessible with only master account with no pin.
@SuperDiogenes said:
Followed those instructions - deleted the 4 entries again. Signed back in. Server unclaimed. Claimed it, server still live and accessible. Added managed user, server vanishes. Delete managed user, sign out, sign in. Server live and accessible with only master account with no pin.
After deleting the extra users and removing the registry entries we no longer have Plex Home active so no token authentication would be needed for localhost access to the server.
The moment you add a managed user, Plex Home is activated and the extra security measures kick in.
What this is suggesting is that Plex Web is probably using an old cached invalid token for the authentication.
The token it should be using is the one you see in the registry item PlexOnlineToken.
Could we prove this point by repeating this test using a browser you have not used before or one you would not be concerned with clearing all its cached data ?
Sorry I’ve taken a while to get back to you. I’ve had time this weekend to complete the process again with a new browser (Firefox). Fresh cache etc. Still the same issue.
Deleted the 4 registry entries. Restarted PMS, signed in via web app. Reclaimed my server and it was accessible. Added a managed user to enact Plex Home without a PIN. Server was accessible momentarily but as soon as I close the browser and try to relaunch the web-app the server becomes inaccessible (no longer visible) no matter which user I am using (server user or managed user).
Deleted the managed user, close web-app and relaunch and the server is accessible again.
Recently I have discovered that while I have no managed users, and I can stream to my laptop that runs Plex Home Theatre without issues. However I can no longer stream to either my Xbox One or PS4. I’m logged in on both consoles with my Plex account, both are on the same home network with the same IP’s (192.168.1.xx and same subnets) but neither can find my PMS despite PMS showing the devices as trying to connect. Does Plex Home have to be working (with at least one managed user) before my PMS will stream to my 2 consoles?
Sorry I’ve taken a while to get back to you. I’ve had time this weekend to complete the process again with a new browser (Firefox). Fresh cache etc. Still the same issue.
Deleted the 4 registry entries. Restarted PMS, signed in via web app. Reclaimed my server and it was accessible. Added a managed user to enact Plex Home without a PIN. Server was accessible momentarily but as soon as I close the browser and try to relaunch the web-app the server becomes inaccessible (no longer visible) no matter which user I am using (server user or managed user).
Deleted the managed user, close web-app and relaunch and the server is accessible again.
Recently I have discovered that while I have no managed users, and I can stream to my laptop that runs Plex Home Theatre without issues. However I can no longer stream to either my Xbox One or PS4. I’m logged in on both consoles with my Plex account, both are on the same home network with the same IP’s (192.168.1.xx and same subnets) but neither can find my PMS despite PMS showing the devices as trying to connect. Does Plex Home have to be working (with at least one managed user) before my PMS will stream to my 2 consoles?
Many thanks!
I would like to separate the issues of Plex Web failure to access the server on the machine when a user or pin added to that of a Plex app on devices failing to get through. A bug has just been identified whilst investigating problem in this forum topic with the outcome summarized here
Could you have a look at the linked post and see if making the change for Plex Web makes a different to the Plex Web access issue
So I changed the Plex web app setting to always allow insecure connections. Added a managed user and the server disappeared. Deleted the user, changed it back to “on same network as server” and my server was usable again.
Next I changed my DNS settings to use Google’s public DNS. Now I can add a managed user without losing access to the server. So it appears that using Google’s DNS settings I can add a managed user without my server disappearing which is cool. Hopefully a fix will be out at some stage so I don’t have to rely on Google’s DNS settings.
However the issue of being able to stream to either my Xbox One and PS4 is still a problem. When launching Plex on either the Xbox or the PS4, it sees both my newly added managed user and the server account. Connecting via either of those accounts still presents me with an error that my server can’t be found. I have tried changing my server setting to either “on same network as user” and “always” when falling back to insecure connections.
Until a fix is found I might try and contact my ISP to get a static IP so I can port forward. It’s something I’ll need for remote access anyway.
@SuperDiogenes said:
So I changed the Plex web app setting to always allow insecure connections. Added a managed user and the server disappeared. Deleted the user, changed it back to “on same network as server” and my server was usable again.
Next I changed my DNS settings to use Google’s public DNS. Now I can add a managed user without losing access to the server. So it appears that using Google’s DNS settings I can add a managed user without my server disappearing which is cool. Hopefully a fix will be out at some stage so I don’t have to rely on Google’s DNS settings.
However the issue of being able to stream to either my Xbox One and PS4 is still a problem. When launching Plex on either the Xbox or the PS4, it sees both my newly added managed user and the server account. Connecting via either of those accounts still presents me with an error that my server can’t be found. I have tried changing my server setting to either “on same network as user” and “always” when falling back to insecure connections.
Until a fix is found I might try and contact my ISP to get a static IP so I can port forward. It’s something I’ll need for remote access anyway.
A number of users appear to have issues with their ISP’s DNS and plex.direct url’s that are used by Plex.
There are a number of tests that can be made to confirm that the ISP’s DNS is not translating any plex.direct url as used by Plex. See https://forums.plex.tv/discussion/comment/1167819/#Comment_1167819
Switching to Google DNS or Open DNS appears to circumvent the problem. There are two forum topics that are related to this issue. I am not sure if it is specific ISPs or territory
There are also nslookups that can be checked for your own plex.direct url’s which you can pick from the xml from https://plex.tv/pms/resources.xml?includeHttps=1
@SuperDiogenes said:
So I changed the Plex web app setting to always allow insecure connections. Added a managed user and the server disappeared. Deleted the user, changed it back to “on same network as server” and my server was usable again.
Not sure why setting to use insecure connection always did not overcome the issue. Is the server secure connections set to Required or Preferred?
@SuperDiogenes said:
However the issue of being able to stream to either my Xbox One and PS4 is still a problem. When launching Plex on either the Xbox or the PS4, it sees both my newly added managed user and the server account. Connecting via either of those accounts still presents me with an error that my server can’t be found. I have tried changing my server setting to either “on same network as user” and “always” when falling back to insecure connections.
The settings you mention are not server settings but plex web client app settings. Not sure if the Plex for PlayStation or Plex for XboxOne have the equivalent options.
