Methods to fix Repository does not have a release file error

Repository does not have a release file⇒ Fix Error in Ubuntu

Repository does not have a release file” error occurs when the package manager can’t find the repository’s package information.

This error can prevent you from successfully installing or updating software on your Ubuntu system.

Common causes are:

  • Typos in repository URLs.
  • Outdated repositories.
  • Missing “Release” files.

To solve this error, you need to consider the below solutions:

  • Verify the URL again: Repository URL typos are frequently the source of problems. Check the source list carefully for any errors.
  • Compatibility Is Important: Make sure the repository is appropriate for the version of Ubuntu you are using. Packages in outdated repositories might not be compatible.
  • Eliminate the Culprit: Just delete the repository’s entry from your list of sources if it is incompatible or unnecessary.
  • Examine servers for archives: Certain repositories may be saved for older Ubuntu versions. For alternatives, visit
  • Update After Fixing: To update the package lists and make your modifications visible use sudo apt update after resolving the issue.


To let this tutorial work correctly, provide the options below and move on.

A Server running Ubuntu VPS.

A non-root user with sudo privileges.

Fixing “repository does not have a release file” Ubuntu Error

This error message is usually displayed in the following format when the sudo apt-get update command is executed to update the Ubuntu system and the software packages available in the repositories:

E: The repository ' bionic Release' does not have 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.

As a result, through the URL displayed along with the error, you can identify the repository that caused the problem and solve your problem faster. Try the provided solutions to prevent getting the “repository does not have a release file” error.

1. Checking the Repository Compatibility with your Ubuntu version

Installing and using PPA (third-party repositories) is one of the common ways to install specific software that is not supported by the official Ubuntu repository. Sometimes, the unavailability or incompatibility of the PPA repository with the version of Ubuntu you are using leads to the display of “the repository no longer has a release file” error. To avoid this problem, before installing the PPA repository, check whether the desired PPA repository is available for your version of Ubuntu. In the following, we will explain how to check Repository Compatibility.

Each version of Ubuntu has a unique code name you can find out about the code name and your current version of Ubuntu by running the following command:

lsb_release -a

Sample Output:

No LSB modules are available.
Distributor ID:    Ubuntu
Description:        Ubuntu 20.04 LTS
Release:               20.04
Codename:        focal

In the output you receive after running the previous command, the Codename section displays the codename of your Ubuntu version.

After knowing the code name of the Ubuntu version, check the web page of the desired PPA repository that you intended to install; from the “Overview of published packages” section on the website related to the PPA repository and filter your Ubuntu code name, Check the PPA repository support for your Ubuntu version’s codename.

This step that we explained should be done before installing the PPA repositories, but if you have installed PPA without checking the compatibility of the PPA repository with the Ubuntu version and you encounter problems when updating or installing the software, you should check the availability of the problematic third-party PPA repository specified in the error content for the version of Ubuntu you are using.

If, after checking, you find that the PPA repository does not support the Ubuntu codename, removing the problematic PPA repository is the solution to your problem. Follow the steps below to remove the problematic PPA repository from your Ubuntu system:

Removing problematic repositories in the Ubuntu system through GUI

  • Open Software & Update tool.
  • Select the “Other Software” tab and find the repository that you have a problem with.
  • Check the check box in front of the desired PPA repository, and after highlighting it, click the “Remove” option in the screen’s bottom bar.

Removing the problematic repository in Ubuntu through Terminal

If you are used to performing tasks and settings through the Linux terminal, run the following command with sudo privileges to remove the problematic repository:

sudo add-apt-repository --remove ppa:[name]

By removing the problematic PPA repository, you were able to free the system from incompatible PPA repository problems. Do not worry that removing the PPA repository will deprive you of specific software features supported by the PPA repository; you can use other sources to install the software you want.

2. Checking the correctness of the Repository URL in the package manager configuration

One of the reasons for receiving the “repository does not have a release file” error when updating the Ubuntu Linux system is a typo in the Repository URL in the package manager configuration. Hence, you need to check that the repository URL is correct in the package manager configuration of your Ubuntu system. To check the URL of the repository in the Ubuntu system, you need to check the configuration files containing the repository resources.

The /etc/apt/sources.list file in Ubuntu stores the configuration files for the repository URLs and also the files in the /etc/apt/sources.list.d/ directory contains a list of the initial configuration files for the repository URLs. To check the content of the Sources.list file, follow the steps below:

  • Check the content of the Sources.list file

Launch the Linux terminal and open the sources.list file through your favorite editor:

sudo nano /etc/apt/sources.list

By displaying the content of the sources.list file, you can see the URLs of the repository and the defined resources of the Ubuntu system.

Note: You may need Superuser (root) privileges to view and edit the content of the Sources.list file. Also, theCatcommand helps display the content of the Sources.list file, you can use thecat /etc/apt/sources.listcommand for this purpose.

  • Check Additional Sources

The /etc/apt/sources.list.d/ directory also contains files that store some repositories separately, which checking the content of this directory also has advantages. To check additional repository URLs in the content of the files listed in the /etc/apt/sources.list.d/ directory, you can use thecatcommand:

cat /etc/apt/sources.list.d/filename

Replace the filename section with the file name you want to check.

  • Search for problematic repository URLs in the content of the Sources.list file

