Not available outside your network / Indirect playback

Plex Media Server Remote Access
,
1

Server Version#:1.29.2.6364
[Plex Media Server Logs_2022-11-06_19-41-09.zip|attachment]
Player Version#:1.56.2.3345-2a4c0924
(upload://xYtegN2zZzgi4snKjv520eAY1q7.zip) (932.3 KB)

A few days ago, users began to send me complaints of poor video quality. I checked the dashboard while they were streaming and it said something about Indirect Playback. In addition, I can no longer get a stable Remote Connection on the Public Side under Settings → Remote Access for my server. It was working flawlessly until only a few days ago. The VM that is running the Server runs Ubuntu and has a static IP assigned in my router, along with port 32400 being opened. What can I do?

Remote Access Window
Remote Access Window913×548 42.8 KB

2

Test and make sure the port is actually open

3

Thanks for the fast response!

Am I checking the Public Port then? That IP Address and that Port Number?

4

That tool should automatically open with your public ip entered in the box, then just put in 32400 for the port

The only way the it would open with something other than your public ip is if you’re running a vpn.

5

It says it’s closed, but how is that possible when it’s opened on my Router?

6

Disable any firewalls and try the test again.

If you do use a VPN with a split tunnel feature disable that too

7

Disabled it and tested again. Still closed. Also, the IP in my router is different than the one on the website I’m testing. The one on my router forward is a 192.168, whereas the one on the website is a 50.93 address.

8

The port forwarding in your router should show the internal IP address of the machine you’re running the server on. (192.168.whatever), but I see in your Plex screen shot the private IP is 172.18.0.15

The internal and external port forwarding should be 32400. That routes your traffic to the external IP address which you won’t see in that part of the router settings.

9

this is because his server is a docker container. the 172 is the local docker network address however his local net is 192.

10

I see. I suspect then if you, manually input 172.18.0.15 into the port checking tool you’ll see that 324000 is open?

11

Nope, if I manually enter that into the port checker tool, it’s also closed.

12

Thanks for pointing that out, I’ve changed the post tags to reflect this.

13

If I may suggest?

If you want to run PMS in the container but still use the Host’s IP address,
set network=host in the container spec.

This allows it to run in the container but use the host’s IP address and removing the double-nat caused by the docker 172.x.x.x network.

14

Absolutely suggest! I’ll take whatever help you can send my way. Just need a bit of help as I had assistance setting almost all of this up so I’m a little unsure of what goes where. What do I need to change in here to get it to run the way you’ve explained? The more explanation you can give the better for me please.

Untitled
Untitled857×822 39 KB

15

I use docker run. I’m not the most versed with docker.

sudo docker run \
-d \
--name plex \
--network=host \
-e TZ="EST" \
-e LANG="en_US.UTF-8" \
-e PLEX_UID=1000 \
-e PLEX_GID=1000 \
-e PUID=1000 \
-e PGID=1000 \
-h dockerplex \
-v /sata/dockerplex:/config \
-v /sata/dockerplex/tmp:/tmp \
-v /sata/dockerplex/transcode:/transcode \
-v /vie:/data \
--device=/dev/dri:/dev/dri \
plexinc/pms-docker:plexpass

When you specify network=host, you won’t need to map ports because they will use the host’s ports naturally.

Pretty sure you remove all the ports and ports: clause
Add

network: host

in their place.

Ref: How to use host network for docker compose? - Stack Overflow

16

So I made a copy of the original YAML file just in case, changed over the bit you specified ( just commented out the ports), and now it doesn’t seem to want to up anymore.

Untitled

17

Copied from the linked stackflow - should be network_mode not network.

The equivalent configuration for docker-compose v3 is using the network_mode key: Compose file version 3 reference | Docker Documentation

You should set network_mode to "host" in your docker-compose.yml.

18

This made progress, the container tried to at least start up when I ran the docker compose up -d command. But now it’s caused a new error:

image
image1599×103 11.4 KB

Here is the whole compose.yaml script I have running now.

Untitled 2
Untitled 2849×847 40.4 KB

What do I do / should I do from here?

19

From quick reading, it seems because you can’t have both network_mode and networks items in your yaml

20

After making the proposed changes, I was able to up the docker container, but it continues to throw the same error message of “Not available outside your network”.