I have used the instruction to install PMS in docker. As soon as I log into the web interface it connects to the Plex Media Server that I already have. I do not get to see the wizard to create a new PMS. When I use other PMS docker images it works as expected. Also adding, changing, removing PLEX_CLAIM doesn’t seem to have any impact.
Please advice. Thanks!
I don’t have PMS in/on Docker but I do have 3 versions of plexpy for 3 different PMS.
It’s all about the ports.
This is where plexpy is for one of my servers http://192.168.100.85:32854/home# when the container port is the default 8181.
2nd server is http://192.168.100.85:32855/home# and same container port
@spikemixture, It does not seem port related since I can access the web interface. It just doesn’t show the setup wizard.
I am seeing the same thing I think…
Installed the docker image - access the webUI, log in with my plex account and I can see and play around with the existing plex server on the network - but not configure this one as a replacement.
I shall look again when I am not due in bed, but this is mildly confusing, and feels like a generic ‘plex being cleverer than me’ issue rather than docker specific.
My first task will be to trawl the rest of the forum (non docker) to see how people migrate plex servers (it’s a while since I migrated mine, and I can’t remember how I did it)
I am experiencing the same issue. I have re-created the container multiple times with no luck. The only server I see is the other one on the network and I cannot find a way to “add” a new server.
I wonder if it is to do with the fact that we are accessing a docker container and are therefore not on the ‘local’ network.
I recall seeing something like that in the compose file…
Aha - yes. I was running the container through docker-compose, and not in net-host mode.
Putting it in host mode has given me the setup.
I’m going to shut it down, and try again in bridged mode to see if it is still there.
OK - back up in bridged mode, and it seems to be working (from the web interface, I’m not at home, so I can’t try playing anything yet*)
My suggestion is therefore to run the plex container in host mode for setup.
Back in ‘normal’ bridged docker networking - I had to manually set the IP on my client, but it plays video perfectly.
I should add the env variable as described in the container readme:
ADVERTISE_IP This variable defines the additional IPs on which the server may be be found. For example: http://10.1.1.23:32400. This adds to the list where the server advertises that it can be found. This is only needed in Bridge Networking.
Indeed that worked as described…
That was the solution. Thanks XAPBob.
XAPBob, Can you offer some help on this issue? I’m experiencing this issue as well, but I cant get it to work.
I have the advertise ip varibable set. I’m in bridge networking, but everytime i go to the IP, it just logs me into the current plex machine on the network (sees it as a nearby server).
Can you help me determine what’s going wrong?
