Public IP correct on PMS-Windows 10 but incorrect using linuxserver/plex:latest-Raspberry Pi when both using the same network

Plex Media Server Remote Access
1

Debian 10.4
Docker 5:19.03.9~3-0~debian-buster
PMS 1.19.3.2843

My first setup of PMS was on my Windows 10 laptop and all is working fine, including remote access (public IP matched that of the router).

However, due to the age of my laptop I decided to setup a new PMS (and Plex account) on a Raspberry Pi with OMV5 and Docker.
This has not gone without issues but all seems to be working well apart from remote access.

My problem is that Settings / Remote Access is signed in to Plex, but is not reachable from outside my network. It is displaying a different public IP to that on my router and Windows 10 server. Both servers are on the same network.

I am far from network knowledgeable but could the container be causing double NAT?

Any help would be most appreciated … :pray:

2

Are you sure Plex is displaying a public IP address?

3

It’s in the range 185.206.xxx.xxx

4

Weird if that IP range is completely different from your own. Is it? I have no idea how Plex is coming up with that. What happens if you log the server in with your other Plex user ID?

5

My public IP is definitely 31.51.xx.xxx and works on my Windows 10 setup. Not sure about signing in with my other account as I thought it referenced it’s own server?

6

I’m pretty sure you can have more than one server per account.

Any chance you have a VPN running on the machine that Plex shows the weird IP for?

1 Like
7

To be safe I tried it the other way around (not so worried about screwing up my Windows Server) and it’s looking for my Linux Server.
I definitely have no VPN running.
My only thought is that docker containers handle networks differently and it’s causing a double NAT. However, I’m not technical enough to debug this idea.

8

Dockers have their own internal networks but they are in the private IP spaces, never in the public spaces.

It would be helpful to see how the container was configured.

Could be some sort of glitch up on the Plex server side where they think you are someone else that has or had a server on that weird address.

I’d trash the container and rebuild it.

9

OMG what an old fool I am.

You just triggered a memory mentioning VPN, I was playing around with OpenVPN when I first setup the server and thought it was disabled. Apparently not !! All working now.

Many thanks for your replies, case closed as they say :pray:

10

LOL. VPN was the only thing I could think of that would explain it.

Enjoy OMV. I am on OMV 5, having upgraded over the last five years starting with OMV 2. I have fourteen docker containers running here, plex is one of them.

11

Early days for me, straight into OMV5. It’s a good hobby for me now I have retired, it keeps the old grey matter going (apart from forgetting about VPN lol). Any way thanks again for the nudge.

12

Retired here too, and Plex is part of my hobbies.

I wish drives and internet bandwidth were cheaper. My Plex media consumes 24TB and it grows by at least 1TB/month.

Enjoy!

13

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