Resolved PUM error persists....

J

Jeroentje

New Pleskian
Server operating system version
Ubuntu 24.04.1 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.67 Update #2
Hello everyone,

I'm pretty new at Plesk. I got this PUM error while updating my Ubuntu 24.04.1 LTS server with Plesk Obsidian 18.0.67 Update #2
Got the error for a month now, I searched the internet and found more than one post about it, but no solution. I did everything that was offered but with no results..
Can someone help me ?


root@webserver:~# apt update
Hit:1 Index of /pool/PSA_18.0.67_16338 noble InRelease
Hit:2 Index of /RUBY_0.0.2 noble InRelease
Hit:3 Index of /PHP74_17 noble InRelease
Hit:4 https://dl.google.com/linux/chrome/deb stable InRelease
Hit:5 Index of /PHP80_17 noble InRelease
Hit:6 Index of /PHP81_17 noble InRelease
Hit:7 Index of /grafana/deb stable InRelease
Hit:8 Index of /PHP82_17 noble InRelease
Hit:9 Index of /DRWEB_6.0.2.9 noble InRelease
Hit:10 Index of /PHP83_17 noble InRelease
Hit:11 Index of /PHP84_17 noble InRelease
Hit:12 Index of /pool/WPB_18.0.59_78 all InRelease
Get:13 Index of /kernelcare-ubuntu/24.04/ noble InRelease [1896 B]
Hit:14 Index of /ubuntu noble InRelease
Ign:15 https://storage.googleapis.com/download.dartlang.org/linux/debian stable InRelease
Hit:16 Index of /ubuntu noble-security InRelease
Hit:17 Index of /ubuntu noble-updates InRelease
Hit:18 https://storage.googleapis.com/download.dartlang.org/linux/debian stable Release
Hit:19 Index of /ubuntu noble-backports InRelease
Err:13 Index of /kernelcare-ubuntu/24.04/ noble InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6DC3D600CDEF74BB
Reading package lists... Done
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
W: http://autoinstall.plesk.com/pool/PSA_18.0.67_16338/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/RUBY_0.0.2/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP74_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP80_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP81_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: https://autoinstall.plesk.com/grafana/deb/dists/stable/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP82_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: https://autoinstall.plesk.com/DRWEB_6.0.2.9/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP83_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP84_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/pool/WPB_18.0.59_78/dists/all/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: GPG error: Index of /kernelcare-ubuntu/24.04/ noble InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6DC3D600CDEF74BB
E: The repository 'Index of /kernelcare-ubuntu/24.04/ noble 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.
 
Thank you for your reply. I read the this should be fixed in 18.0.67 however, I already run plesk 18.0.67 update #2

And there is definitely an error which stops the whole process.

Err:13 Index of /kernelcare-ubuntu/24.04/ noble InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6DC3D600CDEF74BB
 
