Executing an everyday package update with sudo apt update on Ubuntu or Debian only to be halted by the error message E: The repository ‘…’ is not signed. N: Updating from such a repository can’t be done securely, and is therefore disabled by default is a common stumbling block. Because modern versions of Ubuntu (including Ubuntu 22.04 LTS and Ubuntu 24.04 LTS) enforce strict cryptographic verification for all software repositories, APT explicitly refuses to fetch package manifests or install software from any source that lacks a verified GPG signature. This security safeguard protects systems from man-in-the-middle attacks and malicious package tampering, but it also halts package management whenever third-party PPAs expire, change maintainer keys, or become abandoned.
Why Does APT Return ‘The repository is not signed’?
APT relies on InRelease and Release files signed by public GPG keys to guarantee package authenticity. The error triggers when this cryptographic trust chain breaks down, typically due to:
- Missing or Expired GPG Keyrings: The third-party repository maintainer updated their public signing key, leaving your local system with an obsolete or revoked key in
/etc/apt/trusted.gpg.d/. - Unsupported Ubuntu Release Codename: Adding a PPA designed for an older or newer release (such as focal or jammy on a noble system) where the repository maintainer has not published signed release manifests for your distribution.
- Abandoned or Dead PPAs: Third-party software projects discontinued by their maintainers, causing launchpad HTTP 404 responses that APT flags as unsigned.
- Deprecated apt-key Transitions: Older key installation methods clashing with modern signed-by directory architectures.
Step 1: Identify the Problematic Repository
Before making changes, examine the exact output of your update command to pinpoint the failing repository URL.
- Open your terminal application.
- Run the package list update command:
sudo apt update - Carefully read the terminal output preceding the
E: The repository ... is not signederror. - Note the specific PPA name or domain (for example,
ppa.launchpadcontent.net/maintainer/nameor an external vendor repository URL).
Step 2: Remove Obsolete or Abandoned PPAs
If the error points to a discontinued third-party PPA that no longer provides signed releases for your version of Ubuntu, removing the source immediately restores full APT functionality.
- If the repository is a standard Personal Package Archive (PPA), remove it using
add-apt-repository:sudo add-apt-repository --remove ppa:maintainer/repository-name - Alternatively, if the repository was added as a standalone list file, list the contents of the sources directory:
ls /etc/apt/sources.list.d/ - Delete the offending
.listor.sourcesfile:sudo rm /etc/apt/sources.list.d/problematic-repo.list - Also remove any associated legacy GPG keys:
sudo rm /etc/apt/trusted.gpg.d/problematic-repo.gpg - Run
sudo apt updateto confirm the error is cleared.
Step 3: Manually Import Missing Repository GPG Keys
If the repository is legitimate and actively maintained, fetching its new public key and storing it in the dedicated /etc/apt/keyrings/ directory resolves the signature requirement.
- Ensure the modern APT keyrings directory exists on your system:
sudo mkdir -p -m 755 /etc/apt/keyrings - Fetch and de-armor the vendor’s official GPG key directly using
curlorwget:curl -fsSL https://vendor.example.com/repo/key.gpg | sudo gpg --dearmor -o /etc/apt/keyrings/vendor-archive-keyring.gpg - Open the repository list file in a text editor (e.g.
sudo nano /etc/apt/sources.list.d/vendor.list) and ensure the entry references the newly imported keyring using thesigned-byattribute:deb [signed-by=/etc/apt/keyrings/vendor-archive-keyring.gpg] https://vendor.example.com/repo/ ubuntu-codename main - Save the file (press Ctrl + O and Enter, then Ctrl + X to exit) and re-run
sudo apt update.
Step 4: Clean Corrupted APT Cache Lists
Occasionally, an interrupted network download can leave a partially downloaded, corrupt InRelease file in your local cache that causes APT to mistake a valid repository for an unsigned one.
- Clear local repository index lists by running:
sudo rm -rf /var/lib/apt/lists/* - Clean the APT package cache:
sudo apt clean - Rebuild all repository lists from scratch:
sudo apt update - All active repositories will re-download fresh, valid cryptographic manifests.