Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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!
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.
@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.
This comment has been deleted