Docker Plex is all jacked up

Server Version#: 4.8.4
Plex Media Server.log (451.4 KB)
Player Version#: 4.8.4

Recently my Plex server is unable to work properly.

First is started with “Remote Access” issues where the tool would show it is accessible outside. After 5 seconds, it would show it is not accessible externally. Tried the following:

  • Port forwarding
  • DNS override with “plex.direct”
  • UPnP/NAT-PMP

All show the same behavior.

Then Plex wouldn’t come back up with my library anymore (nothing modified). I was forced to abandon my previous configurations and start fresh. configuration. However, now Plex is showing a “No soup for you!” message that reads “You do not have access to this server”.

I am connecting to my internal IP address to this server, so I have no idea why this is showing this.

Docker Images I have tried:

  • linuxserver/plex
  • plexinc/pms-docker (My preferred)

Nothing changes with either version.

Please help. This is killing me slowly.

EDIT:
It might also be pertinent to mention this is my setup.

[FreeNAS -> [Ubuntu VM as Docker server -> plex]]
The directory holds the Docker-Compose and Plex configuration is a mounts NFS share. Because FreeNAS doesn’t have an option to mount a local dataset/folder to VMs outside of NFS shares.

This is what the /etc/fstab/ has setup on the Ubuntu Docker server:
[IP of FreeNAS]:/mnt/main/repository /docker nfs defaults,nofail,exec,auto 0 0
[IP of FreeNAS]:/mnt/main/entertainment /entertainment nfs auto,defaults,nofail,exec 0 0

Console into the Plex docker and gather logs and post them.

Which logs? There are a ton of them.

Mainly “Plex Media Server.log”

It might also be pertinent to mention this is my setup.

[FreeNAS -> [Ubuntu VM as Docker server -> plex]]
The directory holds the Docker-Compose and Plex configuration is a mounts NFS share. Because FreeNAS doesn’t have an option to mount a local dataset/folder to VMs outside of NFS shares.

This is what the /etc/fstab/ has setup on the Ubuntu Docker server:
[IP of FreeNAS]:/mnt/main/repository /docker nfs defaults,nofail,exec,auto 0 0
[IP of FreeNAS]:/mnt/main/entertainment /entertainment nfs auto,defaults,nofail,exec 0 0

Hi Nokdim,

I haven’t heard back. Did you have better luck with the logs than I did?

I dont see anything glaring in the logs, I do see a roku playing items are you able to play from the roku?

Maybe try and point to a new /config directory and restart docker so its a fresh boot with no old configuration and see if it comes up happy that way.

Thanks for taking a look, @nokdim. I couldn’t find anything either. I’m thinking I need to move this solution to a non-NFS mounted drive. But I didn’t want to chance that I wouldn’t be able to get the files back on FreeNAS’s Hypervisor. (Not very Docker friendly.)

There is a RancherOS Docker host on FreeNAS, but I would still need to use NFS shares once again. sigh I need a better NAS system.

I’m working on moving the Plex Docker container to another Docker host that is on [bare metal [Alpine [Docker]]] to see if that helps.

I hope this works out.

If you know of a better Home NAS system that is more Docker friendly, feel free to give it a shout out. I’ve almost outgrown this one anyways.

I use UnRaid myself which is very docker friendly.
You can add a share from the NAS right into the docker container so no need for SMB or any fstab changes at all.

Well, I got everything to work. Had to do some config changes to the uPnP and work on issues with port sharing on Docker, but it is not up and connected. Thanks for the 2nd look, @nokdim. Appreciate the help!

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