# Update failed - signatures couldn't be verified **URL:** https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469 **Category:** Troubleshooting **Created:** [8 September 2026 04:38 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469 "2026-09-08T04:38:51Z") **Posts on this page:** 19 **Page:** 1
### Author: ![SandyBlack](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/b782af/32.png) [@SandyBlack](https://dietpi.com/forum/u/SandyBlack) #### Post date: [8 September 2026 04:38 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/1 "2026-09-08T04:38:51Z")
#### Details: - Date | 2026-09-08 06:33:26 - Program name | DietPi-Update - Command | `apt-get -y -eany update` - Exit code | 100 - DietPi version | v9.9.0 (MichaIng/master) - Distro version | bookworm (ID=7,RASPBIAN=0) - Kernel version | `Linux loxberry 6.6.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25) aarch64 GNU/Linux` - Architecture | `arm64` - Hardware model | RPi 5 Model B (aarch64) (ID=5) - Power supply | (EG: RAVPower 5V 1A) - SD card | (EG: SanDisk Ultra 16 GB) #### Steps to reproduce: 1. … 2. … #### Expected behaviour: - … #### Actual behaviour: - … #### Extra details: - … #### Additional logs: ```auto Ign:1 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease Get:2 https://packages.sury.org/php bookworm InRelease [6136 B] Hit:3 https://deb.debian.org/debian bookworm InRelease Hit:4 https://deb.debian.org/debian bookworm-updates InRelease Get:5 https://dl.yarnpkg.com/debian stable InRelease Hit:6 https://deb.debian.org/debian-security bookworm-security InRelease Hit:7 https://deb.debian.org/debian bookworm-backports InRelease Hit:8 https://dietpi.com/apt bookworm InRelease Err:2 https://packages.sury.org/php bookworm InRelease The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key Hit:9 https://dietpi.com/apt all InRelease Hit:10 https://archive.raspberrypi.com/debian bookworm InRelease Hit:11 https://pkg.cloudflare.com/cloudflared any InRelease Err:5 https://dl.yarnpkg.com/debian stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525 Ign:1 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease Ign:1 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease Err:1 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease Something wicked happened resolving 'repo.ebusd.eu:https' (-5 - No address associated with hostname) Fetched 22.7 kB in 7s (3207 B/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://pack ages.sury.org/php bookworm InRelease: The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.y arnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 62D54FD4003F6525 E: Failed to fetch https://repo.ebusd.eu/apt/default/bookworm/dists/bookworm/InRelease Something wicked happened resolving 'repo.ebusd.eu:https' (-5 - No address associated with hostname) E: Failed to fetch https://packages.sury.org/php/dists/bookworm/InRelease The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.OR G Automatic Signing Key E: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures couldn't be verified because the public key is not ava ilable: NO_PUBKEY 62D54FD4003F6525 E: Some index files failed to download. They have been ignored, or old ones used instead. ``` ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [8 September 2026 08:14 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/2 "2026-09-08T08:14:23Z")
> [@SandyBlack](#): > > - loxberry You are using a Loxberry system? Might be good to get in touch with these guys. Anyway you have multiple issues or challanges > [@SandyBlack](#): > > - DietPi version | v9.9.0 These version is nearly 2 years old, from December 2024 Within you source configuration you have a couple of old/incorrect sources defined > [@SandyBlack](#): > > `Err:2 https://packages.sury.org/php` We don’t use sury php repository since ages, not sure if this is specific thing of Loxberry > [@SandyBlack](#): > > `Err:5 https://dl.yarnpkg.com/debian` This doesn’t seems to be setup by DietPi. At least I’m not able to find it in our code. Not sure if this is specific thing of Loxberry > [@SandyBlack](#): > > `Err:1 https://repo.ebusd.eu/apt/default/bookworm` same goes for this repository. This even did not exist anymore > [@SandyBlack](#): > > `Something wicked happened resolving 'repo.ebusd.eu:https' (-5 - No address associated with hostname)` Best ist to check with Loxberry guys first if these repositories have been setup intentionally. ---
### Author: ![SandyBlack](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/b782af/32.png) [@SandyBlack](https://dietpi.com/forum/u/SandyBlack) #### Post date: [8 September 2026 13:09 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/3 "2026-09-08T13:09:04Z")
Thanks for the fast response. I will talk to the Loxberry devs. If I can’t get the update to work are there any security relevant changes from my version to the newest one or could I still live with my current version if the upgrade issue can’t be solved? ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [8 September 2026 13:14 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/4 "2026-09-08T13:14:00Z")
theoretically things could be fixed. But first to check with Loxberry if these repositories have been setup intentionally. ---
### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng) #### Post date: [8 September 2026 15:08 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/5 "2026-09-08T15:08:45Z")
You should definitely solve those issues ASAP, as with such an old package state, your system is at high risk, and possibly a risk for other systems across the Internet, as part of a botnet or similar. APT upgrades should be done at a weekly, better daily basis, especially in times of AI tools being able to find and exploit security vulnerabilities within hours. If you did not add those 3 APT repositories by yourself, then yes, at best talk to Loxberry whether they were added their end, and how to update the keys, and what to replace `repo.ebusd.eu` with (which does not exist anymore). If you did add those repos by yourself, then check back whether your really still need those, and for what: - `yarn` is a Node.js package/dependency manager, which can be installed via `npm` and alike directly. It is uncommon to install it via APT repository. - The PHP repository is reasonable only if you require a specific different PHP version on your Debian version. But using it has some risks, since it ships a bunch of other system libraries, which can cause incompatibilities. Usually I’d recommend to stick with the native Debian PHP packages, upgrade Debian itself if you need a newer PHP version, and stop using software which requires older PHP to run (as this means it is badly maintained, and possibly a security issue by itself). - If `repo.ebusd.eu` was for eBUSd, then that repo was shut down. Remove it and follow current install instructions, which means to download and install the matching DEB package from their releases on GitHub manually: [GitHub - john30/ebusd: daemon for communication with eBUS heating systems · GitHub](https://github.com/john30/ebusd#installation) ---
### Author: ![SandyBlack](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/b782af/32.png) [@SandyBlack](https://dietpi.com/forum/u/SandyBlack) #### Post date: [9 September 2026 06:41 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/6 "2026-09-09T06:41:46Z")
I didn’t added any of these packages myself I already reached out to the Loxberry developers. Assuming they cannot help what are my best options? Regarding repo.ebusd.eu: I guess this repo is for the ebusd-plugin in loxberry. The big advantage is it has a GUI where you can check the ebus values directly. But if that’s the issue I guess I have to just delete the repo? ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [9 September 2026 07:03 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/7 "2026-09-09T07:03:24Z")
can you link the topic you created at Loxberry? So we can follow. EDIT: found it [Update von DietPi schlägt fehl - loxforum.com](https://www.loxforum.com/forum/projektforen/loxberry/allgemeines-aa/491202-update-von-dietpi-schl%C3%A4gt-fehl) (German speaking forum) ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [9 September 2026 16:57 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/8 "2026-09-09T16:57:59Z")
ok did some research using claude.ai - **Sury PHP** part of the Loxberry installation script > A potential fix could be ```auto curl -sL https://packages.sury.org/php/apt.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/deb.sury.org-php.gpg >/dev/null ``` - **Yarn** part of the Loxberry installation script > A potential fix could be ```auto curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null ``` - **ebusd** Not part of the Loxberry installation script but seems to be related to the plugin `loxberry-plugin-ebusd` source: [Victor Vlasák / LoxBerry Plugin ebusd · GitLab](https://gitlab.com/VVlasy/loxberry-plugin-ebusd) and there is already a GitLab issue [Error: Failed to fetch https://repo.ebusd.eu (#12) · Issues · Victor Vlasák / LoxBerry Plugin ebusd · GitLab](https://gitlab.com/VVlasy/loxberry-plugin-ebusd/-/work_items/12) installed by: [preroot.sh · master · Victor Vlasák / LoxBerry Plugin ebusd · GitLab](https://gitlab.com/VVlasy/loxberry-plugin-ebusd/-/blob/master/preroot.sh?ref_type=heads#L65-L67) Best to remove this as it doesn’t seems to be maintained anymore, related GitHub repositories have been deleted. A potential fix could be ```auto sudo rm /etc/apt/sources.list.d/*ebusd* ``` ---
### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng) #### Post date: [9 September 2026 21:41 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/9 "2026-09-09T21:41:46Z")
For the PHP repo, the better solution which also Loxberry does in the meantime: ```sh cd /tmp wget 'https://packages.sury.org/debsuryorg-archive-keyring.deb' dpkg -i debsuryorg-archive-keyring.deb ``` From that point on, APT upgrades should keep the key up-to-date automatically. ---
### Author: ![SandyBlack](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/b782af/32.png) [@SandyBlack](https://dietpi.com/forum/u/SandyBlack) #### Post date: [10 September 2026 06:21 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/10 "2026-09-10T06:21:38Z")
Thank you both! The log now looks like this: ```auto Get:1 https://packages.sury.org/php bookworm InRelease \[6136 B\] Ign:2 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease Get:3 https://dl.yarnpkg.com/debian stable InRelease Hit:4 https://deb.debian.org/debian bookworm InRelease Get:5 https://deb.debian.org/debian bookworm-updates InRelease \[55.4 kB\] Get:6 https://deb.debian.org/debian-security bookworm-security InRelease \[34.8 kB\] Get:7 https://deb.debian.org/debian bookworm-backports InRelease \[59.4 kB\] Get:8 https://packages.sury.org/php bookworm/main arm64 Packages \[289 kB\] Hit:9 https://dietpi.com/apt bookworm InRelease Hit:10 https://dietpi.com/apt all InRelease Get:11 https://pkg.cloudflare.com/cloudflared any InRelease \[5039 B\] Get:12 https://archive.raspberrypi.com/debian bookworm InRelease \[55.0 kB\] Get:13 https://deb.debian.org/debian-security bookworm-security/main arm64 Packages \[335 kB\] Get:14 https://pkg.cloudflare.com/cloudflared any/main arm64 Packages \[375 B\] Get:15 https://archive.raspberrypi.com/debian bookworm/main arm64 Packages \[581 kB\] Ign:2 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease Ign:2 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease Err:2 https://repo.ebusd.eu/apt/default/bookworm bookworm InRelease Something wicked happened resolving 'repo.ebusd.eu:https' (-5 - No address associated with hostname) Fetched 1439 kB in 7s (202 kB/s) Reading package lists... E: Failed to fetch https://repo.ebusd.eu/apt/default/bookworm/dists/bookworm/InRelease Something wicked happened resolving 'repo.ebusd.eu:https' (-5 - No address associated with hostname) E: Some index files failed to download. They have been ignored, or old ones used instead. ``` If I interpret it correctly only the ebusd-repo is causing a problem. Am I right? If I delete the repo I guess the plugin won’t work anymore as well will it? Or is the repo only needed during installation for fetching the files? Because even if it is - unfortunately - not maintained anymore it is still working great on my end. One question for my understanding: I have a ssd with two partitions. If I use dietpi-backup it will backup all files on both partitions and all the loxberry files etc. as well? ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [10 September 2026 07:56 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/11 "2026-09-10T07:56:55Z")
> [@SandyBlack](#): > > If I interpret it correctly only the ebusd-repo is causing a problem. Am I right? correct > [@SandyBlack](#): > > Or is the repo only needed during installation for fetching the files Yes, exactly. Simply removing the repository won’t affect functionality. Keep in mind, however, that you won’t receive any further updates (it doesn’t work anymore anyway). This could lead to incompatibilities or security risks in the future. Maybe you should consider some alternatives 😉 For now, best to remove the source file configuration ```auto sudo rm /etc/apt/sources.list.d/*ebusd* ``` > [@SandyBlack](#): > > One question for my understanding: I have a ssd with two partitions. If I use dietpi-backup it will backup all files on both partitions and all the loxberry files etc. as well? correct, the entire system should be backed up. There is one exception: the file systems `/mnt/` and `/media/` are not backed up, although `/mnt/dietpi_userdata/` is included after all. I know it sounds complicated, or 🙂 ---
### Author: ![SandyBlack](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/b782af/32.png) [@SandyBlack](https://dietpi.com/forum/u/SandyBlack) #### Post date: [10 September 2026 10:42 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/12 "2026-09-10T10:42:48Z")
Thank you so much guys. The update finished successfully and ebusd is still kinda working. But if I rerun dietpi-update I get an error: ```auto APT update │ - Command: apt-get -y -eany update │ - Exit code: 100 │ - DietPi version: v10.6.2 (MichaIng/master) | HW_MODEL: 5 | HW_ARCH: 3 | │ DISTRO: 7 │ - Error log: │ Hit:1 https://deb.debian.org/debian bookworm InRelease │ Hit:2 https://deb.debian.org/debian bookworm-updates InRelease │ Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease │ Hit:4 https://deb.debian.org/debian bookworm-backports InRelease │ Hit:5 https://packages.sury.org/php bookworm InRelease │ Hit:6 https://dietpi.com/apt bookworm InRelease │ Hit:7 https://dietpi.com/apt all InRelease │ Hit:8 https://pkg.cloudflare.com/cloudflared any InRelease │ Hit:9 https://dl.yarnpkg.com/debian stable InRelease and the shell: DietPi-Update ───────────────────────────────────────────────────── Phase: Checking for available DietPi update \[OK \] DietPi-Update | Checking IPv4 network connectivity \[OK \] DietPi-Update | Checking IPv6 network connectivity \[OK \] DietPi-Update | Checking DNS resolver \[INFO \] DietPi-Update | Getting latest version from: https://raw.githubusercont ent.com/MichaIng/DietPi/master/.update/version \[OK \] DietPi-Update | Got valid latest version: 10.6.2 \[OK \] DietPi-Update | No update required, your DietPi installation is already up to date: \[INFO \] DietPi-Update | Current version : v10.6.2 \[INFO \] DietPi-Update | Latest version : v10.6.2 \[INFO \] DietPi-Update | Checking for new available live patches \[INFO \] DietPi-Update | APT update, please wait... Hit:1 https://deb.debian.org/debian bookworm InRelease Hit:2 https://deb.debian.org/debian bookworm-updates InRelease Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.debian.org/debian bookworm-backports InRelease Hit:5 https://packages.sury.org/php bookworm InRelease Hit:6 https://dietpi.com/apt bookworm InRelease Hit:7 https://dietpi.com/apt all InRelease Hit:8 https://pkg.cloudflare.com/cloudflared any InRelease Hit:9 https://dl.yarnpkg.com/debian stable InRelease Hit:10 https://archive.raspberrypi.com/debian bookworm InRelease Err:5 https://packages.sury.org/php bookworm InRelease The following signatures couldn't be verified because the public key is not av ailable: NO_PUBKEY B188E2B695BD4743 Reading package lists... W: An error occurred during the signature verification. The repository is not up dated and the previous index files will be used. GPG error: https://packages.sur y.org/php bookworm InRelease: The following signatures couldn't be verified beca use the public key is not available: NO_PUBKEY B188E2B695BD4743 E: Failed to fetch https://packages.sury.org/php/dists/bookworm/InRelease The f ollowing signatures couldn't be verified because the public key is not available : NO_PUBKEY B188E2B695BD4743 E: Some index files failed to download. They have been ignored, or old ones used instead. \[FAILED\] DietPi-Update | APT update * Command: apt-get -y -eany update \[FAILED\] DietPi-Update | Unable to continue, DietPi-Update will now terminate. ``` For sury I did this: `cd /tmp` `wget '``https://packages.sury.org/debsuryorg-archive-keyring.deb``'` `dpkg -i debsuryorg-archive-keyring.deb` ---
### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng) #### Post date: [10 September 2026 10:55 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/13 "2026-09-10T10:55:08Z")
Check the respective list file in `/etc/apt/sources.list.d/`. There should be a “signed-by” value, like `[signed-by=/usr/share/keyrings/deb.sury.org-php.gpg]` or similar, but the path seems wrong. Change the path to `/usr/share/keyrings/debsuryorg-archive-keyring.gpg`. ---
### Author: ![SandyBlack](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/b782af/32.png) [@SandyBlack](https://dietpi.com/forum/u/SandyBlack) #### Post date: [11 September 2026 05:21 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/14 "2026-09-11T05:21:37Z")
I’ve adapted the php.list. It looks like this now: ![image](https://dietpi.com/forum/uploads/default/original/2X/c/cc1b0df3d2cba98c1775cc411a070dd21fe7ba0e.png) That was the old one: ![image](https://dietpi.com/forum/uploads/default/original/2X/f/f4a9b1d4001c48a24f86568b957258fce112dbcb.png) Unfortunately I still get an error: ```auto Hit:1 https://deb.debian.org/debian bookworm InRelease Get:2 https://deb.debian.org/debian bookworm-updates InRelease \[55.4 kB\] Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease Get:4 https://deb.debian.org/debian bookworm-backports InRelease \[59.4 kB\] Hit:5 https://packages.sury.org/php bookworm InRelease Hit:6 https://dl.yarnpkg.com/debian stable InRelease Hit:7 https://pkg.cloudflare.com/cloudflared any InRelease Hit:8 https://dietpi.com/apt bookworm InRelease Hit:9 https://dietpi.com/apt all InRelease Err:5 https://packages.sury.org/php bookworm InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743 Get:10 https://archive.raspberrypi.com/debian bookworm InRelease \[55.0 kB\] Fetched 170 kB in 1s (163 kB/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743 E: Failed to fetch https://packages.sury.org/php/dists/bookworm/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743 E: Some index files failed to download. They have been ignored, or old ones used instead. ``` ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [11 September 2026 10:11 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/15 "2026-09-11T10:11:10Z")
ok let’s see how it looks on your system ```auto ls -la /etc/apt/sources.list.d/ | grep -i php ls -la /usr/share/keyrings/ | grep -i sury grep -ri sury /etc/apt/sources.list /etc/apt/sources.list.d/*.list 2>/dev/null sudo apt-key list 2>/dev/null | grep -i -B2 sury ``` pls try to copy paste from your ssh shell to avoid screen prints. ---
### Author: ![SandyBlack](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/b782af/32.png) [@SandyBlack](https://dietpi.com/forum/u/SandyBlack) #### Post date: [11 September 2026 11:13 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/16 "2026-09-11T11:13:10Z")
> [@Joulinar](#): > > `apt-key list 2>/dev/null | grep -i -B2 sury` Here’s the result: ```auto root@loxberry:/opt/loxberry# ls -la /etc/apt/sources.list.d/ | grep -i php -rw-r--r-- 1 root root 112 Sep 11 07:18 php.list root@loxberry:/opt/loxberry# ls -la /usr/share/keyrings/ | grep -i sury root@loxberry:/opt/loxberry# grep -ri sury /etc/apt/sources.list /etc/apt/sources.list.d/\*.list 2>/dev/null /etc/apt/sources.list.d/php.list:deb \[signed-by=/usr/share/keyrings/debsuryorg-archive-keyring.gpg\] https://packages.sury.org/php/ bookworm main root@loxberry:/opt/loxberry# apt-key list 2>/dev/null | grep -i -B2 sury root@loxberry:/opt/loxberry# ``` The error is now: ```auto Hit:1 https://packages.sury.org/php bookworm InRelease Hit:2 https://deb.debian.org/debian bookworm InRelease Get:3 https://deb.debian.org/debian bookworm-updates InRelease \[55.4 kB\] Hit:4 https://deb.debian.org/debian-security bookworm-security InRelease Get:5 https://deb.debian.org/debian bookworm-backports InRelease \[59.4 kB\] Err:1 https://packages.sury.org/php bookworm InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743 Hit:6 https://dietpi.com/apt bookworm InRelease Hit:7 https://dietpi.com/apt all InRelease Hit:8 https://pkg.cloudflare.com/cloudflared any InRelease Hit:9 https://dl.yarnpkg.com/debian stable InRelease Get:10 https://archive.raspberrypi.com/debian bookworm InRelease \[55.0 kB\] Get:11 https://archive.raspberrypi.com/debian bookworm/main arm64 Packages \[581 kB\] Fetched 751 kB in 2s (398 kB/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743 E: Failed to fetch https://packages.sury.org/php/dists/bookworm/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743 E: Some index files failed to download. They have been ignored, or old ones used instead. ``` ---
### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng) #### Post date: [11 September 2026 11:33 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/17 "2026-09-11T11:33:26Z")
Please repeat this: ```sh cd /tmp wget 'https://packages.sury.org/debsuryorg-archive-keyring.deb' sudo dpkg -i debsuryorg-archive-keyring.deb ``` And check whether it throws errors. If that package is installed successfully, the file `/usr/share/keyrings/debsuryorg-archive-keyring.gpg` should exist. ---
### Author: ![SandyBlack](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/s/b782af/32.png) [@SandyBlack](https://dietpi.com/forum/u/SandyBlack) #### Post date: [11 September 2026 12:44 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/18 "2026-09-11T12:44:36Z")
> [@MichaIng](#): > > `dpkg -i debsuryorg-archive-keyring.deb` Here’s the result: ```auto root@loxberry:/opt/loxberry# cd /tmp root@loxberry:/tmp# wget 'https://packages.sury.org/debsuryorg-archive-keyring.d eb' --2026-09-11 14:41:00-- https://packages.sury.org/debsuryorg-archive-keyring.de b Resolving packages.sury.org (packages.sury.org)... 2a04:4e42:8e::820, 140.248.14 3.52 Connecting to packages.sury.org (packages.sury.org)|2a04:4e42:8e::820|:443... co nnected. HTTP request sent, awaiting response... 200 OK Length: 7180 (7.0K) \[application/octet-stream\] Saving to: ‘debsuryorg-archive-keyring.deb’ debsuryorg-archive- 100%\[===================>\] 7.01K --.-KB/s in 0s 2026-09-11 14:41:00 (97.6 MB/s) - ‘debsuryorg-archive-keyring.deb’ saved \[7180/7 180\] root@loxberry:/tmp# dpkg -i debsuryorg-archive-keyring.deb Selecting previously unselected package debsuryorg-archive-keyring. (Reading database ... 88422 files and directories currently installed.) Preparing to unpack debsuryorg-archive-keyring.deb ... Unpacking debsuryorg-archive-keyring (2025.11.18) ... Setting up debsuryorg-archive-keyring (2025.11.18) ... root@loxberry:/tmp# ``` It actually seems to work now: ```auto DietPi-Update ───────────────────────────────────────────────────── Phase: Checking for available DietPi update \[OK \] DietPi-Update | Checking IPv4 network connectivity \[OK \] DietPi-Update | Checking IPv6 network connectivity \[OK \] DietPi-Update | Checking DNS resolver \[INFO \] DietPi-Update | Getting latest version from: https://raw.githubusercontent.com/MichaIng/DietPi/master/.update/version \[OK \] DietPi-Update | Got valid latest version: 10.6.2 \[OK \] DietPi-Update | No update required, your DietPi installation is already up to date: \[INFO \] DietPi-Update | Current version : v10.6.2 \[INFO \] DietPi-Update | Latest version : v10.6.2 \[INFO \] DietPi-Update | Checking for new available live patches \[INFO \] DietPi-Update | APT update, please wait... Hit:1 https://deb.debian.org/debian bookworm InRelease Hit:2 https://deb.debian.org/debian bookworm-updates InRelease Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://packages.sury.org/php bookworm InRelease Hit:5 https://deb.debian.org/debian bookworm-backports InRelease Hit:6 https://dl.yarnpkg.com/debian stable InRelease Hit:7 https://dietpi.com/apt bookworm InRelease Hit:8 https://dietpi.com/apt all InRelease Hit:9 https://pkg.cloudflare.com/cloudflared any InRelease Get:10 https://archive.raspberrypi.com/debian bookworm InRelease \[55.0 kB\] Get:11 https://archive.raspberrypi.com/debian bookworm/main arm64 Packages \[581 kB\] Fetched 636 kB in 2s (338 kB/s) Reading package lists... \[OK \] DietPi-Update | APT update \[INFO \] DietPi-Update | Storing number of available APT upgrades to file: /run/dietpi/.apt_updates root@loxberry:/tmp# ``` How can I configure the update application to do the APT upgrade daily but not bigger dietpi upgrades? ---
### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng) #### Post date: [11 September 2026 13:07 UTC](https://dietpi.com/forum/t/update-failed-signatures-couldnt-be-verified/25469/19 "2026-09-11T13:07:32Z")
Great! > [@SandyBlack](#): > > How can I configure the update application to do the APT upgrade daily but not bigger dietpi upgrades? This will do via daily cron job: ```sh G_CONFIG_INJECT 'CONFIG_CHECK_APT_UPDATES=' 'CONFIG_CHECK_APT_UPDATES=2' /boot/dietpi.txt ``` Logs of the last package upgrade call can be found in `/var/lib/dietpi/logs/dietpi-upgrade_apt.log`.