To search for a specific word or problematic repository URL in the content of the Sources.list file, the grep command is useful and efficient. For example, by searching for lines containing the word “repository,” you can optimize the search for the URL of your desired repository in the file’s content. To search for the phrase “repository” in the contents of the Sources.list file and the /sources.list.d directory, run the following command:

grep "repository" /etc/apt/sources.list /etc/apt/sources.list.d/*

Therefore, you can check the lines containing the word “repository” in the Sources.list file and the files in /sources.list.d.

By checking the repository URL in package manager configuration files, you can ensure that the repository URL is correct, or if there is a typo, edit and correct it and save the file. As a result, check if your problem is solved by running thesudo apt-get updatecommand.

3. Checking Network Connectivity in Ubuntu

Blocking access to the repository server due to internet connection problems or rules set in the firewall is one of the other reasons for receiving the “repository does not have a release file” Ubuntu error. Therefore, to solve this problem, ensure that your system has access to the Internet and that rules blocking access to the repository server are not set in the firewall.

Thepingcommand is one of the valuable methods to check the network connection to the remote host. Run thepingcommand to check the Internet connection:

ping -c 4

Thepingcommand sends ICMP (Internet Control Message Protocol) echo requests to the target host, and the result is displayed. By running the previous command, four packets will be sent to the repository server, and if the connection is confirmed, the packets transferred, received, and the time spent will be displayed in the output.

Confirming the network connection may not be enough to solve this problem, so to be sure, check the active status of the repository server through the following command:

curl -Is | head -1

Ensure the server is active by receiving An HTTP/1.1 200 OK output.

If you do not find any problem checking the network connections and the repository server is active, other reasons led to displaying the” repository does not have a release file” error. But if the problem is in the network connections or the failure of the repository server, change the network or be patient in backing up the server.

4. Switching to an alternative repository Mirror

Sometimes, malfunctioning the repository mirror causes problems. To solve the problem of getting the “repository does not have a release file” error in Ubuntu, changing the repository mirror is worth trying. By checking the contents of the sources.list file and checking the problematic repository entry, you can replace the repository URL with a different mirror that you found on the official Ubuntu website. For this purpose, follow the steps below:

  • Launch the Linux terminal.
  • Make a backup of your current source list before changes through thecpcommand:
Sudo cp /etc/apt/sources.list /etc/apt/sources.list.backup
  • Open the sources.list file to edit and replace different repository Mirror with the desired editor:
sudo nano /etc/apt/sources.list
  • To replace different repository mirror URLs, find the lines containing the repository mirror URL we want to change. Check the lines that start with “deb” or “deb-src” and contain the URL, and replace the URL with the new mirror’s URL.

Note: To access a list of official Ubuntu mirrors, visit this site.

  • After making changes, save the file in the nano editor by pressing Ctrl + O and the Enter button, and exit the nano editor by pressing the Ctrl + X buttons.
  • To reflect the changes and refresh the package cache using the new mirror, update the list of packages installed in Ubuntu:
sudo apt update

As a result, by following the steps correctly, you can easily switch to a different repository mirror in the Ubuntu system and resolve issues with your current mirror.

Why Ubuntu update error no longer have a release file?

When you try to access a repository that is no longer actively supported for your particular version of Ubuntu, you frequently get the “Repository does not have a release file” problem when updating Ubuntu.

There are two basic causes of this:

Ubuntu Release Lifecycle: With ongoing maintenance and updates, each Ubuntu release has a set lifespan. The official repositories are moved or archived after this time, thus your current version cannot access them.

Third-Party Repositories: Some third-party repositories might not update to reflect every Ubuntu release, which could result in out-of-date software and the absence of “Release” files for the particular version you’re using.

This update problem is essentially caused by the repository you are attempting to visit not having the required data (the “Release” file) to supply appropriate packages for your Ubuntu system.

What are some additional troubleshooting tips?

Clean the package cache with sudo apt clean.

Update package lists with sudo apt update after fixing the issue.

How to find the problematic repository?

Usually, the error message identifies the precise repository that is the source of the problem.

You can also look for any lines that might be misspelled or out-of-date in your sources list file (/etc/apt/sources.list).

What to do if the repository is not compatible with my Ubuntu version?

Delete the repository: You can either comment out or delete the relevant line from your sources list if the repository is not intended for your version of Ubuntu.

Look for a substitute: Search for an alternative repository that works with your Ubuntu version and provides the required software. Look for suggestions on internet forums or the official software page.

How to stop facing the ‘Repository does not have a Release file’ error?

Use third-party repositories with caution: Add repositories only that are verified to work with your Ubuntu version and come from reliable sources.

Verify the compliance of the repository: Check the repository’s documentation or website to make sure it works with the Ubuntu version you’re running before adding it.

Update your system frequently: To make sure you have access to the most recent compatible applications and repositories, keep your system and package lists up to date.


This error could be caused by several factors, including improper repository configurations, network problems, or poor repository maintenance. This can also happen if the repository you are using is not configured correctly for your version of Linux.

This error message is displayed when the Ubuntu Package Manager (APT), to update or install a package from the repository, fails to find the release file that contains essential information about the contents of the repository and the available packages.


All the methods to solve the repository does not have a release file Debian were explained.

We hope that by trying these methods, you can detect and fix the ‘Repository does not have a Release file’ error in Ubuntu Linux.

Surely, one of the solutions taught will solve your problem, but if you recommend another solution to this problem, share it with us in the comments section.

Leave a Reply

Your email address will not be published. Required fields are marked.