I am attempting to add a second Plex server on the same network and subnet. However when I go to the new servers ip address:32400 all I see is my existing server, and I can find no way to add the new one. Reading forum posts I saw that it should be under Settings/Server/General, but all I can do there is rename my existing server. I have searched for an answer to this for three days and nothing that I have seen has worked. If it makes a difference my existing server is a plugin for FreeNAS, and the new server I am trying to add is on Ubuntu Server 20.04.3 running under Docker. Any ideas would be greatly appreciated.
Server Version#:1.18.9.2578 (I Think, of the existing server)
Player Version#:
If you have the new server under docker, use the PLEX_CLAIM method as described here
Thanks for the reply. I hope I’m smart enough to work through that. I was attempting to use Cockpit to run Docker, but I see no way to use Docker-Compose through Cockpit, so I guess that’s out. Question though. What I’m trying to do now is to build a testing server to see if Plex will work well for me through Docker, as I had a LOT of problems running it inside a VM on my FreeNAS server. And I’m considering rebuilding my FreeNAS server and running it on Ubuntu with Docker. Will there be a problem getting another claim-token if I decide to rebuild the main server and get rid of the testing one?
Claim tokens are valid for 5 minutes.
When you need another – simply go get one.
Thanks. Hopefully only one more question, but seeing how this is kicking my butt it probably won’t be the only one 
Am I correct in my reading comprehension that I will only have to use the ‘docker-compose up’ command the first time I start the container, and then after that I would start it using the normal way with docker commands?
I don’t use Docker compose.
Docker run is just as good
Here is a working example.
[chuck@lizum docker.2017]$ cat dockerplex
sudo docker stop plex
sudo docker rm plex
# Remove old image if exists
Image="$(sudo docker images | grep -i plex | awk '{print $3}')"
if [ "$Image" != "" ]; then
sudo docker stop plex
sudo docker stop plex
sudo docker rm plex
sudo docker rmi -f $Image
fi
sudo docker run \
-d \
--name plex \
--network=host \
-e PLEX_CLAIM="claim-2rZSB3JW2t56cJngN9kt" \
-e TZ="EST" \
-e LANG="en_US.UTF-8" \
-e PLEX_UID=1000 \
-e PLEX_GID=1000 \
-e PUID=1000 \
-e PGID=1000 \
-h dockerplex \
-v /sata/dockerplex:/config \
-v /sata/dockerplex/tmp:/tmp \
-v /sata/dockerplex/transcode:/transcode \
-v /glock:/data \
--device=/dev/dri:/dev/dri \
plexinc/pms-docker:plexpass
#docker start plex
#docker update --restart=unless-stopped plex
[chuck@lizum docker.2018]$
/sata is a local HDD where the container runs.
/glock is my nas root mount point for all network shares.
I knew that wouldn’t be my last question. Keeping in mind that linux is like martian to me, I assume that ‘dockerplex’ is a batch file? and to create it I would just use nano and name it ‘dockerplex’ with no extension? Also, if the plex-claim token is good for only 5 minutes, wouldn’t you have to get another one anytime the container was stopped and you tried to restart it? Sorry if I sound like an idiot. I have been googling the crap out of this and each answer I see confuses me more
While learning is fun.
- Setup a VM
- Play in that VM
- Learn Linux.
- Add Docker in trhat VM and master it.
-or-
Stay with what you know.
Why do I say this?
-
Linux isn’t forgving.
-
Linux doesn’t have ‘batch’ files, it has ‘scripts’. They can have any name I want to assign.
-
Docker is a containerization technology. Understanding how it connects to the underlying OS is critically important.
-
Plex on Linux requries you to have a decent command of Linux. Add Docker to that – you better be ready.
-
Lastly, and regrettably, We are here to support Plex but not to teach Linux or Docker. We’re not equipped or staffed for that. Sorry
Which is exactly why I am using a testing server to figure all this out. If it works as I hope then I will rebuild my main server with what I have learned.
So, while your file “dockerplex” isn’t a batch file, it is a script file? If I know this then I can figure out how to make and use one. But the question about the plex-claim token remains. If it is only good for 5 minutes, then wouldn’t this script (assuming I have my terms correct) file cause an issue after the 5 minutes had expired? Or does Plex only look at that parameter on the first run and then it ignores it?
The Plex Claim token serves one purpose only. – To claim (attach) a newly created server instance to an account when that server instance is otherwise headless or on a different network (NAT) configuration and cannot be claimed by conventional interactive means.
I have a couple questions –
Why the references to “Batch file” ?
Are you trying to add a docker container of Plex in the WSL layer of Windows?
No, I just know the term from DOS and Windows. I figured that Linux had something similar, but I wasn’t aware that it was called a script. But when I looked at what you posted above it reminded me of a batch file, so that’s what I called it.
What I’m trying to work out is this. When I built my current server I tried to set up Plex in a VM, but it’s performance was horrible. So I ended up using a FreeNAS plugin for it, and that works fine. But I would like to replace my FreeNAS server with one running Ubuntu Server for various reasons, and wanted to find out if running Plex inside Docker will be be better than it was in the VM. If it’s not better, then I will be forced to stay with FreeNAS regardless. But to test it out I need to be able to set it up as a different server within my account, thus all my stupid questions And that’s where all this started, I had Plex running inside Docker just fine, but all I could see was my existing server, and I couldn’t figure out how to tell it that this was a different server.
And I get that the purpose of the Plex Claim token is to show that it is a new server, I was just curious about it being left in the script after the first time it was run and the new server instance was established. But I assume that if that is the script that you run it doesn’t cause an issue. I will give this a go tomorrow and hopefully everything will come up roses for a change I certainly appreciate your assistance here.
Please remember KISS, I would recommend using a bare bones install of the latest Ubuntu LTS, and avoiding docker. Just install the deb and follow the standard setup for Linux.
chuckpa,
I finally got it all working today, and it works better than I expected. Now to transfer what you taught me from the test server to a production server. Thanks for all your help and patience dealing with a complete moron! Thanks again!!
We were all morons at one point. Some of us still are. I’m prime example. My family reminds me ALL THE TIME 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
