Server Version#:PlexMediaServer-1.15.0.659-9311f93fd
I just updated to this plexpass version on my freenas server and now I don’t have access to the server settings and it won’t retrieve show or episode data.
I clicked on fix match and the select agent just says “loading.”
Any one else having this issue? Have a fix?
Edit: Reverting to previous version PlexMediaServer-1.14.1.5488-cc260c476-freebsd-amd64 has restored access to server settings and matching works again.
Happens to me too - i have 2 plex servers - 1 plexpass and one regular.
If I force the new version onto the non-plexpass server, same thing happens - have to revert to the 1.14 version to fix it
Same happened to me on freenas
Same for me on freenas 11.2
I am in the same boat, I only realized it because I added a new to PMS show, and it is not pulling any meta data. I then went to fix it and I had no selections to pull it from, and then went to settings and realized that EVERYTHING under Settings header yields a “Server settings are unavailable” running on an Alienware SteamMachine running SteamOS (which is Debian Jessie based). I also redownloaded and reinstalled 1.15.0.659-9311f93fd amd64 deb, and I ran this suggestion https://support.plex.tv/articles/204281528-why-am-i-locked-out-of-server-settings-and-how-do-i-get-in/?_ga=2.34659105.1017903758.1550512994-665605848.1539640697 first. Neither helped.
Unfortunately us BSD folks are now at the mercy of the port/pkg maintainer as PLEX devs decided to change some of the background stuff. The update script will no longer work and you can’t just replace the binaries anymore.
Advanced users can create a new build by following this post:
The rest will have to wait for the plexpass pkg to update.
I used the update script to upgrade and revert back. But I had to stop Plex first or it would get stuck at that part.
Well to be fair this was always the case. But you’re also making a few wrong assumptions here:
1st at any given time something can change that will make un-official tools/script stop working, this IS the risk of using them.
2nd the script is on github anyone can help and submit PRs to fix it (seems like some folks are already doing it)
3rd You can still replace the binaries, no one said you can’t… you own you’re on system if yo want to do it that way its up to you… (I did say in a previous post that this wasn’t the official way to update, perhaps you took it as you can no longer do that, but that’s not true)
I would also like to note that this changes are in the works for some time now, and make things better for the future (See: Much faster (hopefully), smaller (mostly) and better PMS builds preview (1.15.0.573-123756e9a)) so the maintainers of the port/pkg or script had time to update (and still due, remember: this is BETA), and it would be very unfair to criticize them to take a bit longer, especially the UpdaterScript maintainer… he took his own time to provide this tool for free and shared its code, It doesn’t seem fair to ask much more than that.
I do think that when we have a public build, both the script and ports/freenas plugin will get updated (the later simply depends on the port update anyway), maybe even before that, this as been the case in the past and even if it does take a bit longer, I still think we should be thankful for it.
Now with all that said, and without promising anything I do know its being discussed that we could perhaps (special now with the new system) provide a more direct way of updating on freebsd (like with do for other systems, i.e. with linux .deb/.rpm etc that allow u to install directly). Right now we provide the tarball that is used in the port, but this can’t be installed directly with a simple command, perhaps we could take ownership of the port it self, or something of the sort. I personally would like to see that happen but as I said can’t really promise anything as so far this was simply up for discussion, so It might never happen, but 
Yeah. That my last post came off a little strong and my main issue is really the port maintainer. Maybe he has too much to do but even the public release port took weeks to update, often there was a new version by the time he got the last one up. I got sick of waiting and searched for another option which was build it yourself (not feasible for 99% of people) or use the script.
EDIT: On the subject of BETA, what’s the point of maintaining a plexpass port if you don’t port the BETAs in a timely manner as well? (Kinda rhetorical ranting)
EDIT2: The script will always be broken going forward. I dug through the code and it’s sole purpose was grabbing the latest binaries, moving the old binaries to backup folder and unpacking the new ones in their place. It does nothing else besides logging what it did.
Hum you know looking at it (quickly) it shouldn’t be that broken… if it just doesn’t that than it seems you could just use it and then update the rc.d script (which should then work for future 1.15.+++ updates… ) we made a few changes to how we detect if the system is freebsd or freenas, but the most important one is the LD_LIBRARY_PATH so just updating that should work!
Another thing is that eventually it will need to update the url it uses to check if there are updates
I mean, it could be modified to run some sort of post-install script that ensures any changes are made that need to be done. That might be a route you guys could take, maintaining a version of the script packed in with your binaries.
EDIT: It would definitely make a lot of FreeNAS users happy. Between the BSD port and the “official” plug-in, we have always been left in the dust when it comes to plex updates.
I’m running version 1.15.0.659 without issue. If you are using PMS_Updater.sh to perform the update it does not take into consideration any changes to the file structure. With 1.15.0.659, libraries were moved to ‘/usr/local/share/plexmediaserver-plexpass/lib’ from ‘/usr/local/share/plexmediaserver-plexpass’. As a result, the ‘plexmediaserver_plexpass’ config file located at ‘/usr/local/etc/rc.d’ which is used to start the PMS service does not have a matching file structure. Editing the config file as follows allows Plex to start as normal.
Change from:
export LD_LIBRARY_PATH=“/usr/local/lib/compat:${SCRIPTPATH}”
To:
export LD_LIBRARY_PATH=“/usr/local/lib/compat:${SCRIPTPATH}/lib”
This of course is less than ideal and should be addressed with the next iteration of the port.
As @mikec_pt told you in another post, that alone is not enough for proper operations. I used a version of his build files I modified to port the new version properly but that isn’t doable for the average user.
Should work to get it to run, its the critical part at least cause we changed the library path (all systems should now use the same btw which makes thing simpler to maintain)
But let me post here the diff with the full rc.d changes
--- plexmediaserver.in.orig 2018-08-14 16:28:39.300158000 +0100
+++ plexmediaserver.in.new 2019-02-14 22:14:38.537119000 +0000
@@ -40,11 +40,24 @@
plex_precmd()
{
+ # Set identification variables for FreeNAS; with fallback to FreeBSD
+ if [ -f "/etc/version" ]; then
+ export PLEX_MEDIA_SERVER_INFO_VENDOR="$(cat /etc/version|cut -d- -f1)"
+ export PLEX_MEDIA_SERVER_INFO_DEVICE=NAS
+ export PLEX_MEDIA_SERVER_INFO_MODEL="$(uname -m)"
+ export PLEX_MEDIA_SERVER_INFO_PLATFORM_VERSION="$(cat /etc/version|cut -d- -f2-)"
+ else
+ export PLEX_MEDIA_SERVER_INFO_VENDOR=FreeBSD
+ export PLEX_MEDIA_SERVER_INFO_DEVICE=PC
+ export PLEX_MEDIA_SERVER_INFO_MODEL="$(uname -m)"
+ export PLEX_MEDIA_SERVER_INFO_PLATFORM_VERSION="$(uname -r)"
+ fi
+
export SUPPORT_PATH="${%%PORTNAME%%_support_path}"
export HOME="${%%PORTNAME%%_support_path}/Plex Media Server"
export PYTHONHOME="%%DATADIR%%/Resources/Python"
export SCRIPTPATH="%%DATADIR%%"
- export LD_LIBRARY_PATH="%%PREFIX%%/lib/compat:${SCRIPTPATH}"
+ export LD_LIBRARY_PATH="${SCRIPTPATH}/lib"
export PLEX_MEDIA_SERVER_HOME="${SCRIPTPATH}"
export PLEX_MEDIA_SERVER_MAX_PLUGIN_PROCS=${%%PORTNAME%%_maxplugins}
export PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR=${%%PORTNAME%%_support_path}
That first part is for better system identification, we run into problems before because a few things were different on freenas, and it will help in the PMS log cause its easier to identify its actually FreeNAS not plain FreeBSD (XigmaNAS user might want to change that btw) but the core functionality should work fine if LD_LIBRARY_PATH is set correctly (LD_LIBRARY_PATH="${SCRIPTPATH}/lib") note that we no longer need /usr/local/lib/compat its another advantage of the new builds.
So tl;dr is make sure you update the rc.d script to reflect this, and it seems you can continue to use that script in future updates.
Thanks for the update, Mike!
Hi Mike, I’m a total noob with all this (FreeBSD). I somehow managed to install 1.15.1.707-d893009fb on FreeNAS. I can play movies and all that, but I cannot access the server settings.
I understand I need to change some paths and directories and so forth, but I honestly cannot do it with my skill level. I tried to roll-back but I cannot even find a link to download an old version.
I’d like to keep the new version if possible. Is there a way I can learn to do the above fix myself or something?
Thanks,
C
Is this thread for freenas/freebsd only? I am having this issue on a windows 10 install.
Weird - I go to /etc/rc.d and there is no plexmediaserver entry in there for my freenas jail. Am I missing something here?
I, too, have the same issues as above.
B
OK - I updated the file in /usr/local/etc/rc.d (plexmediaserver) with the changed stated above. Stopped and started the server. No change in our issues - still no access to server settings and cannot get media to hit their agents to update covers, etc.
B
