I cannot connect to the PMS from the web client. I can still use plex fine from the Android app, and cast to Chromecast, and from my main user on the Rasplex.
However when point the web browser at http://[plex LAN ip]:32400/web/index.html, I am prompted to select user. If I select my main user I am prompted to enter a PIN, and then I get to the main Plex screen.
My server name has a red triangle next to it and says “unavailable”
How I can reconnect to my server? Thanks!
It sounds like the secure (https) part of the communications isn’t connecting up from within the docker container as asserted by your ‘http’ and not ‘https’ reference.
If there is double address translation going on (double NAT) there will also be connection issues. How is the docker container networking configured? Is it a ‘bridged’ or ‘nat’ network adapter within?
Hi, thanks for replying. It is configured as “Host” not “Bridge”
If I try https://[plex lan ip]:32400/web/index.html, then after chrome complains about the self signed certificate, I get the same behaviour. Prompt for user id, and pin, but then no server found.
Plex has made steps to tighten security (all at user request) and it’s possible not all the ‘kinks’ are out (educating us ninjas).
If you will bare with me a bit, I will ask for help so I know better and can help you and others with this issue.
Confirm for me you cannot get into your machine if you are logged into the machine which is the server and use ‘http://127.0.0.1:32400/web’ ??
I’m very confused about how you get ‘console’ level in docker. I’ve had nothing but trouble using it.
To get to your server the hard way and ‘break in’…
Stop Plex.
Log into your machine as the admin (root) (whatever that may be… reach in through the file system if you must)
find and rename ‘Preferences.xml’ to ‘Preferences-prev.xml’ under Library/Application Support/Plex Media Server (this will save the original server ID for later)
Start Plex.
It will think it’s new… answer the initial questions and re-add your libraries, just as they were. It will find everything waiting for it, completely untouched.
Continue connecting to your account… be really careful of the ‘always secure’ and ‘never fallback’ questions … Don’t lock yourself out.
Displays “unclaimed server”. I click to claim it - ok
Agree to terms of service - ok
Click “Next” on “Great we found a server”
Click “Next” on “Server Setup” where it shows my libraries - ok
Click “Done” on the next screen - ok
All looks good, I can access my server, see my libraries and change settings.
Close browser window using ctrl-W - ok
Open browser window and navigate to http://192.168.27.3:32400/web/index.html - “The server “Tower” is unavailable Plex will automatically try to reconnect to this server”
It seems that as soon as it associates the server with my account, I cannot get back into it after closing the window.
I can repeat those steps and get the same behaviour.
Everything is fine until ‘networking’ is involved, whether it be intra-host (in & out of docker) or inter-host (host-Plex.tv servers)
Try one more thing for me.
Repeat one last time — with alteration: while performing setup
a. Assign a different (test) name
b. Add only 1 ‘Library’ type (just to establish something)
c. Make sure everything is ‘unsecure’ or ‘disabled’ (turn off all security) (Settings -> Server -> Network)
after step 10, do not close browser keep that session live (session tokens)
Go over to Settings - Devices
Delete the OLD instance of the server
Open a different browser and see what shows up.
if you can’t see the new name / connect to it normally on your local lan, it’s within docker. The same happens with VirtualBox and ‘NAT vs Bridged’ network adapters. It’s an instance of double-nat. Your modem -> host (NAT level 1) -> docker NAT adapter (and that’s double NAT… which plex can’t do without lots of manual help)
Kindly examine how the docker networking is configured. My experiences with its networking have been ‘harsh’ at best and why i don’t use it. It’s a ‘lightweight virtualization’ for a reason. “Bridged adapter” should be the right answer if they support it.
With the ‘control session’ (working one) still open, you can resolve this network issue and complete your config again… as it should be.
You can fix this by adding customConnections=" https://192.168.27.3:32400" to your preferences.xml. Restart the container and give it a few minutes and you should see your server again after your IP is published.
When running in bridged mode, the docker container IP gets published to Plex instead of your server hosting docker. If you’d be able to get to the remote access tab, you would see something like this:
Private 172.17.0.2:32400 <- Public External.IP.Address <- Internet
When you would really want to see this:
Private 192.168.27.3:32400 <- Public External.IP.Address <- Internet
