Server Unavailable after Docker Stop?

Plex Media Server NAS & Devices
1

Hi Folks,

I’ve recently made the switch from running PMS on ubuntu 16.x and successfully stood up PMS on a VM (CentOS 7) running Docker 17.12.

After my first night of having sluggish performance I realized I gave my CentOS VM only one vCPU, so summarily shut it down, added vCPUs and fired it back up. Ran a docker start plex and thought all was happy. Logged into my server http://server-ip:32400/web and found that my PMS was unavailable.

After multiple docker stop/start plex with no avail, I blew away my container, got a new claim-id and am now looking at setting up all my libraries again (and I fear downloading all the Metadata, posters, etc).

Question for folks who have a stable running PMS on docker:
1. How robust is the the PMS server with a docker start/stop? I would assume that you shouldn’t expect to have to blow away the container and lose the “server”.
2. How would I save myself the download and try to “transfer” the local library with all that juicy metadata that i already downloaded?
3. Given the Docker Run below, is there anything you can spot that i’m doing wrong?

Much appreciated!
Mark

sudo docker run \
-d \
--name plex \
-p 32400:32400/tcp \
-p 3005:3005/tcp \
-p 8324:8324/tcp \
-p 32469:32469/tcp \
-p 1900:1900/udp \
-p 32410:32410/udp \
-p 32412:32412/udp \
-p 32413:32413/udp \
-p 32414:32414/udp \
-e TZ="America/Los_Angeles" \
-e PLEX_UID=1000 -e PLEX_GID=1000 \
-e PLEX_CLAIM="..." \
-e ADVERTISE_IP="http://192.168.168.239:32400/" \
-h plexserver \
-v /plexdata:/config \
-v /media/vol4/Vol1/Anime:/Anime \
-v /media/vol4/Vol1/Anime\ -\ Movies:/anime-movies \
-v /media/vol4/Vol1/Documentary\ -\ Movies:/documentary-movies \
-v /media/vol4/Vol1/Documentaries:/documentary-shows \
-v /media/vol4/Vol1/Educational:/educational \
-v /media/vol4/Vol1/Kids\ -\ Movies:/kids-movies \
-v /media/vol4/Vol1/Misc:/misc \
-v /media/vol1/Movies:/movies1 \
-v /media/vol4/Vol1/Movies\ 2:/movies2 \
-v /media/multimedia/itunes/Music:/music1 \
-v /media/vol1/Music:/music2 \
-v /media/vol1/Series:/tv1 \
-v /media/vol4/Vol1/TV\ Series2:/tv2 \
plexinc/pms-docker:plexpass
2

I am having the same issue. Every time I need to restart the Plex docker container, I am unable to connect to the server without claiming a new token and setting everything up again. To be clearer about what is happening:

  • This happens after I reboot the server running Docker/Plex. When the server comes up, I do a docker plex start to restart the container.
  • I am fairly sure the container is coming up properly, as I am able to navigate to http://192.168.1.91:32400/web just fine. When I do this, I am presented with a normal Plex login screen. Logging in also seems to succeed, but then it tells me that “The server ‘Home’ is unavailable”.

My original docker run command:

docker run -d \
--name plex \
-p 32400:32400/tcp \
-p 3005:3005/tcp \
-p 8324:8324/tcp \
-p 32469:32469/tcp \
-p 1900:1900/udp \
-p 32410:32410/udp \
-p 32412:32412/udp \
-p 32413:32413/udp \
-p 32414:32414/udp \
-e TZ="America/New_York" \
-e PLEX_CLAIM="<mytoken>" \
-e ADVERTISE_IP="http://192.168.1.91:32400/" \
-e ALLOWED_NETWORKS="192.168.1.0/24" \
-e PLEX_UID=1100 \
-e PLEX_GID=1100 \
-h plexmediaserver \
-v /var/plex/db:/config \
-v /var/plex/temp:/transcode \
-v /mnt/Media:/data \
plexinc/pms-docker:plexpass

Does anyone have any clues why this is happening?