Need to restart Plex Media Server daily since recent data breach

Plex Media Server
1

Server Version#: 1.42.2.10122-3749b980e
Player Version#: 1.110.0.351-4e48eb83
Web Version#: Version 4.149.0

I am running a Plex Media Server instance through Docker, based on the linuxserver.io image.
Ever since I received the email of the data breach, I had to re-setup my server environment, as I also resetted all sessions that I had. The server runs fine and works, the only problem is, ever since I re-setup the environment, I need to restart the Plex Media Server daily, because the clients don’t seem to connect.

Looking at the log files, I don’t see anything out of the ordinary and I don’t even see an error message at all, but maybe I am looking at the wrong log file, I checked the ‘Plex Media Server.log’ files from /Library/Application Support/Plex Media Server/Logs.

For me and my friends on my server, this is rather annoying, as they have to ask me pretty much daily if I can restart Plex. After the restart, everything is working fine again, until it doesn’t work anymore. Any kinds of tips or advice, would help me out a lot!

2

Looks like you don’t have it set to host networking. Which could mean it is acting as if on a different network and things like port forwards to the normal network won’t work. (Of course you could have custom network things set up that it does not matter but in general host networking is easiest)

3 
  plex:
    image: lscr.io/linuxserver/plex:latest
    security_opt: ['no-new-privileges:true']
    container_name: plex
    hostname: plex
    ports:
      - 32400:32400
    environment:
      - PUID=${ID_USER}
      - PGID=${ID_GROUP}
      - VERSION=latest
      - PLEX_CLAIM=claim-{something}
    networks:      
      - downloads-ext
    devices:
      # Intel QSV
      - /dev/dri:/dev/dri
    volumes:
      - ./plexmediaserver:/config
    restart: unless-stopped
    labels:
      - "traefik.enable=false"

I added the network_mode: “host” rule here (and commented out the 2 current networks sentences), is that what you mean? I didn’t use that before I reset my password due to the breach last week and it worked perfectly, so I doubt this is the reason.

4

if it happens again after the change please let us know, we will likely need to see the server logs.

1 Like
5

So far it seems networking_mode: host was the answer indeed, but it doesn’t explain why it did work without it at first and I would like to understand that part too