GPG check failing on server update or install

When I try updating or installing the newest media server it is giving me this error
“Key import failed (code 2). Failing package is: plexmediaserver-1.25.7.5604-980a13e02.x86_64
GPG Keys are configured as: https://downloads.plex.tv/plex-keys/PlexSign.key
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘yum clean packages’.
Error: GPG check FAILED” (This is specifically on a new server install)

As this is something that I am getting on multiple servers (one Centos stream 8 and one Centos stream 9) is this something that is errored on Plex’s side or am I missing something?

If you’re getting a key import failure, that’s within the host.

The package is signed. All Linux packages use the same key.
If signing were broken, everyone would be broken and they aren’t.

You might best want to remove the key you have installed and reinstall the main Plex signing key again.

I have tried removing the key and now when trying to install it, this is what I get.

Importing GPG key 0x3ADCA79D:
Userid : “Plex Inc.”
Fingerprint: CD66 5CBA 0E2F 88B7 373F 7CB9 9720 3C7B 3ADC A79D
From : https://downloads.plex.tv/plex-keys/PlexSign.key
Is this ok [y/N]: y
Key import failed (code 2). Failing package is: plexmediaserver-1.25.7.5604-980a13e02.x86_64
GPG Keys are configured as: https://downloads.plex.tv/plex-keys/PlexSign.key
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing ‘yum clean packages’.
Error: GPG check FAILED

And If I try to install the key manually here is what I get.

rpm --import https://downloads.plex.tv/plex-keys/PlexSign.key

error: https://downloads.plex.tv/plex-keys/PlexSign.key: key 1 import failed.

Looks like RPM version 4.16.1.3, failure to import some keys · Issue #1977 · rpm-software-management/rpm · GitHub

On Centos Stream 9 rpm --import fails, on Fedora 36 - works.

gpg --list-packets PlexSign.key outputs :signature packet: algo 1 == SHA1. It looks like resigning the key with SHA512 will fix issues

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