Resolved GPG Key Error When Installing site-import Extension on Ubuntu Jammy (22.04)

[X3Web]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

18.0.67

GPG Key Error When Installing site-import Extension on Ubuntu Jammy (22.04)

 

[X3Web]

Hi Plesk Community,

I’ve been trying to install the site-import extension on a server running Ubuntu Jammy (22.04) with Plesk Obsidian, and I’m encountering persistent issues with GPG key verification. Despite following various troubleshooting steps, the installation fails due to a missing GPG key (BD11A6AA914BDF7E). Below is a detailed explanation of the issue and the steps I’ve tried.

---

Error Summary​

Whenever I attempt to install the site-import extension, the installation fails during the post-install.php execution with the following errors:

W: GPG error: Index of /PMM_1.0.0 jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
E: Failed to fetch https://autoinstall.plesk.com/PMM_1.0.0/dists/jammy/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E

The post-install.php script appears to fail during the "Bootstrapping dependencies" step, unable to fetch the required repository packages due to this key issue.

---

What I've Tried​

Here’s what I’ve done so far to try to resolve the problem:

1. Added the Plesk GPG Key
   • Downloaded the Plesk GPG key and added it using various methods:
     wget -qO - https://autoinstall.plesk.com/plesk.gpg | gpg --dearmor -o /usr/share/keyrings/plesk.gpg
     Ensured permissions are correct:
     sudo chmod 644 /usr/share/keyrings/plesk.gpg
     Updated Repository Configuration
     • Modified /etc/apt/sources.list.d/plesk.list to use the signed-by attribute:
       deb [signed-by=/usr/share/keyrings/plesk.gpg] Index of /PSA_18.0.67 jammy all
       deb [signed-by=/usr/share/keyrings/plesk.gpg] Index of /PMM_1.0.0 jammy all
2. Attempted a Bypass with trusted=yes
   • As a workaround, I modified the repository to bypass signature verification:
     deb [trusted=yes] Index of /PSA_18.0.67 jammy all
     deb [trusted=yes] Index of /PMM_1.0.0 jammy all
     Unfortunately, this did not resolve the issue either.
3. Manually Installed the Extension
   • Downloaded the extension ZIP file and tried installing it manually:
     plesk bin extension --install ./site-import-1.8.13-2255.zip
     This also fails with the same error during the execution of post-install.php.
4. Cleared and Refreshed Package Cache
   • Cleaned the apt cache and manually removed old keys:
     sudo apt-get clean
     sudo rm -rf /var/lib/apt/lists/*
     sudo apt-key del BD11A6AA914BDF7E
5. Reviewed the post-install.php Script
   • Examined /opt/psa/admin/plib/modules/site-import/scripts/post-install.php but could not identify a clear way to skip or bypass the dependency step without breaking the extension.

---

Environment Details​

• OS: Ubuntu 22.04 (Jammy)
• Plesk Version: Obsidian 18.0.67
• Extension: site-import version 1.8.13-2255
• Repository URLs:
  • Index of /PSA_18.0.67
  • Index of /PMM_1.0.0

---

Request for Assistance​

I’m looking for guidance on the following:

1. Why the Plesk GPG key (BD11A6AA914BDF7E) is not being recognized despite being added to /usr/share/keyrings.
2. How to successfully bypass or resolve the repository signature verification during the post-install.php step.
3. Any manual workaround to install the required dependencies and complete the extension installation.

If anyone has encountered this issue or has a proven fix, your help would be greatly appreciated!

Thanks in advance for your assistance!

 

[X3Web]

Hi everyone,

I managed to resolve the persistent GPG key error when installing the site-import extension on Ubuntu Jammy (22.04). Here's the detailed fix, step by step:

---

Issue​

The installation of the site-import extension was failing due to GPG key verification errors. APT was misusing the Plesk GPG key (BD11A6AA914BDF7E), causing repository signature verification issues.

Errors included:

W: GPG error: https://autoinstall.plesk.com/PMM_1.0.0 jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY BD11A6AA914BDF7E
E: Failed to fetch https://autoinstall.plesk.com/PMM_1.0.0/dists/jammy/InRelease

---

Solution​

Step 1: Remove the Misplaced Plesk Key​

The Plesk GPG key was mistakenly placed in the global keyring directory (/etc/apt/trusted.gpg.d/), causing APT to attempt to use it for unrelated repositories. To fix this:
sudo rm /etc/apt/trusted.gpg.d/plesk.gpg

---

Step 2: Place the Plesk Key in the Correct Directory​

Store the Plesk GPG key in the dedicated /etc/apt/keyrings/ directory to ensure it's only used for the Plesk repository.

1. Create the keyrings directory:
   sudo mkdir -p /etc/apt/keyrings
2. Download and save the Plesk key:
   curl -fsSL https://autoinstall.plesk.com/plesk.gpg | sudo gpg --dearmor -o /etc/apt/keyrings/plesk.gpg

Step 3: Verify the Plesk Repository Configuration​

Ensure the Plesk repository is properly configured to use its specific GPG key.

1. Open the Plesk repository file:
   sudo nano /etc/apt/sources.list.d/plesk.list
2. Update it to include:
   deb [signed-by=/etc/apt/keyrings/plesk.gpg] https://autoinstall.plesk.com/PSA_18.0.66 focal all
3. Save and exit.

---

Step 4: Update APT and Verify​

Finally, refresh APT to ensure everything works correctly:
sudo apt update

What to expect:

• The warnings about the Plesk GPG key in /etc/apt/trusted.gpg.d/ will no longer appear.
• The package lists should update without errors.

 

[Daveo]

1. Update it to include:
   deb [signed-by=/etc/apt/keyrings/plesk.gpg] https://autoinstall.plesk.com/PSA_18.0.66 focal all

Change PSA_18.0.66 to 18.0.67 or whatever Plesk version you are using.