I’ve essentially joined the networks together. I already have Tailscale running on my proxmox server from our initial set up, so you can follow the steps here. If you’re new to Tailscale, you can read more about it here. For me though, the quickest and by easiest is to use Tailscale. With that said, I will want the ability to administer the server remotely. If you do wish to remotely view your library or share it with others, have a look below for some additional steps needed to give the server access to the wider web.Įspecially pay attention to the ADVERTISE_IP variable section. This particular server will not be used for remote viewing due to bandwidth constraints. Now this tutorial isn’t about how to set up Plex, it was just how to get it up and running using Docker-Compose. I will probably add an external drive to Proxmox and use that as my file store, but that’s for another tutorial. These become the basis for my media libraries and I will need to populate these. I also went ahead and created several folders under home/docker/plexms/media (“movies”, “music” and “tvshows”). Note this claim code changes every 4 minutes, so if you’re slow out of the gate then you need to get a new code by following the instructions again and changing it in your compose file. This will essentially add this new Plex server to your Plex account. For example if your Claim Code was claim-t33iotdCjhnBTwD_14PU then input the whole string as follows: You should then just paste the whole variable into the compose file above (inc claim). If you’ve already logged into Plex on that machine, the Claim Code should just pop right up: This Code will Self Destruct in 4 minutesĬopy the code in its entirety including the claim- bit at the beginning. The procedure for getting the actual token you need is as follows You need to use the Plex Claim in order to add this server to your plex account. Obviously, no one would ever use root as the user right? □ No one uses root, right? Plex Claim You can get your relevant ID’s from running the command id and your username on the command line. You could easily substitue that with your own PGID and PUID as per the following lines (for example): This is because I have defined those variables in an environmental file (nano /etc/environment). You may notice I am using $(PUID),$(PGID) and $(USERDIR). The only things that might seem different to other compose files is the number of ports that you need to define for Plex to work properly, as well as the “PLEX_CLAIM” entry. If you’re familiar with Portainer, most of this would seem pretty self explanatory. The image I’ll be using is plexinc/pms-docker. This server will be direct access play only, so I don’t have any concerns about needing to transcode. I can use both in Proxmox, so see no issue here before you flame me in the comments :)).įor those interested, I’m currently running all of this on my beelink GK mini, which continues to perform like a champion. (I know there are LXC’s out there already, but I’m a fan of docker, and prefer to work with it. In this article I’ll take you through a quick docker compose set up of Plex, including getting the appropriate token and how to configure it using Portainer, sitting on Proxmox. Personally, I find them easier to manage. I am a fan of docker compose and using stacks on Portainer. Whilst searching through various Plex articles I found that whilst there was plenty of documentation about how to get it up and running, there were very few methods using compose. So continuing with my Proxmox / docker journey, I decided it was time to fire up Plex and get some kind of media server up and running.
0 Comments
Leave a Reply. |