# Heroku gpg issues in ubuntu images **URL:** \ **Category:** CircleCI Images\ **Created:** [April 26, 2022, 10:11pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834 "2022-04-26T22:11:19Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![hwchase17](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/hwchase17/32/29996_2.png) [@hwchase17](https://discuss.circleci.com/u/hwchase17)\ **Post date:** [April 26, 2022, 10:11pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/1 "2022-04-26T22:11:19Z")
image: ubuntu-2004:202107-02 trying to run `sudo apt-get update` yields the following error ```auto ircleci@ip-172-28-32-194:~$ sudo apt-get update Hit:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal-backports InRelease Get:4 https://cli-assets.heroku.com/apt ./ InRelease [2,895 B] Hit:5 https://deb.nodesource.com/node_16.x focal InRelease Hit:6 http://security.ubuntu.com/ubuntu focal-security InRelease Hit:7 http://ppa.launchpad.net/git-core/ppa/ubuntu focal InRelease Err:4 https://cli-assets.heroku.com/apt ./ InRelease The following signatures were invalid: EXPKEYSIG 6DB5542C356545CF Heroku, Inc. Hit:8 http://ppa.launchpad.net/openjdk-r/ppa/ubuntu focal InRelease Reading package lists... Done W: GPG error: https://cli-assets.heroku.com/apt ./ InRelease: The following signatures were invalid: EXPKEYSIG 6DB5542C356545CF Heroku, Inc. E: The repository 'https://cli-assets.heroku.com/apt ./ InRelease' 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 my first time posting an error so please let me know if I can be more expressive! Thanks! ---
**Author:** ![hervinhio](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/hervinhio/32/30005_2.png) [@hervinhio](https://discuss.circleci.com/u/hervinhio)\ **Post date:** [April 27, 2022, 7:10pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/2 "2022-04-27T19:10:31Z")
I think this [answer](https://github.com/heroku/cli/issues/1812#issuecomment-1110862625) on GitHub will help you. It helped me solve my case. ---
**Author:** ![FelicianoTech](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/felicianotech/32/21348_2.png) [@FelicianoTech](https://discuss.circleci.com/u/FelicianoTech)\ **Post date:** [May 26, 2022, 4:10pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/3 "2022-05-26T16:10:47Z")
This issue can be fixed by running: ```bash curl https://cli-assets.heroku.com/apt/release.key | sudo apt-key add - ``` The issue is that Heroku’s old apt signing key expired. The command above downloads their new key. Updated images are on the way that avoids this issue. ---
**Author:** ![ms1111](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ms1111/32/25750_2.png) [@ms1111](https://discuss.circleci.com/u/ms1111)\ **Post date:** [November 15, 2022, 12:28am UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/4 "2022-11-15T00:28:03Z")
I’m still seeing this error with the stock `ubuntu-2204:2022.10.2` machine image, for what it’s worth. ```auto E: Repository 'https://cli-assets.heroku.com/apt ./ InRelease' changed its 'Origin' value from 'Heroku' to 'Jeff Dickey @jdxcode' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details. ``` ---
**Author:** ![jamesbassett](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jamesbassett/32/31599_2.png) [@jamesbassett](https://discuss.circleci.com/u/jamesbassett)\ **Post date:** [November 15, 2022, 1:47am UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/5 "2022-11-15T01:47:31Z")
Same here. We’ve worked around it with `sudo rm -rf /etc/apt/sources.list.d/heroku.list` ---
**Author:** ![jackdek11](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jackdek11/32/31604_2.png) [@jackdek11](https://discuss.circleci.com/u/jackdek11)\ **Post date:** [November 15, 2022, 1:29pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/6 "2022-11-15T13:29:25Z")
This worked for me 👍 ---
**Author:** ![dafeder](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/dafeder/32/31607_2.png) [@dafeder](https://discuss.circleci.com/u/dafeder)\ **Post date:** [November 15, 2022, 3:53pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/7 "2022-11-15T15:53:57Z")
We’ve also just started hitting this error. Using the workarounds for now… ---
**Author:** ![FelicianoTech](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/felicianotech/32/21348_2.png) [@FelicianoTech](https://discuss.circleci.com/u/FelicianoTech)\ **Post date:** [November 15, 2022, 5:54pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/8 "2022-11-15T17:54:53Z")
This issue was fixed earlier this year. People are seeing this issue again because Heroku has decided to change their signing key YET AGAIN. This is unacceptable for the type of image we produce so this time we’re going to fix this issue by not including the Heroku repository at all. This will prevent the problem from returning. Fixed images will be produced and should roll out within the next 24 hours or so. We’ll update here when they’re ready. ---
**Author:** ![Ortega-Dan](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/ortega-dan/32/31639_2.png) [@Ortega-Dan](https://discuss.circleci.com/u/Ortega-Dan)\ **Post date:** [November 18, 2022, 2:58am UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/9 "2022-11-18T02:58:22Z")
Looks like it got fixed, I just commented the line in /etc/apt/sources.list.d/heroku.list some days ago. And just uncommented it and it upgraded the package well now. Thanks. ---
**Author:** ![Janeer](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Janeer](https://discuss.circleci.com/u/Janeer)\ **Post date:** [December 20, 2022, 2:45pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/10 "2022-12-20T14:45:36Z")
After upgrade it works fine. I also had this error with GPG. project [home page](https://www.worktime.com/employee-time-tracking-software). ---
**Author:** ![jerdog](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jerdog/32/32130_2.png) [@jerdog](https://discuss.circleci.com/u/jerdog)\ **Post date:** [December 20, 2022, 3:20pm UTC](https://discuss.circleci.com/t/heroku-gpg-issues-in-ubuntu-images/43834/11 "2022-12-20T15:20:21Z")
Closed on December 20, 2022, 3:20pm UTC