Just as a heads up. I am still unable to get the correct release from the webpage/json.
I would recommend another full browser cache flush. I needed to do it a few times to clear out all the remnants of the previous due to the various tweaks throughout the day.
I am now properly showing the new files and display strings.
I have tried multiple browsers (incognito) as well as using curl
to pull the json directly. All still show 1.14.
Edit: After trying multiple times in incognito it loaded the proper release. It seems to be inconsistent.
Downloaded 1.15.0.647-67e950f12.x86_64.rpm (Fedora 64 bit.) few days ago and it has broken dependencies:
# dnf upgrade plexmediaserver-1.15.0.647-67e950f12.x86_64.rpm
Last metadata expiration check: 1:51:13 ago on Fri 08 Feb 2019 05:03:01 PM CET.
Dependencies resolved.
Problem: cannot install the best update candidate for package plexmediaserver-1.14.1.5488-cc260c476.x86_64
- nothing provides config(plexmediaserver) = 1.15.0.647-67e950f12 needed by plexmediaserver-1.15.0.647-67e950f12.x86_64
sha1 sum of the rpm file:
759b8d032e16fdeaf21b3cedf3b84df1dfb7d96f
The previously downloaded (a few days) ago had a problem with the Provides: clause in the spec. It has seen been fixed.
Oh i see. Version 1.15.0.659 is ok now.
btw guys… i had no problem to download the actual version using link provided by Plex Server in settings (version check).
Thanks for that info.
Aren’t you glad we’re doing this here, in PlexPass and not on Public?
The download page is still showing 1.14 on all of my test machines, both in the page itself and in the raw JSON feed. Tried 3 different browsers on each of 3 different machines with incognito mode and the same results each time. We’ve also had a few people post issues in plexupdate about this because they’re seeing it as well. (I’m one of the maintainers.)
Is it possible that it’s related to the account being used to do the check perhaps?
fwiw (i could be wrong) to me the problem appears to be in plex tv web api, as the json that it returns is still showing the old 1.14 links.
If I use curl directly to request the link it still shows the 1.14 versions.
(I am including all the headers, plex token etc in my curl request)
I have tried this from 3 machines, in the UK, Netherlands and Germany and still get the same result on all machines.
Sign out of your plex.tv account from the Plex.tv web site.
Then sign back in.
If this fails, repeat in Plex/Web.
If still no success, we will need see if it is regional server issue.
tried those 2 options, logged out from plex.tv and app.plex.tv then logged back in, no dice, still the same 1.14.
and tried my curl command again from the same 3 Countries, 1.14 returned in the json
I am seeing the same problem still. The plex tv web api is still showing 1.14 versions. When I try to download the Linux verison on the website, still is showing 1.14. Cleared cache for my browser and resigned in/out but still showing 1.14 versions.
which regions of the world please? (e.g. Western US, Eastern Europe, SE Asia, etc)
Eastern United States. The weird part is that my server is detecting an update but the web api and download link still say 1.14. I guess they are not getting the info from the same source?
None of the triggers are fully in sync yet. This was announced somewhere. It’s because deployment for PlexPass comes from the new site now. Deployment for Public from the old site.
Sorry for asking the same question probably…what site should we be using for checking if updates are released? Currently, my script is using ‘https://plex.tv/api/downloads/1.json?channel=plexpass’
I also just tried again to update via Docker, got the same 404 error in the logs. I also tried on another computer with a different browser on the downloads page, which still shows only 1.14 for all systems for me (Plex Pass was toggled on).
If it helps, I am in Switzerland.
They changed the channel names and numbers.
That’s why things are whacked out.
Sorry… but I only work here.
May we pick this up on Monday?
Aye, it is weekend. Not to worry.
Same here. Enjoy your weekend!