Yes, go use SSH and get into the machine. Find out what’s happening with the networking. Every time the adapters change state, the routing table is dropped and rebuilt. Either dropping will cause PMS to go silent until again stable.
You’re accessing the server from a different subnet
Nov 15, 2019 16:29:27.666 [0x7f9e2589db80] DEBUG - Network interfaces:
Nov 15, 2019 16:29:27.666 [0x7f9e2589db80] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
Nov 15, 2019 16:29:27.666 [0x7f9e2589db80] DEBUG - * 2 enp6s0 (192.168.100.230) (loopback: 0)
Nov 15, 2019 16:29:27.666 [0x7f9e2589db80] DEBUG - * 1 lo (::1) (loopback: 1)
Nov 15, 2019 16:29:27.666 [0x7f9e2589db80] DEBUG - * 2 enp6s0 (fe80::45d:70eb:fcf7:b5f0%enp6s0) (loopback: 0)
Nov 15, 2019 16:29:27.666 [0x7f9e2589db80] DEBUG - Creating NetworkServices singleton.
Nov 15, 2019 16:29:37.969 [0x7f9df0ff9700] DEBUG - Request: [192.168.150.1:63721 (WAN)] GET /web/favicon.ico (16 live) GZIP
SSH- tunnel into it and then verify it is still signed into your Plex account.
I VNC’d in to that box and got the same thing whether going to IP or just localhost. It asked me to login again but still everything Unreachable.
I want you to use the loopback adapter. 127.0.0.1:32400/web
The reason for this is because the SSH tunnel obscures your address on the other subnet.
PMS will not allow itself to be claimed from a different subnet.
As long as there are no X-Forward or X-Refer addresses flying around, PMS will be ok but i’ve never had success with VNC.
Next step
- Stop PMS
- Drill into var/lib and rename “Preferences.xml” to “Preferences.xml.old” (saves it)
- Start PMS
- Sign out of Plex/web (brower)
- open http://127.0.0.1:32400/web
- it will think a new server - this is expected
- Sign in (claims it)
- See the setup wizard
- DO NOT create new library sections. We’re only resetting the identity
- Continue through to set other preferences as you had them
- When you arrive at the dashboard again, it should be back as yours on your account
1 Like
Same thing. Stopped it. Renamed the xml file. Started it. Hit it via 127.0.0.1 and it walked me through the setup wizard. Didn’t add libraries. Got to the home screen and it shows my libraries from before but everything is still Unreachable. Again…I appreciate it. This is driving me nuts.
give me a few? i will look up something
Take all the time you need. 
You’re the one doing me a favor.
1 Like
I think this docker error had done serious error to ubuntu. I decided to go with fresh install of my server, purge everything PMS related and started again.
I can add library but after that nothing happens.
I look forward to see if you guys find solution to this, hope all the best. Will try some new things tomorrow, keep you posted, it’s night time here.
EDIT:
Hey it seems to be going to work, this “fresh” install thing
ChuckPA helped me get this solved. We believe it’s due to my VPN and plex having issues with the networking due to that. We basically rolled back a version to a clean state and now everything is good and happy.
If I may add, it was the combination of:
- VPN
- Currently operating split across two subnets.
- PMS became decoupled from the account.
Everything was ok until PMS became decoupled (root cause unknown).
Once decoupled, rolling back the server to ‘unauthenticated mode’ allowed sufficient communication to complete first-run setup.
With first-run setup complete, singing back into the account and claiming restored the remainder of the linkages.
Great news, there was no VPN on my network. But of course in both cases this was a network issue that started when logs filled up the disk. Maybe if I done the ‘unauthenticated mode’ it would work. But fresh installed did also work for me 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
