Just started getting this error recently after the latest update.
Any ideas on a fix?
1 Like
May I ask how long it’s been working before this happened?
What previous PMS version were you on?
What happens when you click on Settings - Troubleshooting?
Can you Download Logs?
I don’t remember the last time I tried to access server settings, but it was fairly recently (within the last month) and I usually keep the server updated to the latest version.
When I click settings > troubleshooting, the same thing happens: “Server Settings Unavailable” after a 23 second spinner.
While I cannot access the logs through the plex ui, I am able to find these manually. Which logs are relevant? There are 91 of them in the Logs directory…
You can exit out of the PMS server so it is stopped.
Then start it again, and give it 6 minutes to initialize.
Exit out of it again. Then zip up these two:
- Plex Media Server.log
- com.plexapp.system.log
The restart makes very clean logs. Thanks.
Here attached.
Plex Media Server.log (105.8 KB) com.plexapp.system.log (13.1 KB)
Any changes to your network recently? Router? Modem? NAS? PC changes?
Perhaps you could try uninstalling and reinstalling again. BTW I’m running the 1.18 version on a WD NAS without the issue you posted.
Definitely his network is getting creative 
I took a look at the logs. It’s picking up IPv6 which is the first suspect.
Let’s have you disable IPv6 in PMS Settings - Show Advanced - Network and Save.
Restart PMS and give it 6min to stabilize. Gather logs again and post them please.
Oct 16, 2019 08:39:01.347 [12480] DEBUG - NetworkInterface: ignoring adapter 'Wi-Fi' (fe80::1150:516a:d1dc:81c9%8,169.254.129.201) because it has no gateway
Oct 16, 2019 08:39:01.347 [12480] DEBUG - NetworkInterface: ignoring adapter 'Local Area Connection* 2' (fe80::a0ca:95fc:2e6e:3018%17,169.254.48.24) because it has no gateway
Oct 16, 2019 08:39:01.347 [12480] DEBUG - NetworkInterface: ignoring adapter 'Local Area Connection* 13' (fe80::54cc:8103:508a:5931%10,169.254.89.49) because it has no gateway
Oct 16, 2019 08:39:01.348 [12480] DEBUG - NetworkInterface: ignoring adapter 'Ethernet 2' (fe80::c0f5:5b29:933c:390c%4,169.254.57.12) because it has no gateway
Oct 16, 2019 08:39:01.348 [12480] DEBUG - NetworkInterface: ignoring adapter 'Loopback Pseudo-Interface 1' (::1,127.0.0.1) because it has no gateway
Oct 16, 2019 08:39:01.349 [12480] DEBUG - Detected primary interface: 192.168.0.26
Oct 16, 2019 08:39:01.349 [12480] DEBUG - Network interfaces:
Oct 16, 2019 08:39:01.349 [12480] DEBUG - * 14 Ethernet {A8B848C8-BD44-41EC-B1A8-71F1DAEC6672} (2606:6000:cf02:3100:bcf1:f959:8d95:93d6) (loopback: 0)
Oct 16, 2019 08:39:01.349 [12480] DEBUG - * 14 Ethernet {A8B848C8-BD44-41EC-B1A8-71F1DAEC6672} (fe80::bcf1:f959:8d95:93d6%14) (loopback: 0)
Oct 16, 2019 08:39:01.350 [12480] DEBUG - * 14 Ethernet {A8B848C8-BD44-41EC-B1A8-71F1DAEC6672} (192.168.0.26) (loopback: 0)
Could this be related to What Gives With 1.18.0.1913? ?
I was having this same issue and downgraded and now things are working fine.
That’s a good question. I’d ask those guys to double check that IPv6 isn’t enabled.
@nibbles, how can you tell from those logs Plex is using IPv6 vs. IPv4?
Thanks.
After restarting PMS, if you look in Plex Media Server.log, right near the top you will find this line if IPv6 is still enabled in your Plex Settings:
Oct 08, 2019 21:43:29.705 [8888] DEBUG - HttpServer: Listening on IPv6 as well as IPv4.
Disable IPv6 in Plex might not go far enough. You might have to disable it in Windows Control Panel. I can’t test it here. Because networks still run fine on IPv4, disabling IPv6 in Windows is safe.
Thanks. That the line I was looking for but couldn’t find in the original code you posted.
Anyway (Windows 10) IPv6 would be setup via Networking and Sharing Center, click the Change adapter settings link, right click on your network adapter, Properties, Networking tab, and look for Internet Protocol Version 6 (TCP/IPv6) and tick to enable, untick to disable.
By default mine was enabled, but I’m not using any IPv6 sites, nor is IPv6 enabled in my router. That said, If IPv6 is enabled in router and Network settings, and your NAS, than it would stand to be that it should be enabled in Plex. If none of the previous is done, than it should not be enabled in Plex.
In short, if you don’t use IPv6 for anything than you don’t need it for Plex. If you are using it, than it should be enabled in Plex.
Since Plex defaults to using IPv4 (you have to tell Plex to use IPv6) as long as all your other network setting are also defaulted (set) to IPv4 (and they should since this is the basic protocol) than you don’t (also) need to disable IPv6 in network settings. But if you are using IPv6, it needs to be set every where - Network setting, Router, NAS, Plex.
This is posted for those not in the know 
Peace:)
I can’t disable ipv6 as I am unable to reach that page in advanced settings. I am going to try and disable it in Windows first and see what happens…
Perfect. Reboot the computer after you adjust it. Login to your desktop and give PMS 6min or so to initialize. Then try to access
Do those work? If not try the IP address you assigned to the computer:
Log into the plex.tv website, then look at the authorized servers attached to your account here:
Screenshot anything useful. You may have more than one server listed, or you may need to claim yours, or various other things.
There were gaps in your previous server logs due to crashes that can happen from IPv6 among other things. It will be good to see how it boots up now.
Thanks
Same result for all methods of server access above: “Server Settings are Unavailable”. Disabling ipv6 in Windows network connections made no difference either.
Is there an alternate method of accessing the PMS settings? An XML file or some other config file somewhere? Since I can’t access the settings page with which to disable ipv6, that leaves it enabled, while in Windows, it is disabled.
If IPv6 is off in Windows, the setting for it in Plex won’t matter.
Screenshot your devices https://app.plex.tv/desktop#!/settings/devices/pms
Screenshot what you see when you use https://127.0.0.1:32400/web
Upload your server logs please.
I should have answered your question yes, there is.
https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
It’s good to see you only have one server listed. I also looked at your logs. You’re getting a lot of critical errors due to problems with networking. The services bundle repeatedly crashes, and basic Plex systems then malfunction when they can’t talk to it. It looks like IPv6 is still enabled. We can do a couple of things.
- Stop PMS.
- Use the Advanced Hidden settings article to disable IPv6.
- Start PMS again.
- While it’s initializing, run this in a terminal ipconfig /all
- Paste in the output here.
- Go into the PMS logs folder and delete anything older than two days ago.
- If it has been 6 minutes, then stop PMS again and zip up the whole PMS log folder.
- Attach the zip file please
- Tell us if you have any VPN or ESET or Antivirus or Security software of some sort.
I’m leaning towards IPv6 or some software getting in the way of basic networking. It’s possible, though less so, that you just need to reinstall in a safe way to preserve your metadata and media.
Okay good luck!
Output of ipconfig:
ipconfig.txt (3.4 KB)
Logs:
Logs.zip (2.8 MB)
I do use a VPN (Private Internet Access), but i’ve added Plex as an exception in that it bypasses the vpn:
Ok, interesting. I think i’ve narrowed the issue to my VPN client. The addition of the exclusion of PMS seems to cause an issue. If I disable the VPN altogether, server settings are accessible. As soon as I enable the VPN client, the server settings become inaccessible.
I have removed the exclusion of Plex in the VPN settings and now Plex settings are accessible (both via localhost and pc ip address) even with the VPN connected.
The problem is with the VPN’s “App Exclusions” feature. I know they recently added this. It appears it may be a bug with that feature.
Many thanks for all the help nibbles and others.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
