but if we was to install native whats the difference to running via this media box (docker) setup other than using SSL “Domains” to access PMS , and being able to control multiple modules
Do you have multiple PMS servers in various containers?
this server runs 1x PMS Server
do you need to see the specs of server ?
the only dockers running are
plex
nginx-proxy
letsencrypt
portainer
wow. just wow.
I don’t understand why you built it that way.
Unfortunately, managing that beast is outside of what I or any of us can do here.
I say this because there’s nothing I see in your logs which indicates any kind of error within PMS . The most I found was the proxy and the bandwidth limiting.
There are folks who use LetsEncrypt on their hosts with PMS running native.
That’s easy.
ok Chuck , so in regards to the Native Build is there any difference or affect it would have? to how its running currently?
this is the build and how plex is setup https://github.com/Cloudbox/Cloudbox/wiki/Install:-Mediabox
do not many people use plex like this?
how does the majority of the plex world setup then?
When most folks setup their PMS servers on VPS, they run native packages because they ‘own’ the host even though it’s virtual and will float on different hardware (transparent to them and PMS).
They install their OS (Debian / Ubuntu typically) and install the native package.
Being that way, the package installer finds the transcoding hardware and makes all the setups for native hardware transcoding (Intel QSV-capable CPUs of course).
the server is installed onto a Dedicated Server,
currently the Media is Virtually Mounted via Rsync , “use cloud storage for the media” has worked for years only recently started to get issues,
so plex would need to be setup from scratch or could we backup all the content from my current build (plex setup) so we dont have to let everything re-download to plex,
and restore to new build as a native setup
this is the server that is being used for the Plex Setup
https://www.ovh.co.uk/dedicated_servers/infra/infra-2/
Here’s the ace up our sleeve,
PMS will not care where / how the media is mounted – PROVIDED – it’s at the same path (or even similar path) in the file system and accessible like it was before.
What we do (broad strokes here for now)
- Turn off all auto scanning, Empty trash, and anything else that modifies / removes metadata
- Stop PMS
- Make a tar.gz of the
./Librarydirectory (/var/lib/plexmediaserver is the default) - We copy that and drop it, enmass, onto the new machine which has the media mounted and waiting.
Now, we have a few options.
The media can be at the same exact mount point
-or-
at new mount points
We don’t care. The steps I outlined above allow both options.
I have the Linux-Tips “How To’s” to show how to do all this.
It’s detail rich (how I wrote it) but not complex.
Want to see the procedures ?
do you have a guide or info of a native setup ? ive only ever done via docker?
before swapping the dedicated, would try on vm 1st, to minimise downtime , so i know i can get it perfect 
absolutely.
IIRC about docker (correct me here as needed)
- you have a
/configpath. That’s the same as theLibrary/Application Supportfor the native. - You have that outside the container in the native FS?
- Make a tarball of it from outside the container (stopped of course and with the automatic stuff all turned off especially empty trash)
- Copy that into the VM .
You’re doing two things at the same time.
- cloning the host
- relocating the media
complete the steps for both (clone first) and it will fall in line.
Here’s the how-to’s to read and study. Hollar if you need more .
-
Backup/reload/clone the host from one (docker) to another (inside the VM)
Back up/ Restore /clone your PMS metadata -
This is the media relocation (changing mount points)
Moving your media and keeping the metadata - The TL;DR
Only ONE caution here.
Cloning is a perfect clone (copy). The server ID numbers as well. You’ll get a collision if both come online at the same tine. At some point, the MachineID, ProcessedMachineID and AnonymnousMachineID values in Preferences.xml will need be removed so new can be generated (in the new VM / host). It’ll save the other credentials but separate the otherwise identical twins.
If you think about this, you could stand up the new machine in the VM then take it live on the Hosted machine after you’ve gotten it all perfected.
Thanks mate, ill spin up the VM and see how far i can get on with this , once i have sucsessfully managed to do the test vm ill let you know or if i get issues, ill do this tommorow as its 3am here so quite late, thanks for your advice i hope this fixes my issues
doing native install is easy: (sorry, left that out)
- Recommend debian/ubuntu (new installer) because it’s visual output of config
- Setup the OS
- Download the DEB file from Plex.tv/downloads.
- dpkg -i filename.DEB
- Open 127.0.0.1:32400/web
- Run setup wizard in browser
- Done
Thank you , will start it tommorow , had a few crazy mad days 
thanks again mate will come back with update
sorry ive been inactive will check this now!
im at the backup stage of plex , how would i backup from current plex and import to new, is it all within web interface?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.