Is there a safe solution to fix this yet?
I am having this issue on Ubuntu
Hi,
This topic is rather specific to rpm (and even to Fedora/RHEL/Alma/Rocky) packages, so it may be better to start another topic for Debian/Ubuntu packaging issues?
Please ping me when you create the new thread.
I ask this because I did the packaging upgrade and it’s all set / switched over to using whatever GPG key it gets from plex.tv.
They key (‘secured-by’ in the repo definition file) is upgraded each time a new version is installed.
I’m not seeing any issues on Ubuntu 20.04 → 23.04
I have moved the posts here so we can continue.
Tags are available in the dropdown.
I’ve placed this in Desktops & Laptops + server-linux.
OK… I think I have found the source of the issue.
Recently I updated openssl on my 5 Ubuntu servers. it looks like the update messed with the config (I noticed a brand new version of openssl, so maybe that is why.)
it was not just plexupdate.sh that was showing this issue… but also anything that uses ‘wget’
fix is detailed in this:
Essential I edits the /etc/wgetrc file to add: ca_directory=/etc/ssl/certs
that fixed the issue.
OK… Immediate issue was fixed. Overall, not fixed.
When I run sudo apt update, I get this:
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://downloads.plex.tv/repo/deb public InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 97203C7B3ADCA79D
W: Failed to fetch https://downloads.plex.tv/repo/deb/dists/public/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 97203C7B3ADCA79D
W: Some index files failed to download. They have been ignored, or old ones used instead.
I cannot replicate your problem.
- OS release 22.04
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
[chuck@glockner sources.list.d.2013]$
- Contents of repo definition after manual install of a DEB package
Notice it is referening the Key file it downloaded itself (apt-key no longer used)
[chuck@glockner sources.list.d.2013]$ cat plexmediaserver.list
# When enabling this repo please remember to add the PlexPublic.Key into the apt setup.
# wget -q https://downloads.plex.tv/plex-keys/PlexSign.key -O - | sudo apt-key add -
deb [arch=amd64 signed-by=/usr/share/keyrings/plexmediaserver.gpg] https://downloads.plex.tv/repo/deb/ public main
[chuck@glockner sources.list.d.2014]$
- I probably should reword / cleanup the repo but Ubuntu 18 systems are still supported and require apt-key support. Ubuntu 20.04 and above do not need or use it.
- apt update without issue
[chuck@glockner sources.list.d.2008]$ sudo apt update
Get:1 https://downloads.plex.tv/repo/deb public InRelease [6,685 B]
Hit:2 https://repo.45drives.com/debian focal InRelease
Get:3 https://downloads.plex.tv/repo/deb public/main amd64 Packages [428 B]
Hit:4 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Get:5 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Get:6 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [108 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [855 kB]
Get:9 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [962 kB]
Fetched 2,160 kB in 1s (1,567 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
- Upgrade without issue (except for typos)
[chuck@glockner sources.list.d.2009]$ sudo apt uprade
E: Invalid operation uprade
[chuck@glockner sources.list.d.2010]$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
gsasl-common imagemagick libjs-jquery-ui libavdevice58 ffmpeg libopenexr25
python3-scipy libpostproc55 libmagickcore-6.q16-6-extra libgsasl7
libavcodec58 libmagickwand-6.q16-6 libavutil56 imagemagick-6.q16 libswscale5
libmagickcore-6.q16-6 libswresample3 imagemagick-6-common libavformat58
libavfilter7
Learn more about Ubuntu Pro at https://ubuntu.com/pro
#
# An OpenSSL vulnerability has recently been fixed with USN-6188-1 & 6119-1:
# CVE-2023-2650: possible DoS translating ASN.1 object identifiers.
# Ensure you have updated the package to its latest version.
#
The following packages will be upgraded:
plexmediaserver
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 76.0 MB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://downloads.plex.tv/repo/deb public/main amd64 plexmediaserver amd64 1.32.5.7349-8f4248874 [76.0 MB]
Fetched 76.0 MB in 1s (82.0 MB/s)
(Reading database ... 182182 files and directories currently installed.)
Preparing to unpack .../plexmediaserver_1.32.5.7349-8f4248874_amd64.deb ...
PlexMediaServer install: Pre-installation Validation.
PlexMediaServer install: Pre-installation Validation complete.
Unpacking plexmediaserver (1.32.5.7349-8f4248874) over (1.32.5.7210-77f7f99fa) ...
Setting up plexmediaserver (1.32.5.7349-8f4248874) ...
PlexMediaServer install: PlexMediaServer-1.32.5.7349-8f4248874 - Installation starting.
PlexMediaServer install:
PlexMediaServer install: Now installing based on:
PlexMediaServer install: Installation Type: Update
PlexMediaServer install: Process Control: systemd
PlexMediaServer install: Plex User: plex
PlexMediaServer install: Plex Group: plex
PlexMediaServer install: Video Group: render
PlexMediaServer install: Metadata Dir: /vol/plexmediaserver
PlexMediaServer install: Temp Directory: /dev/shm (set in Preferences.xml)
PlexMediaServer install: Lang Encoding: en_US.UTF-8
PlexMediaServer install: Processor: Intel(R) Xeon(R) CPU E5-2690 v4 @ 2.60GHz
PlexMediaServer install: Config file used: /etc/systemd/system/plexmediaserver.service.d/override.conf
PlexMediaServer install: Intel i915 Hardware: Not found
PlexMediaServer install: Nvidia GPU card: Found
PlexMediaServer install:
PlexMediaServer install: Completing final configuration.
PlexMediaServer install: INFO: Plex Media Server is not enabled to start at system boot.
PlexMediaServer install: Starting Plex Media Server.
PlexMediaServer install: PlexMediaServer-1.32.5.7349-8f4248874 - Installation successful. Errors: 0, Warnings: 0
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...
Running kernel seems to be up-to-date.
The processor microcode seems to be up-to-date.
Restarting services...
Service restarts being deferred:
systemctl restart NetworkManager.service
systemctl restart wpa_supplicant.service
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
Have you considered just wiping out the signing key and letting the installer do its thing normally?
I did sudo apt-key del 97203C7B3ADCA79D
And then “sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 97203C7B3ADCA79D”
Still getting same error on “sudo apt update”
Don’t add a key manually.
The package adds it for you and does so correctly.
You are using 20.04.6 LTS
Manual key add obsolete.
I followed the instructions here… that seems to have fixed it
sorry, that article needs updating.
- Delete the key
- Delete the repo definition.
- Install the package
– it writes the repo file
– it downloads and installs the key (for Ubuntu 20.04 and above)
As last step,
- Edit /etc/apt/sources.list.d/plexmediaserver.list
- Remove the comment
- sudo apt update
PMS is now ready to upgrade via the repo
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
