Plex server - Remote Access PROBLEM - INTERMITTENT ACCESS

(Opening this as separate issue, since I have no more activity on the original topic where it was also mentioned.)

Problem:

As I detaily described here, I have constant problems with remote access to the plex media server from my devices. If accessed from LAN, there are no issues however if accessed from WAN, server keeps disconnecting. Have to keep restarting the client until server will show up - same for desktop or phone. Sometimes playback works but when I try to fast forward movie it disconnects from the server and have to restart client again - very annoying!

It is dockerized setup on the host network:

version: '3.7'

services:
  plex:
    image: plexinc/pms-docker:plexpass
    container_name: plex.529
    restart: always
    network_mode: host
    volumes:
      - $PWD/plex/config:/config
      - $PWD/plex/transcode:/transcode
      - /lvm/raid/private/media:/plex/media
      - /lvm/raid/private/data:/plex/data
    environment:
      - TZ=Europe/Prague
      - PLEX_UID=1000
      - PLEX_GUID=994
      - ADVERTISE_IP=http://192.168.255.11:32400/
      - ALLOWED_NETWORKS=192.168.255.0/24,10.8.0.0/24
    labels:
      - com.ouroboros.enable=true
      - traefik.enable=true
      - traefik.port=32400
      - traefik.frontend.entryPoints=https
      - traefik.frontend.rule=Host:plex.example.com
      - traefik.backend=plex.529
      - traefik.frontend.headers.forceSTSHeader=true
      - traefik.frontend.headers.STSSeconds=315360000
      - traefik.frontend.headers.STSIncludeSubdomains=true
      - traefik.frontend.headers.STSPreload=true

As i mention in other topic, this wasn’t happening before. I even switched back to my old router and exactly same behavior! I am willing to troubleshoot with someone.

How to replicate:

Every time I did a configuration change on the network I restarted the docker container for plex service, then tried to re-enable remote access again. And the results is, that for like 2-3 seconds it blinks green " Fully accessible outside your network"

image
image.jpg991Ă—423 159 KB

but right after that it goes again:

image
image.jpg997Ă—430 163 KB

I am really clueless now and desperate to fix it.

Server version:

Version 1.15.1.710

Logs:

Plex Media Server Logs_2019-03-04_15-08-24.zip (4.5 MB)

Any input will be appreciated. Thanks.

kindly any attention here? I even replaced my home router with old TP-Link using OpenWRT… exactly same behavior… appreciate any inputs/directions

I’m not a Docker guru by any means, but do see it does not seem to be able to get your external IP for some reason. Mar 04, 2019 14:57:31.733 [0x7f2247fff700] DEBUG - MyPlex: Sending Server Info to myPlex (user=xxxxxxxx, ip=, port=999)

I ran it by someone and think it may be a conflict between your reverse proxy (traefik) and the PMS container running in host mode over port 32400. Should either run it and the proxy in bridge mode with ports only open in the proxy container, or ditch the proxy and use host mode, but not both

Also if using a proxy need to add your proxy dns to the ADVERTISE_IP, so http://192.168.255.11:32400/,https://my.movies.com:32400

1 Like

Hi, appreciate the effort.

I had configured ADVERTISE_IP through the app directly before anyway. Tried putting it directly as environment variable - no change.

Secondly I completely disabled reverse-proxy settings and it is behaving exactly the same:

version: '3.7'

services:
  plex:
    image: plexinc/pms-docker:plexpass
    container_name: plex.529
    restart: always
    network_mode: host
    volumes:
      - $PWD/plex/config:/config
      - $PWD/plex/transcode:/transcode
      - /lvm/raid/private/media:/plex/media
      - /lvm/raid/private/data:/plex/data
    environment:
      - TZ=Europe/Prague
      - PLEX_UID=1000
      - PLEX_GUID=994
      - ADVERTISE_IP=http://192.168.255.11:32400/
      #- ADVERTISE_IP=http://192.168.255.11:32400/,https://plex.aronmgv.com
      - ALLOWED_NETWORKS=192.168.255.0/24,10.8.0.0/24
    #labels:
    #  - com.ouroboros.enable=true
    #  - traefik.enable=true
    #  - traefik.port=32400
    #  - traefik.frontend.entryPoints=https
    #  - traefik.frontend.rule=Host:plex.aronmgv.com
    #  - traefik.backend=plex.529
    #  - traefik.frontend.headers.forceSTSHeader=true
    #  - traefik.frontend.headers.STSSeconds=315360000
    #  - traefik.frontend.headers.STSIncludeSubdomains=true
    #  - traefik.frontend.headers.STSPreload=true

