Okay, so my Plex Server has been saying there is an update for about a month or so now but every time I check the downloads it says the latest version is the same as what I am running. Even the PMS_Updater script I’ve been using for a long while is saying that the version is the same. It’s getting ridiculous as I am seeing that others are updating and when I try to manually update via the link provided via the WEBUI the downloaded files don’t work cause the application won’t even start.
There’s were some changes with the 1.15.x builds but the Updater Script is pointing to the correct URL now I think… At least I do remeber seeing a PR for that.
However you will need no manually update the rc.d script to get PMS to start properly.
I’m not sure what you are talking about.
The updater script points to the right URL but the URL doesn’t give any versions higher then what I am currently running which is 1.14.1.5488… and the plex server is telling me the latest build is 1.15.1.710. Basically the point here is that the URL that scripts use for updating is not giving the same information as the server is.
Also, if updating the version of software wouldn’t it install/update the rc.d script? If not is there a document someplace about these changes? I’ve looked around and can’t find anything detailing what you said.
I am running FreeNAS 11.2 and had to make some changes to PMS_Updater.sh to get it to work, notably the URLBASIC/URLPLEXPASS values. You may have a different PMSLIVEFOLDER if you are on a different version of FreeNAS.
Make sure that you have wget, perl5, and ca_root_nss
pkg install wget perl5 ca_root_nss
Then update the PMS_Updater.sh file.
URLBASIC="https://plex.tv/api/downloads/1.json"
URLPLEXPASS="https://plex.tv/api/downloads/1.json?channel=plexpass"
PMSPARENTPATH="/usr/local/share"
PMSLIVEFOLDER="plexmediaserver"
I was able to update the basic version using the following command.
./PMS_Updater.sh -n -vv -a
1 Like
All great information however still does not explain or answer why the URL in the scripts and via web browser don’t show the updated version of Plex to download and get.
I think for now the url for the plex pass version has changed. It may change back once 1.15 goes to public.
For now If you paste this into a browser with a valid plex token, the json returned shows the latest plexpass version
https://plex.tv/api/downloads/5.json?channel=plexpass&X-Plex-Token=PLEX_TOKEN_HERE
(It does not work without a valid plex token)
1 Like
It seems like a lot of this questions should be asked in the script page, but to try and offer some help, this is a custom script that uses a custom method of upgrading, using it is always at risk of things breaking, you can see there are a lot of other threads about this still failing even after update!
To give a bit more detail, what you see in the web app is a result of using the built-in updater API in pms, and the script uses a different approach, which form what I see is based on inspection of the plex.tv downloads page.
Either way I looked in the script repo and did see a PR to update 1.json to 5.json (I think its already merged actually), so I unless you don’t have it up to date I don’t see why this would still fail.
Also do note that you must update the rc.d script for PMS to even work (there’s a few other posts in the forums about this)
Thanks @mike_pt. Much appreciate the feedback and i am fine if the thread needs to be moved. My biggest concern I guess is over the lack of official documentation about the upgrade. You reference thread in the forums on how to do this but to be honest since the FreeBSD version of Plex is officially supported by Plex should there not be some official documentation regarding the upgrade procedure from 1.14 to 1.15? I get the script is not support by Plex but the distro that I am using is.
We ship a tartball that includes a start.sh script, ofc the official way to install software in a FreeBSD based system is by using the ports/pkgng, which is maintained by the community (or a FreeBSD maintainer actually) which as indeed updated the port (even if not right the next day)
In fact I reached out myself to the port maintainer offering help to fix the port as in a first attempt it was marked broken. The next day it was fixed.
If you’re were using the official OS way and waited for the port/pkg to update you wouldn’t notice any issues, and that’s why such systems exists (and they can still fail but its always best to stick to that if you want things somewhat stable - its still beta).
FYI this is not a FreeBSD specific issue, other systems, especially NASes make things even more complicated, and you might actually have to wait for them to update, especially for beta builds.
I guess what I’m trying to say is that you shouldn’t confuse official support to a platform with official packaging system support (we never state that we directly support pkgng or freenas/iocage plugins) anywhere.
In fact if we did it we could be limiting support to just FreeBSD and a single version… say i.e. we distribute a “FreeBSD 12” txz that you can just “pkg install”… well then what happens to FreeBSD 11, or FreeNAS?
With the tarball we theoretically enable any FreeBSD based system to run Plex (proof is other folks are running it on XigmaNAS.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
