edit original post on 4/20
@sa2000 said:
@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 Connectionsset toRequiredorPreferred(default)- Plex Web App default setting of
Allow fallback to insecure connectionsset toNever- Pin added to the server account
- Server not enabled for
Remote Accessor Remote Access through public IP and port not working
andRouter DNS Rebinding Protectionin place making local access through TLS secure connections via local-ip plex.direct route not availableTo 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
- enabling remote access and getting it to work
or- overcoming DNS Rebinding Protection (may be possible by adding Google DNS to the router DNS) or going for suggestions mentioned on this support page https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections section on
DNS Rebinding
or- changing Plex Web App setting to always allow insecure connections
Did a fix ever come out for this? Iām having this same issue on PMS for Linux. Every so often server settings will become unavailable until I restart Plex. This is the case whether Iām trying to access from plex.tv/web or from localip:32400/web.
@IamSpartacus said:
@sa2000 said:
@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 Connectionsset toRequiredorPreferred(default)- Plex Web App default setting of
Allow fallback to insecure connectionsset toNever- Pin added to the server account
- Server not enabled for
Remote Accessor Remote Access through public IP and port not working
andRouter DNS Rebinding Protectionin place making local access through TLS secure connections via local-ip plex.direct route not availableTo 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
- enabling remote access and getting it to work
or- overcoming DNS Rebinding Protection (may be possible by adding Google DNS to the router DNS) or going for suggestions mentioned on this support page https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections section on
DNS Rebinding
or- changing Plex Web App setting to always allow insecure connections
Did a fix ever come out for this? Iām having this same issue on PMS for Linux. Every so often server settings will become unavailable until I restart Plex. This is the case whether Iām trying to access from plex.tv/web or from localip:32400/web.
Not released yet
I went to uninstall progās and ran a repair. Worked for meā¦
Iām having this same issue ever since installing the Beta DVR PMS software. Iām running the PMS on an intel-based Synology NAS. Not sure what are the linux/nas fix equivalents of the windows-based ones mentioned earlier in this thread.
Incidentally, I do have a PIN set up because I have kids accounts and want to limit access to the adult accounts. Disabling the PIN would not be acceptable.
Thanks for any help.
@kieranc said:
Iām having this same issue ever since installing the Beta DVR PMS software. Iām running the PMS on an intel-based Synology NAS. Not sure what are the linux/nas fix equivalents of the windows-based ones mentioned earlier in this thread.
Incidentally, I do have a PIN set up because I have kids accounts and want to limit access to the adult accounts. Disabling the PIN would not be acceptable.
Thanks for any help.
Would need diagnostic logs to troubleshoot - from the plex web client app and from the Plex Media Server
Typical causes for such issues is that the web client app is signed in to a different plex.tv user account from the one that owns the plex media server (i.e. the Plex Media Server is signed into)
So check that the web client that you are using on the local network is signed in to the same account that you signed the server to.
Another reason for issues like this is if you have DNS Rebinding protection on your router and as such secure connections using the local IP plex.direct url are bouncing with DNS errors. You could try to amend the plex web settings to always allow fallback to insecure connections to see if that gets to the server. Of course if you had secure connections set to Required as opposed to the default of Preferred then it would not get through
You can test the plex.direct urls using nslookup and test also with google dns to establish if there is DNS Rebinding. The urls can be obtained through https://plex.tv/pms/resources.xml?includeHttps=1&X-Plex-Token=xxxxxxxxxxxxxxxx and the token you can find in Preferences.xml
The logs I was referring to should be for a test carried out after restarting the server.
The Plex Media Server.log and web client log
The web client log would be through settings / web / show advanced / debug / verbose logging / save changes
Then reproducing the problem, taking a full screenshot and then viewing the log via
settings / web / show advanced / debug / view logs / select all text and copy to text file and save
Attach all logs and screenshots
See https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
Thanks Iāll try to perform these tests tonight and submit logs after.
FYI, updating to the DVR beta2 of PMS fixed this issue.
Update, this issue has reoccurred for me. Iāve not changed anything since my last post, but now I canāt get to the server settings again, from the web app.
Any suggestions?
EDIT, 3 Oct 2016: and now server settings are available again, with no changes or troubleshooting or anything on my side. Weird.
I am suddenly also having this issue.
@ibigfire said:
I am suddenly also having this issue
Could you restart the server, wait a few minutes and retry to access server settings and when you see the problem, get a screenshot (full - showing url and time) and zip all the server logs and attach
See https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
Had the same issue after upgrading to plex server version 1.3.4 on my synology nas , encountered that folders had not be updated and no access to server tools. I removed this version and reinstalled previous version1.3.3. Everything working like a charm
Hey chaps and ladies,
Win 10.
Before you go and do anything drastic, just stop the Plex server, simply right-clicking the icon in the tray and selecting āExit.ā
Then restart; that did the trick for me, so it might for you.
Boom Shankar!
I have tried on three separate occasions to get Plex working, but have not been able to. Have tried uninstalling, deleting all Plex directories, reinstalling. I have no files in the Plug Ins folder. Tried claiming a server, not claiming a server. Iāve run as admin. I literally cannot get it to work. Log attached for anyone that can help. There are some critical errors. Can anyone give me an idea of what to do?
@petee326@gmail.com said:
I have tried on three separate occasions to get Plex working, but have not been able to. Have tried uninstalling, deleting all Plex directories, reinstalling. I have no files in the Plug Ins folder. Tried claiming a server, not claiming a server. Iāve run as admin. I literally cannot get it to work. Log attached for anyone that can help. There are some critical errors. Can anyone give me an idea of what to do?
There should be a Plex Media Server.log to go with the log file that you attached.
which security software do you use ? firewall ? anti virus ? internet security?
You can try adding a port rule in the firewall:
Inbound Port Rule
Protocol: TCP
Local Port 32400
Remote Port Any
Remote IP Any
Programs: Any
Scope: All Profile
Action: Allow
Also if you are using firewall other than windows firewall, try to add exception for the exe Programs in C:\Program Files (x86)\Plex\Plex Media Server
Strange, Iām not finding that log. I use Kaspersky. I will add the port rule tomorrow and let you know how that goes.
@petee326@gmail.com said:
Strange, Iām not finding that log. I use Kaspersky. I will add the port rule tomorrow and let you know how that goes.
Kaspersky Internet Security has been the cause of such issues in the past and may need some configuring. You can search the forums for it
You say the Plex Media Server.log was not present? So what did you have in the Logs folder ?
The log you attached would have been in a sub-folder Logs\PMS Plugin Logs ie lower level
I had both this issue with the āserver is unavailableā, and also not being able to add library āyour changes cannot be savedā (on another discussion).
Solution for me, allow access to python through your firewall or application control.
May not help everyone, but its another solution for you guys to try. 
@papawivo said:
I had both this issue with the āserver is unavailableā, and also not being able to add library āyour changes cannot be savedā (on another discussion).Solution for me, allow access to python through your firewall or application control.
May not help everyone, but its another solution for you guys to try.
What platform / OS?
@sa2000 said:
@papawivo said:
I had both this issue with the āserver is unavailableā, and also not being able to add library āyour changes cannot be savedā (on another discussion).Solution for me, allow access to python through your firewall or application control.
May not help everyone, but its another solution for you guys to try.
What platform / OS?
If it is windows the firewall rules are automatically updated when installing Plex Media Server to add the python related executable PlexScriptHost.exe as well as other exe files
Did you need to add manually because you are using other than Windows Firewall?