After apt update && apt upgrade -y I now get these errors

Community Support
1 
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Get:3 https://packages.sury.org/php bookworm InRelease [6,133 B]
Hit:5 http://deb.debian.org/debian bookworm-updates InRelease
Hit:6 https://packages.redis.io/deb bookworm InRelease
Hit:4 https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/debian bookworm InRelease
Err:3 https://packages.sury.org/php bookworm InRelease
  The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
Hit:7 https://nginx.org/packages/mainline/debian bookworm InRelease
Hit:8 https://apt.hestiacp.com bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
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 were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
W: Failed to fetch https://packages.sury.org/php/dists/bookworm/InRelease  The following signatures were invalid: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Thanks for you help.

2

Please use the search function first: Search results for 'B188E2B695BD4743' - Hestia Control Panel - Discourse

3

Looks like the newest thing there is 2024. Its 2026 now, Really don’t put some two year old repository are fixed there trying to keep things updated.

4

I do not understand what you’re trying to say. But habe you tried to update the key as suggested in the posts/previous threads?

5

This is the fix:

curl -sSlo /usr/share/keyrings/sury-keyring.gpg https://packages.sury.org/php/apt.gpg

6

as it was posted in the other threads :man_shrugging: .

7

I think what he meant was that this error first surfaced in 2024, he did not expect it to resurface in 2026 and he was also probably not sure if the same fix applied in 2024 as in now. Recently did an update and saw this error as well, i was confused myself because i remember applying this fix before to the very same server in 2024 and now again in 2026.