AYamshanov said:
My colleague has helped me to find this KB article, https://support.plesk.com/hc/en-us/...use-the-public-key-is-not-available-NO-PUBKEY
Click to expand...
already tried this :-(

root@webserver:~# gpg --keyserver keyserver.ubuntu.com --recv-keys 6DC3D600CDEF74BB
gpg: key 6DC3D600CDEF74BB: "KernelCare <[email protected]>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
root@webserver:~# apt-get clean

error still occurs

root@webserver:~# apt-get update
Hit:1 Index of /RUBY_0.0.2 noble InRelease
Hit:2 Index of /pool/PSA_18.0.67_16313 noble InRelease
Hit:3 Index of /PHP74_17 noble InRelease
Hit:4 Index of /PHP81_17 noble InRelease
Get:5 https://dl.google.com/linux/chrome/deb stable InRelease [1825 B]
Hit:6 Index of /PHP82_17 noble InRelease
Hit:7 Index of /grafana/deb stable InRelease
Hit:8 Index of /PHP83_17 noble InRelease
Hit:9 Index of /DRWEB_6.0.2.9 noble InRelease
Hit:10 Index of /ubuntu noble InRelease
Ign:11 https://storage.googleapis.com/download.dartlang.org/linux/debian stable InRelease
Get:12 Index of /kernelcare-ubuntu/24.04/ noble InRelease [1896 B]
Hit:13 Index of /ubuntu noble-security InRelease
Get:14 Index of /ubuntu noble-updates InRelease [126 kB]
Hit:15 https://storage.googleapis.com/download.dartlang.org/linux/debian stable Release
Get:16 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1209 B]
Hit:17 Index of /ubuntu noble-backports InRelease
Err:12 Index of /kernelcare-ubuntu/24.04/ noble InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6DC3D600CDEF74BB
Reading package lists... Done
W: http://autoinstall.plesk.com/RUBY_0.0.2/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/pool/PSA_18.0.67_16313/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP74_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP81_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP82_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: https://autoinstall.plesk.com/grafana/deb/dists/stable/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP83_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: https://autoinstall.plesk.com/DRWEB_6.0.2.9/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: GPG error: Index of /kernelcare-ubuntu/24.04/ noble InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 6DC3D600CDEF74BB
E: The repository 'Index of /kernelcare-ubuntu/24.04/ noble 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.
root@webserver:~#
 
root@webserver:/etc/apt/sources.list.d# ls -l
total 32
-rw-r--r-- 1 root root 134 Feb 10 16:31 dart_stable.list
-rw-r--r-- 1 root root 190 Feb 10 16:22 google-chrome.list
-rw-r--r-- 1 root root 126 Jan 7 17:13 kcare.list
-rw-r--r-- 1 root root 110 Jan 3 16:29 plesk-ext-grafana.list
-rw-r--r-- 1 root root 124 Jan 29 06:32 plesk-ext-premium-av.list
-rw-r--r-- 1 root root 105 Jan 3 05:05 plesk-ext-ruby.list
-rw-r--r-- 1 root root 533 Feb 13 06:25 plesk.list
-rw-r--r-- 1 root root 2988 Feb 10 16:33 ubuntu.sources


and the content of:
root@webserver:/etc/apt/sources.list.d# cat ubuntu.sources
## Note, this file is written by cloud-init on first boot of an instance
## modifications made here will not survive a re-bundle.
##
## If you wish to make changes you can:
## a.) add 'apt_preserve_sources_list: true' to /etc/cloud/cloud.cfg
## or do the same in user-data
## b.) add supplemental sources in /etc/apt/sources.list.d
## c.) make changes to template file
## /etc/cloud/templates/sources.list.ubuntu.deb822.tmpl
##

# See UpgradeNotes - Community Help Wiki for how to upgrade to
# newer versions of the distribution.

## Ubuntu distribution repository
##
## The following settings can be adjusted to configure which packages to use from Ubuntu.
## Mirror your choices (except for URIs and Suites) in the security section below to
## ensure timely security updates.
##
## Types: Append deb-src to enable the fetching of source package.
## URIs: A URL to the repository (you may add multiple URLs)
## Suites: The following additional suites can be configured
## <name>-updates - Major bug fix updates produced after the final release of the
## distribution.
## <name>-backports - software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
## Components: Aside from main, the following components can be added to the list
## restricted - Software that may not be under a free license, or protected by patents.
## universe - Community maintained packages. Software in this repository receives maintenance
## from volunteers in the Ubuntu community, or a 10 year security maintenance
## commitment from Canonical when an Ubuntu Pro subscription is attached.
## multiverse - Community maintained of restricted. Software from this repository is
## ENTIRELY UNSUPPORTED by the Ubuntu team, and may not be under a free
## licence. Please satisfy yourself as to your rights to use the software.
## Also, please note that software in multiverse WILL NOT receive any
## review or updates from the Ubuntu security team.
##
## See the sources.list(5) manual page for further settings.
Types: deb
URIs: Index of /ubuntu
Suites: noble noble-updates noble-backports
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

