I see the other thread has removed the links from the last post, and suggests using the downloads page.
But the downloads page is still showing me the 1.14 links and nothing I try seems to resolve it.
Tried multiple browsers, platforms and locations. Cleared cache multiple times and tried private/incognito windows
Same issue guys. Still 1.14.
@zack123, @wjbridge any chance if could you let us know if the downloads page is working for you yet?
Just checked, down for me too.
Im still seeing 1.14 as well
Cleared the cache for my browser and it is still showing 1.14 for me too
May I have tracerouts?
I need to see which one of the world’s servers you are hitting.
Obviously something is hung somewhere. Once we know which one it is, we can beat on it 
Using plexupdate.sh on linux.
Fetching token from Plex server
Retrieving list of available distributions
RELEASE="label":"Ubuntu 64-bit (14.04 or newer)","build":"linux-ubuntu-x86_64","distro":"ubuntu","url":"https://downloads.plex.tv/plex-media-server/1.14.1.5488-cc260c476/plexmediaserver_1.14.1.5488-cc260c476_amd64.deb","checksum":"1bd274026c4d7038ec57bad7c3735ce47f73b887"
DOWNLOAD=https://downloads.plex.tv/plex-media-server/1.14.1.5488-cc260c476/plexmediaserver_1.14.1.5488-cc260c476_amd64.deb
CHECKSUM=1bd274026c4d7038ec57bad7c3735ce47f73b887
INSTALLED_VERSION=1.14.1.5488-cc260c476
FILE_VERSION=1.14.1.5488-cc260c476
Your OS reports the latest version of Plex (1.14.1.5488-cc260c476) is already installed. Use -f to force download.
It’s hitting download.plex.tv which is resolving to:
downloads.plex.tv.cdn.cloudflare.net. 299 IN A 104.18.156.41
downloads.plex.tv.cdn.cloudflare.net. 299 IN A 104.18.157.41
Here’s a mostly-full traceroute (before pings get swallowed up by the AWS routing black hole):
And here’s what www.plex.tv is resolving to in DNS:
~$ dig www.plex.tv
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59907
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; ANSWER SECTION:
www.plex.tv. 60 IN CNAME www.plex.tv.cdn.cloudflare.net.
www.plex.tv.cdn.cloudflare.net. 107 IN CNAME plex4.wpengine.com.
plex4.wpengine.com. 120 IN CNAME lbmaster-95114.wpengine.com.
lbmaster-95114.wpengine.com. 120 IN CNAME cluster95-elbwpeel-1rcyft0q3nddc-1014054933.us-east-1.elb.amazonaws.com.
cluster95-elbwpeel-1rcyft0q3nddc-1014054933.us-east-1.elb.amazonaws.com. 60 IN A 52.4.180.28
cluster95-elbwpeel-1rcyft0q3nddc-1014054933.us-east-1.elb.amazonaws.com. 60 IN A 34.202.207.128
So it looks like I should be hitting AWS directly without Cloudflare stepping in.
@usnhobbz That’s only for the actual file download. The relevant endpoint for getting the version information in plexupdate is https://plex.tv/api/downloads/1.json.
Ah, well in that case:
;; ANSWER SECTION:
plex.tv. 20 IN A 54.171.147.115
plex.tv. 20 IN A 54.76.255.232
plex.tv. 20 IN A 54.171.218.244
plex.tv. 20 IN A 52.31.211.151
plex.tv. 20 IN A 54.154.198.3
plex.tv. 20 IN A 63.32.177.143
plex.tv. 20 IN A 52.16.101.236
plex.tv. 20 IN A 54.171.5.253
I am pinging both the operations and the content teams again.
One manages the servers, the other is responsible for the content (JSON)
As I understand it (waiting confirmation) the web page is on AWS. The downloads come via cloudflare. How that works. 
We are still working on a fix required for our website that talks to the downloads API (the json endpoint)
In the mean time, if you have scripts that look for plexpass downloads via https://plex.tv/api/downloads/1.json?channel=plexpass you can simply use https://plex.tv/api/downloads/5.json?channel=plexpass instead. (be sure to provide your Plex Token in the header for the request, or as a parameter in the request)
the api seems to specify every build as ubuntu right now. 
That API shows all downloads for a particular release. If you are wanting to query the plex.tv API for the latest beta download for a particular platform you will need to use the same API that PMS uses
https://plex.tv/downloads/latest/5?channel=8&build=linux-x86_64&distro=debian&X-Plex-Token=
channel=8 = beta
build=linux-x86_64 = architecture
distro=debian = platform
I can confirm changing to 5.json and adding the auth header is returning the right value. What is the difference between 5.json and 1.json? Should we be making this a perm change in the update process or wait for the 1.json to start returning the right values?
1.json is the old CI/build system (PMS 1.14.1 and older), 5.json is the new CI/build system (1.15.0 and newer)
Currently we have plex.tv mapping from 1.json to 5.json to allow as little disruption. Once we get PMS 1.15.0 into public then that will be the endpoint to use going forward (1.json will live on only as a redirect to 5.json)
most excellent information. Thanks for pointing us in the right direction
in the past, i would target my query to build vs distro to distinguish from 32 vs. 64 bit and deb vs rpm. now, under releases, even releases with distro value of redhat have a build value of “linux-ubuntu-x86_64” has it always been like this?
