Not accessible from outside - new ports not accessible

Plex Media Server Remote Access
1

Server Version#: 1.41.8.9834
Player Version#:

Hello dear community,

I recently started having problems accessing my Plex server from outside my network. I get the message “Indirect playback.” It worked perfectly for years, but since I switched from cable to DSL with the same ISP and got a new router, the problem has existed. I installed Plex as a Docker. The host has the IP: xxx.xxx.xxx.40

so the “private address” for Plex is: xxx.xxx.xxx.40:32400

I also set up port forwarding in my router (FritzBox 7530 AX): TCP 32400. Unfortunately, it didn’t work.

Then I defined port 34600 in Plex under “Settings” → “Remote Access” and also set the port forwarding in the router to 34600. Here, too, I get the message “Not available outside your network.”

I am now at a loss and hope for your help.

best regards!

2

Do you have your docker config for plex using host or bridge mode? Does the private IP start with 172.x.x.x?

3

Thanks for the quick reply!

Attached is my docker-compose file, which I installed via Portainer.
My internal IP starts with 192.xxx.

5

So you are forwarding port 34600 from your external network to 32400 internally to 192.x.x.40?

6

I tested both options and configured port forwarding for both options in my router (TCP).
I have now redefined 32400.

(Addendum: Public Port 9112 und 42500 is also not functioning.)

In the default setting, films can be played from outside, but with the note: “Indirect playback.” (very poor quality and partial interruptions)

The second screenshot shows the defined port forwarding on my router.

Brief information: My network is kept simple (Internet → router → NAS. This means that no other firewall is implemented).

Screenshot 2025-08-13 200913
Screenshot 2025-08-13 2009131029×581 72.6 KB

Screenshot 2025-08-13 200552
Screenshot 2025-08-13 2005521249×100 7.63 KB

7

Unfortunately, I haven’t made any progress yet. Can anyone help me?

8

Let’s maybe go back to something more basic…
Can you see/access the public port of your forward from outside your home network? You can check this using a service like canyouseeme.org.

9

Thank you very much for your reply!
No, I can’t see any ports here. Neither 32400 nor any other. I tried checking the ports listed on canyouseeme: 21, 22, 23, 25, 80, 110, 143, 3389, and 5631.
Everywhere I get the message: “Error: I couldn’t see. I couldn’t see your service at xx.xx.xxx.xx on port 32400 (xxxx).”

10

That means there‘s a problem between „the internet“ and your router (incl. potentially the configuration of the port forwarding rule).
Assuming the port forward setup is ok, your best shot will be to connect with your ISP to verify if the might be blocking any of that communication.

Another troubleshooting step could be to stop the container and setup a native installation (just for testing). If the connection to the native install works, there might also be an issue with your docker config.

11

OK, thank you!
I just spoke to my ISP (Vodafone) on the phone. The problem here was that I was using DS-Lite (IPv6 + shared IPv4 via CGNAT). I have now switched to dual stack (public IPv4 + IPv6). This change will only take effect on the next calendar day. I’ll restart the router tomorrow and see if it works now.