## Ubuntu security updates. Aside from URIs and Suites,
## this should mirror your choices in the previous section.
Types: deb
URIs: Index of /ubuntu
Suites: noble-security
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
 
Jeroentje said:
and the content of:
Click to expand...
What do you have in the /etc/apt/sources.list.d/kcare.list file?

On a test server, I see
Bash: 
# grep -Ri kernelcare /etc/apt/
/etc/apt/sources.list.d/kcare.list:deb [arch=amd64,arm64 signed-by=/usr/share/keyrings/kcare.gpg] https://repo.cloudlinux.com/kernelcare-ubuntu/24.04 noble main

# ls -la /usr/share/keyrings/kcare.gpg
-rw-r--r-- 1 root root 2335 Jan 31 07:00 /usr/share/keyrings/kcare.gpg
 
aha..
no there isn't

root@webserver:/usr/share/keyrings# ls -l
total 72
-rw-r--r-- 1 root root 13978 Feb 10 16:30 dart.gpg
-rw-r--r-- 1 root root 1160 Jan 22 15:40 kernelcare.gpg
-rw-r--r-- 1 root root 3607 Nov 26 2023 ubuntu-archive-keyring.gpg
-rw-r--r-- 1 root root 1227 Nov 26 2023 ubuntu-archive-removed-keys.gpg
-rw-r--r-- 1 root root 2444 Nov 26 2023 ubuntu-cloudimage-keyring.gpg
-rw-r--r-- 1 root root 0 Nov 26 2023 ubuntu-cloudimage-removed-keys.gpg
-rw-r--r-- 1 root root 1191 Nov 26 2023 ubuntu-master-keyring.gpg
-rw-r--r-- 1 root root 1150 Aug 8 2024 ubuntu-pro-anbox-cloud.gpg
-rw-r--r-- 1 root root 2247 Aug 8 2024 ubuntu-pro-cc-eal.gpg
-rw-r--r-- 1 root root 2274 Aug 8 2024 ubuntu-pro-cis.gpg
-rw-r--r-- 1 root root 2236 Aug 8 2024 ubuntu-pro-esm-apps.gpg
-rw-r--r-- 1 root root 2264 Aug 8 2024 ubuntu-pro-esm-infra.gpg
-rw-r--r-- 1 root root 2275 Aug 8 2024 ubuntu-pro-fips-preview.gpg
-rw-r--r-- 1 root root 2275 Aug 8 2024 ubuntu-pro-fips.gpg
-rw-r--r-- 1 root root 2250 Aug 8 2024 ubuntu-pro-realtime-kernel.gpg
-rw-r--r-- 1 root root 2235 Aug 8 2024 ubuntu-pro-ros.gpg
root@webserver:/usr/share/keyrings#
 
Jeroentje said:
aha..
no there isn't

