ð ~1 min read
Table of contents
Symptom & Impact
Repositories are rejected due to missing signing keys, blocking updates and installs.
Environment & Reproduction
Seen after adding third-party sources without signed-by keyring setup.
sudo apt update
Root Cause Analysis
APT cannot verify Release signatures because trusted keyring entries are absent or outdated.
Quick Triage
Identify which repository and key fingerprint are failing.
grep -R '^deb ' /etc/apt/sources.list /etc/apt/sources.list.d
Step-by-Step Diagnosis
Inspect source entries for `signed-by` and confirm key file presence.
ls -l /etc/apt/keyrings && apt-key list

Solution – Primary Fix
Install the correct vendor key into `/etc/apt/keyrings` and reference it explicitly in source files.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
curl -fsSL | sudo gpg --dearmor -o /etc/apt/keyrings/vendor.gpg && sudo apt update

Solution – Alternative Approaches
Disable untrusted repository entries until official signed key distribution is confirmed.
Verification & Acceptance Criteria
Repository metadata verifies cleanly and no NO_PUBKEY warnings appear.
Rollback Plan
Restore prior source list files and remove newly added keyring if the wrong key was applied.
Prevention & Hardening
Require signed-by keyrings for all external repos and review fingerprints before onboarding.
Related Errors & Cross-Refs
Also check expired keys, `InRelease` signature mismatches, and proxy tampering alerts.
Related tutorial: View the step-by-step tutorial for Ubuntu 26.04 LTS.
View all Ubuntu 26.04 LTS tutorials on the Tutorials Hub â
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Ubuntu secure APT repository key management documentation.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today â we respond within one business day.