@RJ17 said:
The install works fine using the spk but when it tries to start I get an error “Failed to run the package service” Any ideas what might be causing this issue?
Most likely down to the user account and DSM6.0 or DSM6.1 (known issue due to Synology changes). You can either install and run as root, run as plex (if on same machine) create a plexpy user account before installing, or modify the start-stop-status file. I run mine as the ‘plex’ user and have done so for well over a year.
relevant piece of script is:
USER=“plex”
start_daemon ()
{
# Launch the application in the background as root so we can open the dns port
sudo -u ${USER} /bin/sh -c “${PYTHON} ${PROG_PY} --pidfile ${PID_FILE} --daemon --nolaunch”
}
Same problem with HTTPS here - pyOpenSSL is installed, but not detected by PlexPy.
Logs show “2017-01-18 19:02:39 - WARNING :: MainThread : The pyOpenSSL module is missing. Install this module to enable HTTPS. HTTPS will be disabled”
…
Any idea how to fix this issue and enable HTTPS support ?
Thanks
Sorry - never got around to using HTTPS for my PlexPy. A few checks - are you using reverse proxy? Is the proxy handling the SSL, or is PlexPy? Are you sending all the correct headers to PlexPy through your reverse proxy. Problem is most likely related to one or more of these issues. Check for more info here
@rjblake said:
I’ve updated the SPK to now run as the ‘plex’ user (for those concerned with it running as root). As mentioned previously, I have only tested on DSM6.0 and have not added code to check for Plex PMS installation, Python installation; so these are prerequisites. As usual ‘use at own risk’
Thank you very much for this. I’ve been trying to get Plex monitoring software installed on my Syno for about 2.5 hours and this got it done in seconds. Really appreciate it!!!
@rjblake said:
I’ve updated the SPK to now run as the ‘plex’ user (for those concerned with it running as root). As mentioned previously, I have only tested on DSM6.0 and have not added code to check for Plex PMS installation, Python installation; so these are prerequisites. As usual ‘use at own risk’
Thank you very much for this. I’ve been trying to get Plex monitoring software installed on my Syno for about 2.5 hours and this got it done in seconds. Really appreciate it!!!
I have python installed and I manually installed the plex run as user. But nothing happened. Am I missing a step?
Btw do you recommend I install this on Docker? If so, how?
@trumpy81 said:
It would appear that the file has been removed or is otherwise unavailable.
If you are looking to install PlexPy, I might suggest that you use a Docker to install PlexPy with.
First you need to install Docker which can be found in Package Center->Utilities. Then open Docker, click on registry and search for the PlexPy package. The rest is up to you.
I am literally at the part the rest is up to you. I’m not sure what to do once PlexPy is installed via docker.
Edit: I don’t understand how people run terminal / SSH in synology. I need to figure that out.
It worked! My only other question is the desktop shortcut doesn’t work. But when I type in the address myself, plexpy populates. How can I fix this desktop shortcut? I made it https://myNASip:8181… is httpS an issue since it’s not a secure connection?
If so, is there a way to obtain HTTPS when connecting to PlexPy container?
Seems I have to do all those container steps again if I want to edit my desktop shortcut address?
Edit: Nvm. had to stop container then hit edit. simple enough. thanks so much trumpy81! I spent several hours searching the internet to figure this out.
@trumpy81 said:
First off, yes you need to create the dockersconfig folder and No it cannot be encrypted.
Secondly, you may need to edit the desktop shortcut. By default it should open the PlexPy Docker status page, not PlexPy in your browser, you can edit the Docker and set it to open PlexPy in your browser.
Stop PlexPy from running in Docker->Container, click on the toggle icon to the right of the Linuxserver/PlexPy image. Then click on Linuxserver/PlexPy to make sure it is highlighted and then click on Edit.
Click OK and then restart the Linuxserver/PlexPy Docker image by clicking on the toggle icon again and you should be good to go.
Thank you. I already created the dockersconfig folder and I chose encryption. So I need to restart the process and make an unencrypted folder? It seems to be working for now.
Edit: Also, once in PlexPy, do I need to setup a folder path for plex logs?
@rjblake said:
I’ve updated the SPK to now run as the ‘plex’ user (for those concerned with it running as root). As mentioned previously, I have only tested on DSM6.0 and have not added code to check for Plex PMS installation, Python installation; so these are prerequisites. As usual ‘use at own risk’
Thank you very much for this. I’ve been trying to get Plex monitoring software installed on my Syno for about 2.5 hours and this got it done in seconds. Really appreciate it!!!
Maybe I should clarify that I believe the encryption is hardware specific. I can go into encrypted folders and make modifications. But if the drive is unmounted (by reboot or removing), then the folder has to be remounted again before being accessible.
Is this the path btw that PlexPy saves data? The logs? Or does my PlexPy data save in that dockerconfig folder?
@trumpy81 said:
If you can edit the encyrpted data easily then it should not be an issue. I dislike encryption because of the headache it can cause when not associated with the needed hardware etc. Great for protecting sensitive data, not so great when that hardware breaks and you need to access that data.
Each to their own though …
PlexPy data will save in the dockersconfig/plexpy folder.
The Plex logs location ‘This is required if you enable IP logging (for PMS 0.9.12 and below)’ I’m not sure it’s even used these days, but it doesn’t hurt to add it just in case.
Just can’t lose your keys. Seriously though, trumpy! Thank you! I was miserable searching the web to find out how to do PlexPy. I gave up a couple weeks back and recently revisited it. I know it took you time to write out those detailed instructions, but I am sure others will find it useful. Or maybe I was just a dumb outlier.
Curious if setting up containers for other apps would be the same or a similar process. Do you recommend using docker instead of traditional installing on the synology NAS?
Yes you do need to set the Plex logs path, the path is: volume1/Plex/Library/Application Support/Plex Media Server/Logs
Your guide on this page was amazing, I’ve now got plexpy up and running in a docker and it took 2 minutes!
but I do have a quick question, in this reply what do you mean by setting this? Where would I go to confirm this is set / set it up?
I figured it out right after I posted heh
In some of the sections it was saying “are you sure you’ve added your plex log files?” (or something like that) and it’s no longer saying that, although the info is all still empty since I’ve only just installed it.
It’s such a shame that plex doesn’t keep it’s own fuller history of plays, etc, that plexpy can tap into and then import.
I think everything is all setup correctly now, I’ll have to use plex for a couple days and then see what plexpy is saying!
@trumpy81 said:
As you can see, it takes a whole other program to track that stuff, so adding that to Plex would make it even heavier than it already is.
You could not run Plex and PlexPy on an ARMv5 processor for example, it would bog down quite a bit I would imagine.
Anyhow, Good Luck with PlexPy and Happy Plexing!
So to free up processing resources would it be better to run plexpy on another standalone? Especially since my CPU already stresses with a few stream going?
@trumpy81 said:
If PlexPy is taxing your resources, then yes, it might be worth running PlexPy on your PC for example, you can still link it to PMS on the NAS.
The only downside with that is, if you turn off the PC, PlexPy wont be able to record all of your usage while the PC is off.
That makes sense. I am also thinking I could literally make another Plex account and run a second PMS from my PC and just point to the NAS to access the media? But in this case I’d have to run two separate PlexPy’s to capture the activity of both accounts? Wish there was a way to just aggregate multiple Plex accounts into one PlexPy. I guess this is a situation why one user had multiple Plex’s and PlexPy’s running – to split up the PMS processing / transcoding if one of their machines wasn’t capable. Can always point to the same media and outsource the processing. Sorry for being off topic.
Edit: I’m thinking of moving my processing power altogether off my NAS to an old PC, but keeping PlexPy on my NAS. Would I only have to change the log paths to keep PlexPy running smoothly since the log path would now be on my PC? Everything else on PlexPy should continue to work as is?
Why would my PC PMS have problems playing content compared to my NAS PMS? Isn’t PMS the engine that drives the transcoding? That sounds like a headache altogether – moving PlexPy to my PC – lol. I had a hard enough time trying to get it to work on docker. Maybe the installation on PC is much more straight forward? Maybe I could even run docker on my windows PC and install? I’ll have to find out which is easier.
In regards to potentially migrating to my PC for PMS, I posted here. There you will see my computer specs compared to my NAS. Maybe it would be better to move that discussion over there.
How do you get the Docker PlexPy to mount the Plex logs folder? It’s not showing up in Docker folder mapping. Do you have to run it more manually to mount that folder?
:))
