Plex content stops being available unless I make a new user

Hello! I am running the plex:latest image, and I am unable to see the content in the Plex UI, whereas yesterday I was perfectly able to.

Here’s the setup:

  • In my Ubuntu machine, I run the image using the suggested docker-compose file in Docker (under Usage)
  • This machine is given IP 192.168.0.200. The machine name is “xibalba”. In my laptop, I access 192.168.0.200:32400 and I get access to the web UI.

The first time I set it up, it was working just fine. After a few hours, I was unable to load the content, and I created a new user purely for testing, and I realized this new user was able to see the content.

Today, it happened again. This second user stopped being able to load the content, so I created a new user, and things are working again. Obviously, I don’t want to have to create a new user every day, so I was wondering what’s the reason for this behaviour, and if there is something I can do to have the content available for all users.

Here’s a video of the issue: plex

Please provide your compose and full container logs which begin with our ascii logo. Also share the plex app version. we will likely request more info once we have this.

Sure thing!

Here’s the Docker compose file:

  GNU nano 6.2                                                                  docker-compose.yml
---
version: "2.1"
services:
  plex:
    image: lscr.io/linuxserver/plex:latest
    container_name: plex
    network_mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - VERSION=docker
      - PLEX_CLAIM= #optional
      # - ADVERTISE_IP="http://xibalba:32400/"
    volumes:
      - ./config:/config
      - /media/long/COLOSSUS/Series:/tv
      - /media/long/COLOSSUS/Movies:/movies
      - /media/long/COLOSSUS/Music:/music
    restart: unless-stopped

Docker logs:

plex  | [migrations] started
plex  | [migrations] no migrations found
plex  | ───────────────────────────────────────
plex  |
plex  |       ██╗     ███████╗██╗ ██████╗
plex  |       ██║     ██╔════╝██║██╔═══██╗
plex  |       ██║     ███████╗██║██║   ██║
plex  |       ██║     ╚════██║██║██║   ██║
plex  |       ███████╗███████║██║╚██████╔╝
plex  |       ╚══════╝╚══════╝╚═╝ ╚═════╝
plex  |
plex  |    Brought to you by linuxserver.io
plex  | ───────────────────────────────────────
plex  |
plex  | To support LSIO projects visit:
plex  | https://www.linuxserver.io/donate/
plex  |
plex  | ───────────────────────────────────────
plex  | GID/UID
plex  | ───────────────────────────────────────
plex  |
plex  | User UID:    1000
plex  | User GID:    1000
plex  | ───────────────────────────────────────
plex  |
plex  | **** Server already claimed ****
plex  | Docker is used for versioning skip update check
plex  | [custom-init] No custom files found, skipping...
plex  | Starting Plex Media Server. . . (you can ignore the libusb_init error)
plex  | [ls.io-init] done.
plex  | Critical: libusb_init failed

And I’m running Plex Version 4.108.0

the highest plex server version is 1.32.7 which was pulled because it was a bad release

I think the most likely issue you have is you’ve put ./config:/config so the config path is in /root which uid 1000 would not have access to. Use a full path, if we pretend UID 1000 is named docker you would use - /home/docker/plex:/config or something similar to this.

My bad, I looked at the Version of the Plex Web app in the browser. If I’m not mistaken, my Docker inspect is telling me that the version is 1.32.5.7349-8f4248874-ls179

User with UID 1000 is my current user:

id -nu 1000
long

and it seems like the files in the config folder are all owned by this user:

ls -alish
total 16K
10092545 4,0K drwxrwxr-x  3 long long 4,0K Thg 9  19 19:55 .
 8781825 4,0K drwxrwxr-x 10 long long 4,0K Thg 9  18 23:54 ..
10092546 4,0K drwxr-xr-x  3 long long 4,0K Thg 9  19 15:10 config
10092547 4,0K -rw-rw-r--  1 long long  524 Thg 9  19 14:18 docker-compose.yml

ls -alish config/Library/Application\ Support/Plex\ Media\ Server/
total 76K
10092550 4,0K drwxr-xr-x 13 long long 4,0K Thg 9  19 19:54  .
10092549 4,0K drwxr-xr-x  3 long long 4,0K Thg 9  19 15:10  ..
10092816 4,0K -rw-------  1 long long   42 Thg 9  19 19:41  .LocalAdminToken
10092551 4,0K drwxr-xr-x  7 long long 4,0K Thg 9  19 19:54  Cache
10092561 4,0K drwxr-xr-x  3 long long 4,0K Thg 9  19 15:10  Codecs
10092552 4,0K drwxr-xr-x  3 long long 4,0K Thg 9  19 19:41 'Crash Reports'
10092557 4,0K drwxr-xr-x  2 long long 4,0K Thg 9  19 15:10  Diagnostics
10092565 4,0K drwxr-xr-x  2 long long 4,0K Thg 9  19 15:10  Drivers
10092559 4,0K drwxr-xr-x  3 long long 4,0K Thg 9  19 19:54  Logs
10092831 4,0K drwxr-xr-x  3 long long 4,0K Thg 9  19 15:12  Media
10092842 4,0K drwxr-xr-x  6 long long 4,0K Thg 9  19 15:14  Metadata
10092555 4,0K drwxr-xr-x  7 long long 4,0K Thg 9  19 15:11 'Plug-in Support'
10092609 4,0K drwxr-xr-x  2 long long 4,0K Thg 9  19 15:10  Plug-ins
10092828 4,0K -rw-------  1 long long  675 Thg 9  19 19:41  Preferences.xml
10092629  16K -rw-------  1 long long  13K Thg 9  19 19:41 'Setup Plex.html'
10092638 4,0K drwxr-xr-x  2 long long 4,0K Thg 9  19 15:10  Updates

I will experiment with different locations for the config folder as suggested

if nothing else, try using a full path to the location you expect config files to be. It’s never a good idea to use relative paths in docker :smiley:

That all said, if my thought is not the issue and since your logs show nothing wrong, i would say this is a plex issue rather than a container issue and you’d need to seek help from them if the full path doesnt work.

I tried using /home/long/plex/config, I tried not mapping the volume at all, but same problem. Now I have 3 users that can’t access the content, but as soon as I create new ones, I can use the app without trouble :frowning:

Thanks for the help, I will try to find the Plex support forum and I will ask them