Server ip, Private ip and Public ip are different. No remote access

Plex Media Server Remote Access
1

Hello,

I think i have a weird problem…

Before i had Plexms in a windows 10 and running perfect with remote access.

Now…

Im running plexms in a docker container with the default ports in a Debian 10 server.

  • My server has a static ip.
  • I can use my server inside my Network but i cannot use remote access.
  • My server ip is 192.168.9.xxx,
  • my router says that My wan ip is 192.168.1.xxx,
  • Plexms says that My private ip is 172.xx.x.x and My public ip is 42.xxx.xxx.xxx.

I can see my public ip from outside but canyouseeme.org cannot see my port 32400 open. So i tried to do port forwarding in my router… and nothing… i even set my server as DMZ and nothing.

If it worked in windows i guess it can work in debian.

Can i fix this with a DNS name service like no-ip.com or something like this?

My log says things like:

Nov 20, 2020 17:02:50.207 [0x7fc680ff9700] Debug — NAT: UPnP, found device http://172.18.0.3:32469/DeviceDescription.xml with private address <172.18.0.3>
Nov 20, 2020 17:02:50.207 [0x7fc680ff9700] Debug — NAT: UPnP, not an IGD: http://172.18.0.3:32469/DeviceDescription.xml.
Nov 20, 2020 17:02:50.207 [0x7fc680ff9700] Debug — NAT: UPnP, getPublicIP didn’t find usable IGD.

Warning — NAT: PMP, got an error: Not Supported by gateway.

Nov 20, 2020 17:02:53.461 [0x7fc680ff9700] Error — Error issuing curl_easy_perform(handle): 28
Nov 20, 2020 17:02:53.461 [0x7fc680ff9700] Debug — HTTP simulating 408 after curl timeout
Nov 20, 2020 17:02:53.462 [0x7fc680ff9700] Debug — MyPlex: mapping state set to ‘Mapped - Not Published’.
Nov 20, 2020 17:02:53.462 [0x7fc680ff9700] Debug — MyPlex: sendMapping resetting state - previous mapping state: ‘Mapped - Not Published’.
Nov 20, 2020 17:02:53.462 [0x7fc680ff9700] Debug — MyPlex: mapping state set to ‘Unknown’.

Warning — MyPlex: Invalid connection URL ‘“http://192.168.9.xxx:32400/”’.

Thank you to whoever read this, I don’t know what else to do :frowning:

Server Version#: 1.20.5.3600
Linux: Debian 10 headless server

2

Ah, good old IPv4 with NAT, after NAT, after NAT…

It appears like you’re triple NATting:

  • the first router (yours? somewhere on the ISP network?) has the actual public IP address 42.xxx.xxx.xxx, and NATs it to 192.168.1.*
  • the second router (the one at home) gets 192.168.1.x on the WAN end, and NATs it to 192.168.9.*
  • your server receives 192.168.9.xxx, and Docker, running on that server, NATs it to 172.17.xxx.* for its containers
  • PMS gets 172.17.xxx.xxx from Docker

Ports have to be carefully mapped at all these hops: the two routers and Docker. And then you cross your fingers and hope your connection survives all this manhandling.

3

Hahaha… ok…

The first router is not mine… It can be in the ISP network or maybe in my building… but i don’t have access to it or I don’t know how to access it.

I think the docker is well mapped i took the config from plex. i can prot forward in my router(second router?) but i dont have access to the first one. :frowning:

Do you think the possibel solution I stated could work?:
Can i fix this with a DNS name service like no-ip.com or something like this?

If not… I guess I’m condemned to use Windows 10 for life. :frowning:

4

A DNS service won’t help, it’s not DNS that’s the problem here.

I would first try if it works with a normal Linux install (ie, not inside Docker), that already removes one layer of NAT and allows PMS to ‘natively’ talk to router 2 using NAT-PMP or UPnP-IGD to map a port. Maybe (?) router 2 will then forward that request upstream to router 1.

I’m actually surprised that it worked on Windows 10, to be honest :slight_smile:

5

In Windows 10 worked without docker… just the regular plex installation without touching anything… all automatic.

I’m going to follow your advice now and i will report the results. Thank you so much

6

Did it work previously on W10 with direct access or through Plex Relay (indirect connection, i.e. tunneled via the Plex servers at max 1-2 Mbit/s)?

7

Access remote is working!! thank you!!

I removed the plex container from docker and install plex outside. I also deleted the port forwarding in my router and let UPnP handle everything… and it just worked.

Now I have a problem with plex which is not able to see the folders in the docker volumes where my movies are. But I guess this is another thread.

8

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