Server update Channel 'unknown'

Plex Media Server Remote Access
,
1

Server Version#: 1.28.2.6151
Player Version#: 4.87.2
Operating System: Ubuntu 22.04.1 LTS (configured as a headless server)

I am unable to claim the server on this machine. I am prompted to update in Settings > General, where the version is read out as Version 1.28.2.6151 (!)An update is available. Please install manually. (This link leads me to the same version I am running, since I am running the current version. I have tried downloading and running it again, and when the Settings page refreshes it says the same message)

I notice that the Server update Channel dropdown on the same Settings > General page only has the option ‘unknown’ to select, where I am used to seeing ‘Public’ on my other machines running Plex servers. This is a fresh install of the Ubuntu Server and a fresh install of Plex; I am not upgrading this from a previous version that had worked.

However, I do currently run Plex servers on a few other machines, all with GUIs: Ubuntu 20.04 and Ubuntu 22.04, as well as Windows 10. All three of these other Plex servers are working fine, I am able to claim their servers and their Server update Channel dropdowns only offer ‘Public’ as an option. Their Version-update-prompt readouts are as expected: Version 1.28.2.6151 Check for Updates Up to date

In order to install PMS on the headless server I used the following commands:
wget https://downloads.plex.tv/plex-media-server-new/1.28.2.6151-914ddd2b3/debian/plexmediaserver_1.28.2.6151-914ddd2b3_amd64.deb
-(this command downloaded the package)
sudo dpkg -i plexmediaserver_1.28.2.6151-914ddd2b3_amd64.deb
-(this command installed the package)

I noticed one other anomaly, in the readout of running the dpkg commands between the Ubuntu 22.04 headless and both the Ubuntu 22.04 and Ubuntu 20.04 GUI systems, which says “Video Group: render” (headless) compared to “Video Group: video” (GUI).

This is my first time running a headless server machine at all, which makes me wonder if that has something to do with it? Perhaps some kind of configuration or hardware oversight is leading to this problem?

Hardware reference, the Windows 10 and Ubuntu 20.04 GUI Plex servers are on a dual-boot running on a desktop machine, Intel 11600K with a 1080ti GPU. The Ubuntu 22.04 GUI Plex server is running on a laptop machine, AMD Phenom II P960 (circa 2010) with integrated graphics. The Ubuntu 22.04 headless Plex server is running on a desktop machine, Intel 8700K with integrated graphics.

Any suggestions would be appreciated. Please let me know!

2

I was able to solve this issue. What I had done, after installing the Ubuntu Server, was edit my /etc/netplan/*.yaml file to assign my network card an ip address. In this way I was able to remotely access the server with an ip of my choosing. For posterity’s sake I will post here the steps I took that complicated Plex:
Old .yaml file:
network:
ethernets:
enp2s0:
dhcp4: true
version: 2

Updated .yaml file:
network:
version: 2
renderer: networkd
ethernets:
enp2s0:
dhcp4: no
dhcp6: no
addresses: [x.x.x.x/x] (here I actually entered the ip I wanted to use)
routes:
- to: default
via: x.x.x.x (here I actually entered the ip I wanted to use)

After reverting these changes back to the old .yaml file and running sudo netplan apply I was able to remove Plex and reinstall. My server update channel is Public, I am not perpetually prompted to update, I am able to claim my server, and I am able to see it on my network and over the internet. All’s well that ends well.

This is, after all, my first headless server, so I’m leaning towards I didn’t properly reconfigure my network card’s ip address in that attempt.

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.