Articles in this section

CentOS 7 to AlmaLinux conversion fails in Plesk: Detected unknown GPG keys for target system repositories: http://autoinstall.plesk.com/plesk.gpg

kb: bug kb: fixed Plesk for Linux

Applicable to:

  • Plesk for Linux

Symptoms

  • CentOS 7 to AlmaLinux conversion fails in Plesk.

  • /var/log/leapp/leapp-report.txt says that the Plesk GPG key is missing

    Risk Factor: high (inhibitor)
    Title: Detected unknown GPG keys for target system repositories
    Summary: Some of the target repositories require GPG keys that are not installed in the current RPM DB or are not stored in the /etc/leapp/files/vendors.d/rpm-gpg/,/etc/leapp/repos.d/system_upgrade/common/files/rpm-gpg/8 directory. Leapp is not able to guarantee validity of such gpg keys and manual review is required, so any spurious keys are not imported in the system during the in-place upgrade. The following additional gpg keys are required to be imported during the upgrade:
    - http://autoinstall.plesk.com/plesk.gpg
    Remediation: [hint] Check the path to the listed GPG keys is correct, the keys are valid and import them into the host RPM DB or store them inside on of the , directories prior the upgrade. If you want to proceed the in-place upgrade without checking any RPM signatures, execute leapp with the --nogpgcheck option.
    Key: e7e3f34a530e861b14f1cdd759cb62f92677066f

  • Additional Plesk repositories were added by Plesk extensions

    # grep -iR "plesk.gpg" /etc/yum.repos.d/
    /etc/yum.repos.d/plesk-ext-watchdog.repo:gpgkey=http://autoinstall.plesk.com/plesk.gpg
    /etc/yum.repos.d/plesk-ext-nodejs.repo:gpgkey=http://autoinstall.plesk.com/plesk.gpg
    /etc/yum.repos.d/plesk-ext-panel-migrator.repo:gpgkey=http://autoinstall.plesk.com/plesk.gpg

Cause

This was caused by a product issue, PPPM-14883, and fixed in Plesk Obsidian 18.0.69, released April 15th, 2025 (Linux).

Resolution

   
Update Plesk (recommended)
   

To resolve the issue, update Plesk to the version with the fix: How to install Plesk updates

   
Workaround
   

If updating is not possible, manually download the key or remove the additional extensions and their repositories.

 

Download Plesk GPG Key

  1. Log in to the server over SSH

  2. Create this directory if it doesn't exist: /etc/leapp/files/vendors.d/rpm-gpg/

    # mkdir /etc/leapp/files/vendors.d/rpm-gpg/

  3. Download the key into this directory

    # wget http://autoinstall.plesk.com/plesk.gpg -O /etc/leapp/files/vendors.d/rpm-gpg/plesk.gpg

  4. Run the conversion script

Remove Extensions

  1. Log in to the server over SSH

  2. List the repositories that use the Plesk GPG key

    # grep -r plesk.gpg /etc/yum.repos.d/
    /etc/yum.repos.d/plesk-ext-panel-migrator.repo:gpgkey=http://autoinstall.plesk.com/plesk.gpg
    /etc/yum.repos.d/plesk-ext-watchdog.repo:gpgkey=http://autoinstall.plesk.com/plesk.gpg

  3. Remove the listed extensions from Plesk:

    # plesk bin extension --uninstall watchdog
    # plesk bin extension --uninstall panel-migrator

  4. Run the conversion script

   
Was this article helpful?

Comments

0 comments

Please sign in to leave a comment.