Please help—plex container no basic setup wizard—yes I used localhost:32400 via ssh tunnel

Plex Media Server Desktops & Laptops
1

Server Version#: latest official docker container
Player Version#: latest official docker container

Hello all,

I am attempting to setup headless PMS via official Docker container on remote headless server Ubuntu 18.04.

I have successfully downloaded the official plex docker image and executed a docker run with proper config (network=host, PID/GID with primary sudo user, valid claim token, mapped to existing folders created by primary sudo user). I have allowed port 32400 on UFW. I have tunneled in with port forwarding and opened localhost:32400 on my local machine.

Localhost:32400 opens into plex web app in my account, I only have one account, it looks for server. It does not open to the basic setup wizard, so I cannot “turn on” my plex container as a server, I can only use it as a web app.

I’m not sure what log files to look for but I am happy to post any that are needed to diagnose the problem.

Any advice?

Edit, here is my docker run:

sudo docker run
-d
–name plex
–network=host
-e PLEX_UID=1000
-e PLEX_GID=1000
-e TZ=“America/New_York”
-e PLEX_CLAIM=“123abcxyz”
-h plexdocker
-v /home/123/docker/config/plex:/config
-v /home/123/plex/transcode:/transcode
-v /home/123/plex/media:/data
plexinc/pms-docker

Edit2:
the plex docker PMS is displayed under my “Authorized Devices” page

Edit3:
I successfully ran the github “ClaimIt” script designed to repair this issue, but nothing changed, still just looking for server when i connect via ssh tunnel as 127.0.0.1:32400 or localhost:32400.

Edit4: not sure if helpful, but the container is setup in host mode. The host machine has a public ip address. The Docker app has a different internal ip address. I assume the plex container is running on an ip address on the same gateway or whatever that the Docker app is running on, but because i’m setup in host mode all of this should be port forwarded, so i’m at a loss.

Edit 5:
I have tested with UFW disabled, but to cover my bases, these are my UFW settings:
o sudo ufw default deny incoming
o sudo ufw default allow outgoing
o sudo ufw allow 22 (ssh)
o Sudo ufw allow 80 (http)
o Sudo ufw allow 443 (https)
o Sudo ufw allow 21 (ftp)
o Sudo ufw allow 32400 (plex)

Edit 6:
I got fed up, deleted the Preferences.xml, and that did the trick. 127.0.0.1:32400/web finally activated server setup and then granted me server access to select library files etc.

2

I been having same issue for a week.

1 Like
5

bump for help!

6

A search of the Support Pages returns

See the bottom of the page for additional information.

7

@Chuck
Yes I have followed this to a Tee. Do you believe I have done something incorrect?

8

I have no way of knowing. I don’t use docker because of hurdles like this.

There are many who swear by the technology. I, unfortunately, swear at it.
I use it only for slave tasks which aren’t available as native apps for the host (as docker was originally intended). A full server in a container, with PMS security requirements, is, imho, pushing it past good common sense. On Linux, there is no reason to run Docker. The app can be moved to another host as easily as a tarball. But, BEFORE getting flamed, this is my humble opinion.

9

This topic was automatically closed after 90 days. New replies are no longer allowed.