Question

NO_PUBKEY D8FF8E1F7DF8B07E

When I try to

$apt update ~~

Get:1 https://repos.influxdata.com/debian stable InRelease [6874 B]

Hit:2 http://mirrors.digitalocean.com/ubuntu jammy InRelease

Get:3 http://mirrors.digitalocean.com/ubuntu jammy-updates InRelease [119 kB]

Get:4 http://mirrors.digitalocean.com/ubuntu jammy-backports InRelease [107 kB]

Err:1 https://repos.influxdata.com/debian stable InRelease

The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E

Hit:5 https://repos-droplet.digitalocean.com/apt/droplet-agent main InRelease

Get:6 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]

Get:7 http://mirrors.digitalocean.com/ubuntu jammy-updates/main amd64 Packages [898 kB]

Fetched 1241 kB in 6s (211 kB/s)

Reading package lists… Done

Building dependency tree… Done

Reading state information… Done

72 packages can be upgraded. Run ‘apt list --upgradable’ to see them.

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian stable InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E

W: Failed to fetch https://repos.influxdata.com/debian/dists/stable/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E

W: Some index files failed to download. They have been ignored, or old ones used instead.

I tried this https://www.digitalocean.com/community/questions/how-to-fix-no_pubkey-77b79b3ffaf7ef65?comment=192177

wget -qO - https://repos.insights.digitalocean.com/sonar-agent.asc | sudo apt-key add -

But not work.

Does anyone have a solution for ubuntu 22.04


Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

KFSys
Site Moderator
Site Moderator badge
February 26, 2023
Accepted Answer

Hey @jul1o,

You seem to be using old keys. You can check the following article on how to fix your issues:

https://www.influxdata.com/blog/linux-package-signing-key-rotation/

Basically, you have to do the following:

  1. Obtain and verify the new key:
  1. wget -q https://repos.influxdata.com/influxdata-archive_compat.key
gpg --with-fingerprint --show-keys ./influxdata-archive_compat.key
  1. Install the new key:

    $ cat influxdata-archive_compat.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg > /dev/null
    
  2. Update your APT sources to use the new key:

    $ echo 'deb [signed-by=/etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg] https://repos.influxdata.com/debian stable main' | sudo tee /etc/apt/sources.list.d/influxdata.list
    
  3. Cleanup the old key:

    $ sudo rm -f /etc/apt/trusted.gpg.d/influxdb.gpg
    
  4. Confirm that sudo apt-get update returns no errors for https://repos.influxdata.com

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel