Related

Certbot unable to locate virtual host Question Question
Why my website down? SSH cannot be accessed Question Question

Question

The repository 'https://repos.insights.digitalocean.com/apt/do-agent main InRelease' is no longer signed.

Posted March 20, 2020 670 views
Ubuntu 18.04

I can’t update/upgrade. How do I fix this?

root@starfish:~# apt-get update && apt-get upgrade -y
Hit:1 http://mirrors.digitalocean.com/ubuntu bionic InRelease
Err:2 https://repos.insights.digitalocean.com/apt/do-agent main InRelease                               
  400  Bad Request [IP: <SNIP> 443]
Hit:3 http://mirrors.digitalocean.com/ubuntu bionic-updates InRelease                                   
Hit:4 http://mirrors.digitalocean.com/ubuntu bionic-backports InRelease                                 
Get:5 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]                             
Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease                                       
Hit:7 http://ppa.launchpad.net/wordops/nginx-wo/ubuntu bionic InRelease                                 
Get:8 http://mariadb.mirrors.ovh.net/MariaDB/repo/10.3/ubuntu bionic InRelease [6,265 B]                
Reading package lists... Done                      
E: Failed to fetch https://repos.insights.digitalocean.com/apt/do-agent/dists/main/InRelease  400  Bad Request [IP: <SNIP> 443]
E: The repository 'https://repos.insights.digitalocean.com/apt/do-agent main InRelease' is no longer 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.
Add a comment
richpav
By:
richpav
edited by MattIPv4

Related

Certbot unable to locate virtual host Question Question
Why my website down? SSH cannot be accessed Question Question
Add a comment
1 comment

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.

×
Submit an Answer
1 answer
jdsleppy February 4, 2021

@AHA I’m seeing this same error on a nearly brand-new Ubuntu droplet:

# apt-get update
Hit:1 http://security.ubuntu.com/ubuntu focal-security InRelease                                                               
Get:2 https://repos.insights.digitalocean.com/apt/do-agent main InRelease [5132 B]                                             
Get:3 http://mirrors.digitalocean.com/ubuntu focal InRelease [265 kB]                   
Hit:4 http://mirrors.digitalocean.com/ubuntu focal-updates InRelease
Hit:5 http://mirrors.digitalocean.com/ubuntu focal-backports InRelease
Err:2 https://repos.insights.digitalocean.com/apt/do-agent main InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DE88104AA4C6383F
Reading package lists... Done
W: GPG error: https://repos.insights.digitalocean.com/apt/do-agent main InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY DE88104AA4C6383F
E: The repository 'https://repos.insights.digitalocean.com/apt/do-agent main InRelease' 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.

Is there a known fix? I can just try a new droplet if not.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help