• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved NO_PUBKEY BD11A6AA914BDF7E

U

umara

New Pleskian
Server operating system version
Debian 10.13 x86_64
Plesk version and microupdate number
18.0.51.0
Hey!

I have an issue with package updates. Since couple days I do receive below errors for all repositories:
Code: 
GPG error: http://autoinstall.plesk.com/PHP73_17 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://autoinstall.plesk.com/PMM_0.1.11 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://autoinstall.plesk.com/NODE_0.0.2 all InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
N: Skipping acquire of configured file 'all/binary-amd64/Packages' as repository 'http://autoinstall.plesk.com/pool/WPB_18.0.51_64 all InRelease' doesn't support architecture 'amd64'
W: Failed to fetch http://autoinstall.plesk.com/PSA_18.0.51/dists/buster/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Failed to fetch http://autoinstall.plesk.com/debian/SITEBUILDER_17.8.12/dists/all/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Failed to fetch http://autoinstall.plesk.com/PHP71_17/dists/buster/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Failed to fetch http://autoinstall.plesk.com/PHP72_17/dists/buster/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Failed to fetch http://autoinstall.plesk.com/PHP73_17/dists/buster/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Failed to fetch http://autoinstall.plesk.com/PMM_0.1.11/dists/buster/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Failed to fetch http://autoinstall.plesk.com/NODE_0.0.2/dists/all/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E

I have already tried this:
Code: 
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys BD11A6AA914BDF7E

But received below:
Code: 
Executing: /tmp/apt-key-gpghome.LQ0EIUQgQV/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys BD11A6AA914BDF7E
gpg: keyserver receive failed: No data

I though maybe it is related to gpg version, so installed gpg2, tried this:
Code: 
gpg2  --keyserver keyserver.ubuntu.com --recv-keys BD11A6AA914BDF7E
and received same as above:
Code: 
gpg: keyserver receive failed: No data

Help please.

plesk version output:
Code: 
Product version: Plesk Obsidian 18.0.51.0
     OS version: Debian 10.13 x86_64
     Build date: 2023/03/10 09:00
       Revision: 7de3d6afacb31f7ca7bdc07684f3b689cb7b0ef6
 
Just checked /var/log/plesk/install/autoinstaller3.log
The issue started after upgrade from Plesk Obsidian 18.0.50 to 18.0.51
 
There are two issues mentioned in your thread.

1) Your system claims that Web Presence Builder cannot be installed "... repository 'Index of /pool/WPB_18.0.51_64 all InRelease' doesn't support architecture 'amd64'". However, I spun up a test instance Debian 10 and installed Web Presence Builder there without issues and was also able to use it after installation. I do not know why this does not work on your system.

2) Missing keys. For that we have a KB article: https://support.plesk.com/hc/en-us/articles/360006278554
Please make sure to not simply copy the examples given there, but to enter the BD11A6AA914BDF7E key from your error messages and the correct key server. I am not a Debian expert, but in your post above you are trying to address an Ubuntu repository. I am not sure if that should not be keyring.debian.org instead. Maybe a Debian specialist on here can help us out which server is correct.

This again raises the suspicion in me that your repositories might be a mixture of Ubuntu and Debian repositories? That could cause the WPB issue maybe.
 
Hey Peter, thank you for the answer.
I am sorry I forgot to add I've tried keyring.debian.org however it finished with output
Code: 
No name

In sources list I have only official Plesk repos for Debian 10.
 
Little update. I made typo in command for debian keyring server. Instead of keyring.debian.org typed debian.keyring.org which, obviously, did not work.
So tried again:
Code: 
sudo apt-key adv --keyserver keyring.debian.org --recv-keys BD11A6AA914BDF7E
Executing: /tmp/apt-key-gpghome.dBVBqDHUWm/gpg.1.sh --keyserver keyring.debian.org --recv-keys BD11A6AA914BDF7E
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

Still no luck. Today, after morning cofee, I searched again this forum and found similar topic (but with Ubuntu server), where also user is facing issue with same key in Plesk Obsidian 18.0.51 -> CLICK

Instructions from this KB did not solve issue

When I did
Code: 
apt --allow-unauthenticated upgrade
then packages installed. However I would like to avoid doing updates this way.
 
Peter Debik said:
There are two issues mentioned in your thread.

1) Your system claims that Web Presence Builder cannot be installed "... repository 'Index of /pool/WPB_18.0.51_64 all InRelease' doesn't support architecture 'amd64'".
Click to expand...
Well, it doesn't. It supports x86_64. There seems to be some confusion about arch vs. os_arch.

Peter Debik said:
2) Missing keys. For that we have a KB article: https://support.plesk.com/hc/en-us/articles/360006278554
Please make sure to not simply copy the examples given there, but to enter the BD11A6AA914BDF7E key from your error messages and the correct key server. I am not a Debian expert, but in your post above you are trying to address an Ubuntu repository. I am not sure if that should not be keyring.debian.org instead. Maybe a Debian specialist on here can help us out which server is correct.
Click to expand...
This is not a debian key issue however, but a plesk pgp key issue, as all the repositories involved are plesk's. Maybe a leftover from the botched grafana key update?

It seems plesk itself messed around with the keys, because in /etc/apt/trusted.gpg.d/, I see this:
-rw-r--r-- 1 root root 1151 Mar 30 06:25 plesk.gpg~
6:25 is the time plesk's updater runs, so apparently plesk's updater sabotaged itself.
 
And btw, plesk still doesn't show dist-upgrades. /admin/pum/updates-list says

All packages are up-to-date​

Checked on Mar 30, 2023 10:47 AM

but apt-get upgrade says

The following packages have been kept back:
linux-image-amd64
 