And thirdly I put it on its own network:

version: '3.7'

services:
  plex:
    image: plexinc/pms-docker:plexpass
    container_name: plex.529
    restart: always
    #network_mode: host
    ports:
      - 32400:32400/tcp
      - 1900:1900/udp
      - 3005:3005/tcp
      - 5353:5353/udp
      - 8324:8324/tcp
      - 32410:32410/udp
      - 32412:32412/udp
      - 32413:32413/udp
      - 32414:32414/udp
      - 32469:32469/tcp
    expose:
      - 32400
    volumes:
      - $PWD/plex/config:/config
      - $PWD/plex/transcode:/transcode
      - /lvm/raid/private/media:/plex/media
      - /lvm/raid/private/data:/plex/data
    environment:
      - TZ=Europe/Prague
      - PLEX_UID=1000
      - PLEX_GUID=994
      - ADVERTISE_IP=http://192.168.255.11:32400/
      - ALLOWED_NETWORKS=192.168.255.0/24,10.8.0.0/24

This seems to solve the problem with the disconnecting over WAN. However issue with DLNA is now permanent:

docker-compose ps:

        Name            Command      State                                             Ports
----------------------------------------------------------------------------------------------------------------------------------
plex.529                /init     Up (healthy)   0.0.0.0:1900->1900/udp, 0.0.0.0:3005->3005/tcp, 0.0.0.0:32400->32400/tcp,
                                                 0.0.0.0:32410->32410/udp, 0.0.0.0:32412->32412/udp, 0.0.0.0:32413->32413/udp,
                                                 0.0.0.0:32414->32414/udp, 0.0.0.0:32469->32469/tcp, 0.0.0.0:5353->5353/udp,
                                                 0.0.0.0:8324->8324/tcp
plex.529.handbrake.89   /init     Up             0.0.0.0:52989->5800/tcp, 0.0.0.0:52990->5900/tcp
plex.529.jackett.85     /init     Up             0.0.0.0:52985->9117/tcp
plex.529.lidarr.83      /init     Up             0.0.0.0:52983->8686/tcp
plex.529.ombi.84        /init     Up             0.0.0.0:52984->3579/tcp
plex.529.radarr.81      /init     Up             0.0.0.0:52981->7878/tcp
plex.529.sonarr.82      /init     Up             0.0.0.0:52982->8989/tcp
plex.529.tautulli.86    /init     Up             0.0.0.0:52986->8181/tcp

netstat:

root@caradhras:[/docker/plex]: netstat -tulpn | egrep "1900|3005|5353|8324|32400|32410|32412|32413|32414|32469"
tcp6       0      0 :::8324                 :::*                    LISTEN      826/docker-proxy
tcp6       0      0 :::32400                :::*                    LISTEN      740/docker-proxy
tcp6       0      0 :::32469                :::*                    LISTEN      621/docker-proxy
tcp6       0      0 :::3005                 :::*                    LISTEN      924/docker-proxy
udp6       0      0 :::32410                :::*                                711/docker-proxy
udp6       0      0 :::32412                :::*                                694/docker-proxy
udp6       0      0 :::32413                :::*                                682/docker-proxy
udp6       0      0 :::32414                :::*                                655/docker-proxy
udp6       0      0 :::1900                 :::*                                940/docker-proxy
udp6       0      0 :::5353                 :::*                                903/docker-proxy

So my question is: Is it possible to advertise DLNA out of its LAN (the docker container network bridge in this case) to the host LAN?

Thanks, Michal

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