Running on Bridge Network Leads to Streams Running over WAN instead of LAN

Hi All,

After getting my new PMS container up and running I noticed that I was streaming data over the internet and not directly from the LAN. I did some reading and it appears to be a common issue, so tried the following recommendations:

  • Modified the Custom URL in Plex settings to 192.168.0.1/24 - Result: Continued streaming over the internet.
  • Accessed the server directly by the IP address 192.168.0.XXX - Result: Works as expected.
  • Changed from using the Bridge Network to Host - Result: Traffick runs over LAN, but is very slow to load details within the GUI (images, metadata, episodes etc), as well as heavily buffering video.
  • Turned off Remote Access - Result: Unable to connect to server from any of my clients.

This is what my docker-compose.yml file looks like as of now.

secrets:
  plex_claim:
    file: ../../secrets/plex_claim

services:
  # Plex - Media Server
  plex:
    image: plexinc/pms-docker:plexpass
    container_name: plex-media-server
    # network_mode: host
    networks:
      - default
    security_opt:
      - no-new-privileges:true
    restart: "unless-stopped"
    # profiles: ["media", "all"]
    devices:
      - /dev/dri:/dev/dri # for hardware transcoding
    ports:
      - "32400:32400/tcp"
      - "3005:3005/tcp"
      - "8324:8324/tcp"
      - "32469:32469/tcp"
      - "1900:1900/udp"
      - "32410:32410/udp"
      - "32412:32412/udp"
      - "32413:32413/udp"
      - "32414:32414/udp"
      #- "33400:33400/tcp"
    volumes:
      - ../../appdata/plexmediaserver/config:/config
      - /mnt/syno-video:/data/media
      # - $EXTDIR/ssd/home-server/downloads:/data/downloads
      # - /dev/shm:/data/transcode # Offload transcoding to RAM if you have enough RAM
    environment:
      TZ: $TZ
      HOSTNAME: 'PlexServer'
      PLEX_CLAIM_FILE: /run/secrets/plex_claim
      PLEX_UID: $PUID
      PLEX_GID: $PGID
      # ADVERTISE_IP: "http://$MEDIASERVER_IP:32400/,http://$ZEROTIER_IP_MEDIASERVER:32400/,https://proxplex.$DOMAINNAME_CLOUD_SERVER"
      # ALLOWED_NETWORKS: 192.168.0.0/24,172.16.0.0/16
    secrets:
      - plex_claim

Does anyone know why I might be experiencing this issue?

Thanks For Your Help

After some tinkering, it appears that adding the local IP to the ADVERTISE_IP environment variable resolved the issue.

Friend, thank you very much for your feedback on your post, it was of great help today. I was going crazy because my Plex started buffering on the LAN network, while external access was ok.
Thanks!

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