When I log in to my Plex server on the web, I get a banner saying a Plex Media Server update (1.14.1.5488) is available for the server. If I click to download that, and then upload the resulting file to my Plex server and do a dpkg -i, it says I can’t because it’s a i686 package not i386.
When I try to do an apt upgrade on the server, it says everything’s up to date, but the Web UI says I’ve got 1.14.0.5470.
which update channel are you using for your Plex Media server?
Plex Media Server 1.14.1.5488 is the latest public release available to all Plex users
Plex Media Server 1.15.1.710 is the latest update for Plex Pass members using the beta update channel
The linux repo is only available for public releases – however occasionally it’s slightly behind or takes a little longer to be updated… that’s probably why it considers 1.14.0.5470 to be up-to-date
As for the manual update… did you run dpkg -i with admin permission / sudo?
If the update is properly applied, app.plex.tv/desktop > settings > server > general should show the version you’re running.
You’re not by chance running multiple servers with one still being on 1.14.0?
Thanks - how do I tell what channel I’m using? I’ve not got multiple servers.
I’ve just logged in to the web UI and now it says I’m on Version 1.15.1.710! So was it some kind of cache issue? It sure took a long time to display that!
So have I now got a separate problem? I’ve manually installed the 1.15 package but my repo is using the 1.14…?
This also doesn’t explain why the web UI said I had an update pending when apt upgrade on the server disagreed. All this seems really odd to me.
(As an aside, Plex seems to assume that the default setup is to have it running on the same machine as client. At least, I assume that’s why it would make a .deb file for the wrong platform downloadable from the web UI. Am I really in the minority treating the Plex “server” as an actual server on a separate machine? )
Using the web client (which is served to your browser by the server), you can manage both some web client settings as well as the server settings (if you’re the owner of the server).
(As the web client is served by the server, their lifecycles are connected; you only can get a newer web client by upgrading the server).
So just to clarify that there is no assumption being made at all that the server is on the same machine as the client. It’s just that the web client is also the server admin console.
OK thanks. It’s a minor point perhaps, but I assume the reason the web UI gave me the i686 .deb to download was because the machine I was viewing the admin console with was i686. But the server is in fact i386. And that’s a separate issue from the fact that it told me I had an update when apt on the server said I didn’t.
Can’t say anything from experience here, as I’m running the server on Windows.
With my setup I simply use the warning in the web UI to trigger me to update the plex server manually on the server machine (automatic updates from the web ui don’t work for me; has to do with me wanting to run the plex server processes as a windows service).
No… this is the exact same thing
Plex Web checks for Plex updates directly with Plex and will display a banner if the selected update channel has a newer version than the one you installed.
This function is completely ignoring the fact that you use the apt repository to automatically update.
You can see which update channel Plex is checking under Settings > Server > General > Server update Channel. The available options should be Public or Beta – referring to my original response.
Please keep an eye on this and let me know if you keep getting offered the download for the wrong platform. This usually works based on the platform the server is running – at least I’m not aware of any issues.
That’s about the oddest part. Let’s consider it some hiccup. Once the manual update is completed, Plex usually takes a moment to restart the server but from the moment it’s up-and-running again, it should show the correct server version in Settings > Server > General.
)
