Hey folks, there is a new Podcast category for forums https://forums.plex.tv/categories/podcasts
If you have not already, we suggest setting your Plex username to something else rather than email which is displayed on your posts in forum. You can change the username at https://app.plex.tv/desktop#!/account
Welcome to our forums! Please take a few moments to read through our Community Guidelines (also conveniently linked in the header at the top of each page). There, you'll find guidelines on conduct, tips on getting the help you may be searching for, and more!

Issue with new docker PMS

S3ltaS3lta Posts: 2Members, Plex Pass

Hello,
I've been running Plex for a few years. I previously was running it on a Windows VM on an ESXi host. That was all fine and dandy, but I'm container-izing everything else, so I thought I'd give it a whirl with Plex as well.

I can easily get the docker container running.
I **can ** access it with my publicIP:32400 as well as internalIP:32400 (I updated the appropriate network port forwarding to the new internal IP address). So network should be fine.

No matter which IP I use to access, if I am not logged on, I am taken to the login prompt and login is successful.

The issue I seem to be having is relating to Claiming the server maybe?
The WebUI does not show my server in the drop down in the upper left corner (it does show all of my friend's PMSes as expected, mine is entirely missing from the list).
I do not get a Claim banner.
When I click Settings, the Server option is missing (I only have Web, Users, Devices).

At this point I have not moved the previous install. I'm trying a pure, net-new install.

Things I've tried:

  • Stopping the container, deleting everything from the /config directory (including Preferences.xml), generating a new claim code, and restarting PMS.
  • Stopping the container, deleting everything from the /config directory, delete the container, purge the image, generate a new claim code, restart PMS.
  • Reverted my port forward rule to the old interal IP, fired up the Plex on the VM, and it works immediately.

more info if it matters:
docker version: 18.03.1-ce docker-compose version: 1.18.0, build 8dd22a9

docker-compose.yaml:

version: '3'
services:
plex:
container_name: plex
image: plexinc/pms-docker:latest
restart: unless-stopped
networks:
- media
ports:
- "3005:3005/tcp"
- "8324:8324/tcp"
- "32400:32400/tcp"
- "32469:32469/tcp"
- "32410-32414:32410-32414/udp"
environment:
- TZ=America/Los_Angeles
- PLEX_CLAIM=${PLEX_CLAIM_CODE}
volumes:
- /data/virtual/plex:/config
- /data/media/tv:/data/tv
- /data/media/movies:/data/movies/
- /data/media/4k/tv:/data/4k/tv
- /data/media/4k/movies:/data/4k/movies
- /data/media/music:/data/music/
- /data/virtual/plex/tmp:/transcode
networks:
media:
driver: bridge
ipam:
driver: default
config:
- subnet: 172.28.0.0/16

I've also attached the PMS log to this post.

Answers

  • S3ltaS3lta Posts: 2Members, Plex Pass

    I apparently can't upload the logs :-/

  • dohdoh Posts: 135Members, Plex Pass Plex Pass

    I'm getting exactly the same - driving me nuts!

  • uglymagoouglymagoo Posts: 1,081Members, Plex Pass, Plex Ninja, TunerTester Plex Ninja
    edited June 1

    Two possible solutions:

    (1) Delete the file /.firstRunComplete in the container, get a NEW PLEX_CLAIM code (any PLEX CLAIM code is only valid for 4 minutes!) and restart the container.

    The Plex claim process is only triggered the first time your container is run (check for file /.firstRunComplete). Take a look at the following script that's run.
    https://github.com/plexinc/pms-docker/blob/master/root/etc/cont-init.d/40-plex-first-run

    (2) Start the container temporarily in "host" network mode and use a ssh tunnel to access the web interface "locally". Please read "On a different Network":

    https://support.plex.tv/articles/200288666-opening-plex-web-app/#toc-2

    Official instructions for Plex Media Server on the Raspberry Pi 2 and 3 / Banana Pi / ODROID / many more : armhf and arm64 Debian Repository
    My PMS hardware: RPi 2, NVIDIA Shield TV, Intel Xeon

Sign In or Register to comment.