# Apt repo no longer signed

**URL:** <https://discourse.chef.io/t/apt-repo-no-longer-signed/20843>\
**Category:** Chef Infra (archive)\
**Created:** [March 11, 2022, 9:05pm UTC](https://discourse.chef.io/t/apt-repo-no-longer-signed/20843 "2022-03-11T21:05:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cswilliams](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/cswilliams/32/2572_2.png) [@cswilliams](https://discourse.chef.io/u/cswilliams)\
**Post date:** [March 11, 2022, 9:05pm UTC](https://discourse.chef.io/t/apt-repo-no-longer-signed/20843/1 "2022-03-11T21:05:51Z")

</div>

I started receiving this error today when running "apt-get update" on our chef server:

```auto
E: The repository 'https://packages.chef.io/repos/apt/stable focal Release' 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.

```

This is on an Ubuntu 20.04 server. The apt repo was added by following the steps here under Debian/Ubuntu: [Chef Software Packages](https://docs.chef.io/packages/)

---

<div class="post-metadata">

**Author:** ![jasonwbarnett](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jasonwbarnett/32/2157_2.png) [@jasonwbarnett](https://discourse.chef.io/u/jasonwbarnett)\
**Post date:** [March 12, 2022, 10:21pm UTC](https://discourse.chef.io/t/apt-repo-no-longer-signed/20843/2 "2022-03-12T22:21:55Z")

</div>

Me and another person were chatting on Slack about this same issue. He was using the apt repo and I'm using the YUM repo.

---

<div class="post-metadata">

**Author:** ![js2](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/js2/32/3337_2.png) [@js2](https://discourse.chef.io/u/js2)\
**Post date:** [March 14, 2022, 12:36am UTC](https://discourse.chef.io/t/apt-repo-no-longer-signed/20843/3 "2022-03-14T00:36:17Z")

</div>

This should be working again.