Invalid signature when trying to update packages [Debian] - Focal thread

Hello,

I also just started to get GPG update errors when trying to update apt via apt. I can see that there is a workaround in this thread for downloading the latest DEB package, but is it possible to get the key/signature issue fixed?

sudo apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu eoan InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu eoan-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu eoan-backports InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu eoan-security InRelease
Ign:5 https://downloads.plex.tv/repo/deb public InRelease
Get:6 https://downloads.plex.tv/repo/deb public Release [5,815 B]
Get:7 https://downloads.plex.tv/repo/deb public Release.gpg [821 B]
Ign:7 https://downloads.plex.tv/repo/deb public Release.gpg
Reading package lists... Done
W: GPG error: https://downloads.plex.tv/repo/deb public Release: The following signatures were invalid: BADSIG 97203C7B3ADCA79D Plex Inc.
E: The repository 'https://downloads.plex.tv/repo/deb public Release' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
1 Like

To all reading here:

Operations is aware of the issue.

There is no need to continue posting “Broke here too”.

If the condition persists after it’s been repaired _then please let us know.

Thanks.

1 Like

Ah OK, my apologies, I had misinterpreted some of the messages above with the DEB as indicating that people believed the issue was fixed.

This is an enduring thread. It contains history of past events.

Your interpretation presents a very valid point. I will discuss it with the forum admin about archiving this thread after events are resolved.

No need to reboot…

Hi there,
Issue seems fixed in UK as of this morning…

yes same in FR, fixed !

ALL: The team reports it’s fixed.

The team injected additional logic to perform the extended verification at the end points. It seems that presenting the files at the API inlet aren’t always enough for the cloud provider (<shrug>) .

2 Likes

1.8.5 and it’s new install process went smoothly over top of 1.8.4 via repository. :+1:

My win10 mirror server loads betas, my Ubuntu runs public off of the repository.

Its happening again, I manually updated to the latest version but wanted to let the devs know.

reported about 90 minutes ago

1 Like

Interestingly I updated just fine from the repo last night. Is this something that’s happened recently?

Is it still not working?

If so, may I have the geo location (region) so I may report it again?
Operations informs me it is working for them.

Last night I updated, and it worked fine opted not upgrading since many users where using plex last night. To my surprise its not working again this morning.

I Authored this thread here. https://forums.plex.tv/c/plex-media-server which you can close since I thought old threads where not brought back to life.

Trying to update to 1.19.1.2630 on Ubuntu Bionic Beaver (18.04.4 LTS) and getting this error. Tried the manual Sig update listed in This Topic to no avail.:

Err4: https://downloads.plex.tv/repo/deb public Release.org
The following signatures were invalid: BADSIG 97203C7B3ADCA79D Plex Inc.



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/dev public Release: The following signatures were invalid BADSIG 97203C7B3ADCA79D Plex Inc.
W: Failed to fetch https://downloads.plex.tv/repo/deb/dists/public/Release.gpg
The following signatures were invalid: BADSIG 97203C7B3ADCA79D Plex Inc.
W: Some index files failed to download. They have been ignored, or old ones used instead.

Note, I just update to version 1.18.9.2578 just last week absolutely fine, after following the instructions to Enable repository updating for supported Linux server distributions. I went to update this morning after seeing the update avail last night (but plex in use) and this morning it is reporting bad sig.

US Eastern cluster

Thanks @mikerod

I’ll let them know to verify Eastern US.

1 Like

Ok… Let’s take the sleigh for another ride. :rofl:

They’re talking about giving some serious love to the deployer.
This is getting seriously old.

For other threads abuout this topic, please make a post there which links to here, mark the post as “solution” and the forum will auto close.

1 Like

No errors on the apt update now so fingers crossed…

And I was successfully able to update to 1.19.1.2630 now.

Me thinks maybe the devs should check for an expiry on their signatures?

If I see any other topics on this, I will link it here as the solution.

Thanks Chuck!

It’s the deployer.

If you were to see the steps performed, it would make perfect sense.
They have to go through all the different sites. Best I can share is: “It doesn’t handle retries gracefully” .

2 Likes

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