Moved server to docker - have network issues

Server Version#: latest
Player Version#: web/unknown

I moved my plex server into a docker container. It was previously in a VM, and I’ve migrated all of those into containers.

What I am experiencing is that I can access the plex server with the browser, and when I go to settings it tells me that my connection is indirect.

When I attempt to access plex using my LG tv or Firestick application I am told the server is unavailable.

I’m creating my container like so:

docker run \
--restart always \
-d \
--network plexnet \
--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="claim-u3lawRcSMNUr9WhPmTU4" \
-e ADVERTISE_IP="192.168.80.16:32400/" \
-e PLEX_UID=1004 \
-e PLEX_GID=1004 \
-h PlexContainer \
-v /containers/plex/plexmediaserver:/config \
-v /containers/plex/transcode:/transcode \
-v /containers/plex/data:/plex \
plexinc/pms-docker

(No, that’s not my actual claim)
I’m only using port 32400, and I’ve opened that port from the outside to 192.168.80.16, which is the host IP of the container.

Plex says it’s fully accessible, but my clients cannot connect (just browser)

Additionally, I’ve done this to try and get the web client to not show “indirect”

My home LAN is 192.168.80.0/24.

What could be causing these issues?

Did you figure this out? I’m having similar issue.

I think I have it working, but I don’t know that this is “the way”
I put a static route on my gateway pointing to the container network (172.19.0.0/24) using my container host as a gateway (192.168.80.16) - This resolved the “indirect issue”

Then I edited Preferences.xml and I put this: customConnections="192.168.80.16:32400" inline with the file based on this thread: Bridged mode trouble · Issue #36 · linuxserver/docker-plex · GitHub

Now both problems are “resolved” but I still feel weird about it. I thought that ADVERTISE_IP was supposed to take care of this.

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