Is Ubuntu 20.04 LTS no longer supported?

I’m getting the following The repository ... no longer has a Release file. error on many of my Ubuntu 20.04 LTS droplets. Is this OS no longer supported? If it is supported, how do I resolve this?

I can happily edit /etc/apt/sources.list to whatever it needs to be… but I’ve never had to do this with within-5-years-released Ubuntu LTS versions before.

With regards to the Certificate verification failed: error: this does -not- solve my problem (I already had ca-certificates package installed): sudo apt install ca-certificates … as per:

$ apt update
Ign:1 main InRelease
Err:2 main Release
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 443]
Hit:3 focal-security InRelease
Get:4 focal InRelease [265 kB]
Hit:5 main InRelease
Hit:6 focal-updates InRelease
Hit:7 focal-backports InRelease
Reading package lists... Done
E: The repository ' main Release' no longer has a Release file.
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.
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.5 LTS
Release:	20.04
Codename:	focal
$ date
Wed Mar  8 23:59:20 CST 2023

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.

Site Moderator
Site Moderator badge
March 9, 2023

Hey @johnnyutahh,

Ubuntu 20.04 LTS is still supported however, I’ll recommend upgrading to Ubuntu 22.04 LTS.

As for the error you are receiving, you can just disable the repository if you don’t need it from your /etc/apt/sources.list file.

Additionally, you can try running the following

  1. sudo dpkg --configure -a
  2. sudo apt-get remove droplet-agent
  3. sudo rm /etc/apt/sources.list.d/droplet-agent.list
  4. sudo apt-get update
  5. wget -qO- | sudo bash

It appears I’m forced to install the DigitalOcean “metrics agent” – something I never installed and do not want – on my system in order to fix this with curl -sSL | sudo bash. (“Uninstalling” with apt-get purge do-agent did not solve my problem.) Details:

So to be clear: something I do not want and never installed on my system is causing Ubuntu-apt-update errors. Now I’m forced to update all my automated deployment scripts only to accomodate this DO strangeness.

Is there some other way for me to interpret this? If so, what can be done to avoid this problem in the future?

For now: This is unacceptable. The previously-stellar-DO reputation has lost it’s “luster” with me. If this is what DO has become, I no longer want to be a customer and plan to move to another hosting service as soon as I can.

With regards to the Certificate verification failed: error:

The following solution below does -not- solve my problem. (I already had ca-certificates package installed.)

sudo apt install ca-certificates

The above is an excerpt from:

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