Okay, I think I know what happened:
Starting with the upgrade to 18.0.49, plesk explicitly pins the pgp key for the plesk repositories:
Code: 
add line 'deb [signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/pool/PSA_18.0.49_10759/ bullseye all' to temporary source list '/etc/apt/sources.list.d/50sw_autoinstaller.list'
add line 'deb [signed-by=/etc/apt/keyrings/plesk.gpg] http://autoinstall.plesk.com/pool/PSA_18.0.49_10759/ bullseye extras' to persistent source list '/etc/apt/sources.list.d/plesk.list'
...

The key is put in that new location created on that upgrade that is not normally searched by apt.

Now there are some entries in sources.list inserted before the deb9->10 upgrade according to the instructions in https://support.plesk.com/hc/en-us/...upgrade-procedure-on-Linux-server-with-Plesk- that are still active:
Code: 
deb [arch=amd64] http://autoinstall.plesk.com/PMM_0.1.11 buster all
deb [arch=amd64] http://autoinstall.plesk.com/NODE_0.0.2 all all
deb [arch=amd64] http://autoinstall.plesk.com/RUBY_0.0.2 buster all
Those are now changed to bullseye, but have not been altered to use the new key location.

Now it seems that in the upgrade to 18.0.51, the key in /etc/apt/trusted.gpg.d/ was deactivated (moved to plesk.gpg~, see above).
This broke package signing for the three lines above that do not have the new key location, as apt doesn't search that location on its own.

The upgrade guide should be updated to reflect the current sources.list[.d] layout with instructions .
I guess the three lines can be safely removed?
(some more lines for OP, and I think they have an [arch=amd64] in the WPB line that needs to be removed)
 
umara said:
Topic can be closed. I have resolved issue by doing this:
Code: 
sudo wget http://autoinstall.plesk.com/plesk.gpg && apt-key add plesk.gpg
sudo apt clean
sudo apt update
Click to expand...
Yes, this helps -- but only for 1 day -- then the messages come again
 
@B3 Support I can only encourage you to open a support ticket an tell support to also look into PPS-14261. Developers need system access to find the root cause of the issue. So far many people are talking about it, but it seems that suitable access has not been provided so we cannot provide better support than the existing known workaround. It would be helpful if support could check this and if the solution could then be reported back here.
 
Peter Debik said:
@B3 Support I can only encourage you to open a support ticket an tell support to also look into PPS-14261. Developers need system access to find the root cause of the issue. So far many people are talking about it, but it seems that suitable access has not been provided so we cannot provide better support than the existing known workaround. It would be helpful if support could check this and if the solution could then be reported back here.
Click to expand...
I understand that developers need access to such a system. However, this is usually not really possible for privacy reasons. We are happy to provide the relevant information - but we cannot provide blank access to one of the affected systems.
 
Code: 
:/etc/apt/trusted.gpg.d# ls -trla
total 28
-rw-r--r-- 1 root root 1733 Mär 29  2021 ubuntu-keyring-2018-archive.gpg
-rw-r--r-- 1 root root 2794 Mär 29  2021 ubuntu-keyring-2012-cdimage.gpg
-rw-r--r-- 1 root root 2796 Mär 29  2021 ubuntu-keyring-2012-archive.gpg
-rw-r--r-- 1 root root  360 Apr  3 13:59 ondrej_ubuntu_php.gpg
-rw-r--r-- 1 root root 1151 Apr 28 06:25 plesk.gpg~
drwxr-xr-x 2 root root 4096 Apr 28 06:25 .
drwxr-xr-x 8 root root 4096 Apr 28 06:25 ..
it seems that this is also a possible cause of the problem.
Code: 
:/etc/apt/trusted.gpg.d# ls -trla /etc/apt/keyrings
total 16
-rw-r--r-- 1 root root 1151 Apr 27 06:33 plesk-ext-grafana.gpg
-rw-r--r-- 1 root root 1151 Apr 28 06:25 plesk.gpg
drwxr-xr-x 8 root root 4096 Apr 28 06:25 ..
drwxr-xr-x 2 root root 4096 Apr 28 06:25 .
no "diff"
Code: 
diff plesk.gpg~ /etc/apt/keyrings/plesk.gpg
 
I’m trying to solve this issue and nothing i do is working at all. I host at Strato so i cant do a support ticket and Strato does not know anything. Even the workarounds are not working.
 
The support at Strato is in principle never a help. I have had to experience this several times.
Which file generates the error for you? I have a Strato server myself and have already successfully solved the problems.
 
When i do “plesk installer update” i get errors the first one is:

Code: 
Err:2 http://autoinstall.plesk.com/NODE_0.0.2 all InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
Code: 
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://autoinstall.plesk.com/NODE_0.0.2 all InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Failed to fetch http://autoinstall.plesk.com/NODE_0.0.2/dists/all/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
W: Some index files failed to download. They have been ignored, or old ones used instead.
Warning: not connected 'multiverse' repository section

what ever i try i cant solve it. In the documentation its said that version 18.0.53 solves the issue but i’m on 18.0.52 and cant upgrade. I have even tried skipping the checksums but that did not work. I tried the add-key but then it comes back with no data. This is a mess created by plesk but there not solving the underlaying issue by uploading the key somewhere.
 
You must log in or register to reply here.

Similar threads

brainforge
Resolved System updates have started failing.
Replies
2
Views
347
brainforge
brainforge
W
Resolved An error occurred during the signature verification
Replies
2
Views
8K
Wongle
W
S
Resolved error 'problems with system updates'
Replies
2
Views
807
Peter Debik
P
Q
Issue have problem with update
Replies
3
Views
945
GwenDragon
G
Daveo
Resolved Can't install Grafana extension update
Replies
17
Views
4K
Cosmin Truta
C
Back
Top