Server Version#: latest
Player Version#: latest
I’ve installed a new Plex LXC container in Proxmox, but if I try and access the web interface, as soon as I sign in with my Plex account, I get the error that I’m not authorized. I do have a couple other Plex servers but I shut them down before I installed the container. What am I missing?
If the container IP is on a different subnet as your computer
then you will get this.
PMS does not allow setting up “remote” without some kind of authentication
- SSH tunnel into the box
or - SSH into the box and claim using a claim token.
Yeah that must be it. I’ve SSh’d in, but how do I claim it via the command line?
- SSH into the box.
- make certain you have
curlinstalled (not all have it by default) - With PMS running
- https://plex.tv/claim
- COPY the claim token from the browser
- Switch to the SSH session
curl -X POST 'http://127.0.0.0.1:32400/myplex/claim?token=PASTE_TOKEN_HERE'- Hit enter.
- After 15-30 seconds, you’ll get a flood of XML from “MyPlex”.
- The server will now be claimed.
BE ADVISED: The claim token is valid for 5 minutes and only 1-time use.
If you’re on-task and not wasting time, you’ll be fine.
EDIT
[chuck@lizum ~.2006]$ curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-19hczxFsmqKiKTeht9cA'
supplemental,
being in the LXC, if you stop plex, given the LXC runs as ‘root’ user inside,
you can use my claim script if you wish.
I did it slightly differently but it worked. Since I used the Proxmox Helper Script there is no way to edit the container to edit the paths so it’s useless for me. I’ll reinstall with good ole Docker and use this. Thanks for the guidance.
Didin’t even know you had that. Will definitely bookmark that.
for me, (lxd / lxc environment), i go direct
| plexdev | STOPPED | | | CONTAINER | 0 |
+---------------+---------+---------------------+---------------------------------------------+-----------+-----------+
| testbed | STOPPED | | | CONTAINER | 0 |
+---------------+---------+---------------------+---------------------------------------------+-----------+-----------+
| ubuntu22 | STOPPED | | | CONTAINER | 0 |
+---------------+---------+---------------------+---------------------------------------------+-----------+-----------+
[chuck@lizum ~.2013]$ lxc start debian11
[chuck@lizum ~.2014]$ lxc exec debian11 bash
root@debian11:~# whoami
root
root@debian11:~# hostname
debian11
root@debian11:~#
might you be able to do that from proxmox CLI ?
Not sure what’s happening in that, so no. I think I have to do something like mount IPaddress:/share/name and see if that will mount it to the container. Never done it before with a remote NAS though so I don’t know.
For me, when dealing with LXC.
-
NFS mount the share on the host.
-
I then share the NFS-mounted directory into the LXC
(LXC does not permit network mounts inside the container) -
lxc config device add ContainerName ShareName disk source="/host/path" path="/inside/container/path"
I’ll try that. I ended up installing it on Ubuntu and mounting the drives into the VM, which worked fine. However, even though when I cd into the plexmedia directory and subdirectories I created for the media and do an ls and can see all the media, Plex can’t see it. I thought it might be a permissioning issue, but when I look at the permissions, it doesn’;t seem like it’s a permissioning issue. Any idea what I could be missing that won’t allow Plex to see the plexmedia folder and subfolders?
Remember the rules of mounting
- Create the mount point directory
- Set ‘755’ permissions for the mount point directory
- Mount the directory
- Check the permissions again AFTER mounting. Adjust as needed.
- Now confirm user
plex(or the user you’re running as) can see the contents - If not, go to the network source and relax the permissions.
I use NFS, sec=sys mount option for this reason.
It tells the NFS server to trust the client host to verify security (system level trust)
As soon as I learn what “set 755” means" and how to check and set permissions I will remember it! 
I can’t tell what the user is. Just seems like it’s a bunch of random numbers. I tried sudo chown nobody:nogroup -R /plexmedia/ and it came back with an error that the movies file has a stale file handle. Not sure if that’s important or not. Made no difference anyways for the rest of the folders.
Where did you get your Linux driver’s license from? 
Did you give a read of my tutorials
The entire collection is here:
1 Like
Still on chapter 1 of The Linux Command Line 2nd Edition! I’ll check these out. I got it working. Now I need to get my head around installing all the arrs in Docker, on top of Ubuntu with remote shares. Bit of a headwrecker that one.
“arrs” ?
In the container:
- You mount the remote share(s) on the host.
- you MAP the host directory (which now has the remote share mounted to it into the container.
- Magic happens
Prowlarr, Lidarr, Bazarr, Sonarr, Radarr. The tricky bit is trying to understand GUIS, PUID, ownership and permission for each of the services mapped to each of the folders.
-
each of them is their own docker container.
-
I recommend a parent ‘docker’ directory
/top-level-path/docker -
Subdirectories for each app
/top-level-path/docker/sonarr
/top-level-path/docker/nzbget
etc -
using
network=hostso they all talk to each other easily as that same host -
Once you have the first one, the rest are copy/cookie-cutter
This is something I could use for docker run for nzbget
sudo docker run \
-d \
--name nzbget \
--network=host \
-e TZ="EST" \
-h usenet \
-e PUID=1000 \
-e PGID=1000 \
-v /sata/config/nzbget:/config \
-v /sata/usenet:/usenet \
-v /sata/download:/download \
linuxserver/nzbget
sudo docker update --restart=unless-stopped nzbget
sudo docker start nzbget
this configuration allows me to delete the container, change config, or pull, without losing anything in /config
1 Like
You’re the best Chuck. Quick question though; I use Portainer for container management and it creates a top level directory. Do you think there would be any issue using that?