root@webserver:/usr/share/keyrings# ls -l
total 72
-rw-r--r-- 1 root root 13978 Feb 10 16:30 dart.gpg
-rw-r--r-- 1 root root 1160 Jan 22 15:40 kernelcare.gpg
-rw-r--r-- 1 root root 3607 Nov 26 2023 ubuntu-archive-keyring.gpg
-rw-r--r-- 1 root root 1227 Nov 26 2023 ubuntu-archive-removed-keys.gpg
-rw-r--r-- 1 root root 2444 Nov 26 2023 ubuntu-cloudimage-keyring.gpg
-rw-r--r-- 1 root root 0 Nov 26 2023 ubuntu-cloudimage-removed-keys.gpg
-rw-r--r-- 1 root root 1191 Nov 26 2023 ubuntu-master-keyring.gpg
-rw-r--r-- 1 root root 1150 Aug 8 2024 ubuntu-pro-anbox-cloud.gpg
-rw-r--r-- 1 root root 2247 Aug 8 2024 ubuntu-pro-cc-eal.gpg
-rw-r--r-- 1 root root 2274 Aug 8 2024 ubuntu-pro-cis.gpg
-rw-r--r-- 1 root root 2236 Aug 8 2024 ubuntu-pro-esm-apps.gpg
-rw-r--r-- 1 root root 2264 Aug 8 2024 ubuntu-pro-esm-infra.gpg
-rw-r--r-- 1 root root 2275 Aug 8 2024 ubuntu-pro-fips-preview.gpg
-rw-r--r-- 1 root root 2275 Aug 8 2024 ubuntu-pro-fips.gpg
-rw-r--r-- 1 root root 2250 Aug 8 2024 ubuntu-pro-realtime-kernel.gpg
-rw-r--r-- 1 root root 2235 Aug 8 2024 ubuntu-pro-ros.gpg
root@webserver:/usr/share/keyrings#
Click to expand...
where can I get this missing key ?
 
You're a hero !! , This worked ! now only getting the warning, but I can upgrade .
Thank you so much !

root@webserver:/usr/share/keyrings# apt update
Hit:1 Index of /RUBY_0.0.2 noble InRelease
Hit:2 Index of /pool/PSA_18.0.67_16313 noble InRelease
Hit:3 Index of /PHP74_17 noble InRelease
Hit:4 Index of /PHP81_17 noble InRelease
Hit:5 Index of /PHP82_17 noble InRelease
Hit:6 Index of /ubuntu noble-security InRelease
Hit:7 Index of /PHP83_17 noble InRelease
Hit:8 Index of /grafana/deb stable InRelease
Hit:9 Index of /DRWEB_6.0.2.9 noble InRelease
Hit:10 https://dl.google.com/linux/chrome/deb stable InRelease
Ign:11 https://storage.googleapis.com/download.dartlang.org/linux/debian stable InRelease
Get:12 Index of /kernelcare-ubuntu/24.04/ noble InRelease [1896 B]
Hit:13 Index of /ubuntu noble InRelease
Hit:14 Index of /ubuntu noble-updates InRelease
Hit:15 https://storage.googleapis.com/download.dartlang.org/linux/debian stable Release
Hit:16 Index of /ubuntu noble-backports InRelease
Get:17 Index of /kernelcare-ubuntu/24.04/ noble/main amd64 Packages [1365 B]
Get:18 Index of /kernelcare-ubuntu/24.04/ noble/main arm64 Packages [1328 B]
Fetched 4589 B in 1s (4325 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: http://autoinstall.plesk.com/RUBY_0.0.2/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/pool/PSA_18.0.67_16313/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP74_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP81_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP82_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: http://autoinstall.plesk.com/PHP83_17/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: https://autoinstall.plesk.com/grafana/deb/dists/stable/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: https://autoinstall.plesk.com/DRWEB_6.0.2.9/dists/noble/InRelease: Signature by key 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E uses weak algorithm (dsa1024)
W: https://repo.cloudlinux.com/kernelcare-ubuntu/24.04/dists/noble/InRelease: Signature by key E58FE9B3FE3B0470525159BD6DC3D600CDEF74BB uses weak algorithm (dsa1024)
 
You must log in or register to reply here.

Similar threads

C
Issue apt cache fetch failed / Package update manager notification
Replies
6
Views
2K
carlos.pacheco@nanode
C
A
Issue apt cache fetch failed / Package update manager notification
Replies
5
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
M
Resolved error occurred during the signature verification
2
Replies
26
Views
8K
a-plesk-forum
A
Gerzam73
Resolved Error update Ext Inmunify AV
Replies
2
Views
982
Gerzam73
Gerzam73
nic00
Issue Apt get update + curl error + lot of bug
Replies
1
Views
2K
Sebahat.hadzhi
Sebahat.hadzhi
Back
Top