This is just an example of a third party tool that stops Plex Media Server working - you may have this or something else that is giving rise to these issues
Have a look at what you have installed on your system and see if you can spot some program that may be interfering. The culprits would be proxy, vpn, and program like the tcp optimizer mentioned
You could use SysInternals ListDLLs to see what 3rd Party DLLs have attached themselves to Plex
HEUREKA! I did uninstall Astrill VPN and it works now!
Although this is a bit strange. I had Astrill installed alongside PMS for a long time and it never caused issues. I also have not updated Astrill.
Iâm not using Astrill anymore, so I do not want to bother experimenting whether everything stays in one piece if I reinstall Astrill now, etc. Iâm using HMA now and it works alongside PMS. But people using Astrill might be screwed â probably worth looking into the issue for the devs checking what the problem is.
@sa2000: thank you so much for your help tracking down the issue, this is highly appreciated!!
I had the same problem (server settings unavailable), coincidentally I also use Astrill, not sure if thatâs relevant.
I solved the problem by running Plex as Administrator. My account is an administrator account, but I still need to ârun as administratorâ to give a program admin access (or whatever that does). Anyway, works great as long as I start it with run as administrator.
It should not be necessary - you could try and re-apply permissions to the local app data plex media server set of files and folders and see if that allows you to run without the elevation
If this does not, you could try to uninstall and then delete the folder
C:\Program Files (x86)\Plex\Plex Media Server
And re-install
Make sure uninstall is dine after exiting Plex media server and making sure no processes for plex remain running
@rogueqd said:
I had the same problem (server settings unavailable), coincidentally I also use Astrill, not sure if thatâs relevant.
I solved the problem by running Plex as Administrator. My account is an administrator account, but I still need to ârun as administratorâ to give a program admin access (or whatever that does). Anyway, works great as long as I start it with run as administrator.
same problem, new discovery
This does not happen until I âclaimâ my server. If I delete the server from devices, log out, restart server, and log in - manage âserverâ option reappears.
Same problem on my QNAP NAS as on my w10 laptop. I can manage server up until the point I âclaimâ my âunclaimed serverâ. If I leave it unclaimed, works fine.
@michael.spam said:
same problem, new discovery
This does not happen until I âclaimâ my server. If I delete the server from devices, log out, restart server, and log in - manage âserverâ option reappears.
Same problem on my QNAP NAS as on my w10 laptop. I can manage server up until the point I âclaimâ my âunclaimed serverâ. If I leave it unclaimed, works fine.
W10, windows firewall off, same in IE and FF
lets get some diagnostics. you should be able to enable plex web logging (settings / web / show advanced / debug) and select verbose logging and then save the changes. And then restart the server and reproduce the problem and get the plex web app log (settings / web / show advanced : debug / view log) and copy and paste to text file and attach together with a screenshot (showing url and time of day) and Plex Media Server.log and also the PMS Plugin Logs\com.plexapp/system.log
Does the problem arise when using local host as well ? http://localhost:32400/web
and have you tried signing out and in within plex web (top right corner)
IE, FF, secure, unsecure, as long as i follow the process I can replicate it.
Firewall is off, no VPN services, signout, signin, restart services - once I claim the server I lose the ability to manage âserverâ functions. Remove the device, restart service, login - itâs back.
@michael.spam said:
IE, FF, secure, unsecure, as long as i follow the process I can replicate it.
Firewall is off, no VPN services, signout, signin, restart services - once I claim the server I lose the ability to manage âserverâ functions. Remove the device, restart service, login - itâs back.
@michael.spam said:
PIN removal seems to have fixed it.
Add PIN, server not available. Remove PIN, itâs there.
Why would that cause this behavior?
Well the pin is part of the Plex Home feature available for servers owned by PlexPASS users. A person not having PlexPASS can join a Plex Home for another user and would then need a pin for the access to the server shared by the PlexPASS user with the person not having PlexPASS
However, adding a Pin to an account would result in all access needing a pin and if the person sets up his / her own server then that too would also needs to be accessed through a pin - which means it needs to be part of a Plex Home. I have already flagged this to the development team as needing some better documentation - messages when a pin is added
@âmichael.spamâ said:
PIN removal seems to have fixed it.
Add PIN, server not available. Remove PIN, itâs there.
Why would that cause this behavior?
Would like to get to the Plex Development team the exact steps to result in the lockout. But first need to check the starting position with respect to the server settings. Could you export the following registry area to text file and send it to me by Private Message
Area to export using RegEdit
HKEY_CURRENT_USER\Software\Plex, Inc.
And the exact steps to reproduce the problem - and if the server or plex web were signed in with other plex.tv usernames beforehand
sure; I replicated the problem by just adding the PIN - restart service - no access. Remove PIN - restart - access.
No need to remove the devices.
EDIT:
I should have included in this post that I claimed my server and was able to manage the server; however once I add a PIN âserverâ settings are not available.
@michael.spam said:
sure; I replicated the problem by just adding the PIN - restart service - no access. Remove PIN - restart - access.
No need to remove the devices.
Thank you. I have reproduced the problem and passed on the details to the Plex team
I did a lot of testing and the factors that affect this are: Secure Connections, DNS Rebinding Protection, Allow Fallback to insecure connections and whether Remote Access is enabled or not !
Could you try a simple test - with the pin added you will fail to get to the server. After this go to settings / web / show advanced and change the Allow Fallback to insecure connections from Never to Always and then sign out and sign in within Plex Web App (top right corner) and see if this now lets you through with the pin in place.
confirmed, insecure allowed management.
I donât think I fiddled around with many settings. My goal was to get it tested to see how the platform compares to XBMC/Kodi.
@michael.spam said:
confirmed, insecure allowed management.
I donât think I fiddled around with many settings. My goal was to get it tested to see how the platform compares to XBMC/Kodi.
That is good in that it ties in with what I discovered and the bug that has just been unearthed
A fix will be out soon - not sure if it is going to be in Plex Web 2.6.2.
A number of factors affect the outcome resulting in access to the server on the same machine fails through localhost or 127.0.0.1 when the following scenarios arise:
Server Secure Connections set to Required or Preferred (default)
Plex Web App default setting of Allow fallback to insecure connections set to Never
Pin added to the server account
Server not enabled for Remote Access or Remote Access through public IP and port not working
and Router DNS Rebinding Protection in place making local access through TLS secure connections via local-ip plex.direct route not available
To explain - with the pin added the connection through 127.0.0.1 is failing and that will be fixed. It tires to find alternative route. With secure connections in place, it has to use one of the 2 secure plex.direcct urlâs. If DNS Rebinding protection is in the router then the local ip plex.direct url fails. Only other option would be the remote access public ip and public port plex.direct url. If remote access is not enabled then this will not be available and resulting in failure to connect to the server
Until the bug is fixed - the problem can be avoided by
