Resolved error occurred during the signature verification

[yohanr]

Hello, @yohanr . From what I can see the error you are getting is related to CloudLinux's repository. They are aware of the issue and a fix should be introduced soon. You may apply the workaround mentioned previously:

indeed this worked, thank you

 

[Zalem Citizen]

Hi all,

Same issue here... but for Imunify360.

2025-06-02 06:25:27 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
/usr/lib/python3/dist-packages/apt/cache.py:562: Warning: W:An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /imunify360/ubuntu/24.04/ noble InRelease: The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024), W:An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /ubuntu/24.04/slot-1/ noble InRelease: The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71

And when I try to check for package updates in Plesk I get 'Error: Unable to receive update information for the package(s)'.

Total newbie here but wondering if the apt update list cache needs to be cleared? Don't want to try it until someone who knows what they are doing advises!

Thanks!

Same issue here for Imunify360

# apt update
...
Err:22 https://repo.imunify360.cloudlinux.com/imunify360/ubuntu/24.04 noble InRelease
  The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
Fetched 525 kB in 2s (323 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.imunify360.cloudlinux.com/imunify360/ubuntu/24.04 noble InRelease: The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
...
W: Failed to fetch https://repo.imunify360.cloudlinux.com/imunify360/ubuntu/24.04/dists/noble/InRelease  The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
W: Some index files failed to download. They have been ignored, or old ones used instead.
N: Missing Signed-By in the sources.list(5) entry for 'http://nova.clouds.archive.ubuntu.com/ubuntu'
N: Missing Signed-By in the sources.list(5) entry for 'http://nova.clouds.archive.ubuntu.com/ubuntu'

 

[Tjerk Visser]

Hi all, here also still recieving these errors

/etc/cron.daily/drweb-update:
ERROR: Dr.Web Updater: failed to download files !
run-parts: /etc/cron.daily/drweb-update exited with return code 105

And

2025-06-06 06:25:28 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
/usr/lib/python3/dist-packages/apt/cache.py:562: Warning: W:An error occurred during the signature verification

Advise please

Regards Tjerk

 

[Sebahat.hadzhi]

@Zalem Citizen As previously mentioned, CloudLinux is are aware of the issue and working on fixing it. However, I cannot provide any ETA on when that will be fixed. At this time, you can safely ignore the warnings.

@Tjerk Visser the issue you are reporting about Dr Web's update is significantly different than the one discussed in here. Kindly refer to this thread.

 

[carlsson]

I just want to confirm; I also have errors since two weeks and it looks like this:

Hello,
There was an issue with updating system packages and third-party components on the nnn.se server. Please wait for the next automatic update or run the update manually: https://nnn.se/admin/pum

Reason: 2025-06-12 06:25:31 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2025-06-12 06:25:35 ERROR: Apt cache fetch failed. Try to run the `apt-get update` command.
2025-06-12 06:25:35 ERROR:
2025-06-12 06:25:35 ERROR: Exited with returncode 1.

Doing the apt-get update in the terminal gives a "public key is not available: NO_PUBKEY E9299045CE550E57" error.

Is this the same error or something else? It just started two weeks ago without any obvious reason.

 

[a-plesk-forum]

Hello,
I have the same issue, on two independent Plesk instances (one Debian 11, second Debian 12), both start sending the same error regarding PUM at the same day.

Any thoughts ? Just waits another week for Plesk update ? I see that due to this I cannot update the whole repo

in sudo apt-get update I see Grafana as root cause



In advance, thank you for any help, guideline, or how to solve it ease&safe

Regards
Artur

 

[a-plesk-forum]

Solved on OS: Debian 11.11 Product: Plesk Obsidian 18.0.70 Update #1

by using below in Terminal

wget -q -O - http://autoinstall.plesk.com/plesk.gpg | gpg --dearmor > /etc/apt/keyrings/plesk-ext-grafana.gpg