Local traffic appears as remote when hosted on bridged docker container

Plex Media Server Remote Access
,
1

Server Version#: 1.40.1.8227
Player Version#: Plex Web Client

I am running a instance of Plex on a docker container within my Synology NAS box; because this is my second instance (the first one being hosted by Package Centre), I’ve had to put the container in bridge mode so I can map the default port from 32400 to 32403. The server is accessible via app.plex.tv and 192.168.1.100 which is my LAN IP. When I play any content in the dashboard it claims I am streaming remotely; I have remote connections and relays turned off.

I have put 192.168.1.0/24,172.17.0.0/16 into my Settings > Network > LAN Networks and checked the ‘Treat WAN IP As LAN Bandwidth’ option.

When I access plex via 192.168.1.100 and play content, the dashboard claims the connection is local but I can see through my router that the PMS is uploading the content, and my client is downloading traffic from the internet to stream it. Similarly, if I access app.plex.tv through my web browser or maybe use PlexAmp on my phone (while on the local network), in the dashboard it claims these are remote connections and shows my WAN IP address.

How can I resolve this?

2

Also experiencing this on my Debian host.

Relevant docker-compose.yaml entry:

  plex:
    container_name: plex
    hostname: plex
    image: plexinc/pms-docker:plexpass
    deploy:
      resources:
        reservations:
          devices:
            - capabilities: [gpu]
    ports:
      - 32400:32400/tcp
      - 32410:32410/udp
      - 32412:32412/udp
      - 32413:32413/udp
      - 32414:32414/udp
      - 32469:32469/tcp
    environment:
      ADVERTISE_IP: "https://192.168.2.100:32400/"
      PLEX_UID: "1003"
      PLEX_GID: "998"
      HOSTNAME: "Vergil (New, Active)"
      TZ: "America/New_York"
      NVIDIA_DRIVER_CAPABILITIES: "compute,video,utility"
      NVIDIA_VISIBLE_DEVICES: "all"
    volumes:
      - "/mnt/plex/vergil:/config"
      - "/dev/shm:/transcode"
      - "/etc/timezone:/etc/timezone:ro"
      - "/etc/localtime:/etc/localtime:ro"
      - "/mnt/zpool/media:/media:ro"
    devices:
      - "/dev/dri:/dev/dri"
      - "/dev/dvb:/dev/dvb"
    restart: unless-stopped
    logging:
      driver: json-file
      options:
        max-file: "3"
        max-size: "10M"

In my Settings > Network I’ve set my LAN Networks to the CIDR’s 192.168.0.0/16,172.0.0.0/8,10.10.10.0/24; however, my server still appears as Remote to all my LAN clients, despite them being one hop away and on that 192.168.0.0/16 CIDR:

image

Would love a solution other than “Set networking to ‘Host’ instead of ‘Bridge’”, as I’d prefer to have the container be resolvable to other bridge-networked containers.

3

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