• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved package cannot be loaded

Stefan Reiser

New Pleskian
Hello everybody,

I have a new Linux server with current Plesk license:

Version Plesk Onyx v17.8.11_build1708180613.11 os_Ubuntu 18.04
OS Ubuntu 18.04.1 LTS

and during the automatic update the following error message appears regularly and the package cannot be loaded:

Fehler: Paketliste konnte nicht abgerufen werden: 2019-02-12 12:12:10 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2019-02-12 12:12:11 ERROR: W:GPG error: Index of /imunify360/ubuntu/16.04 xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C55A6628608CB71, E:The repository 'Index of /imunify360/ubuntu/16.04 xenial InRelease' is not signed. 2019-02-12 12:12:11 ERROR: Exited with returncode 1.

I connect to the server via SSH and run :

#plesk bin license --retrieve

the message:

Updating Plesk license key: [2019-02-12 12:03:54.543] ERR [panel] 2019-02-12 12:03:53 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2019-02-12 12:03:54 ERROR: W:GPG error: Index of /imunify360/ubuntu/16.04 xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C55A6628608CB71, E:The repository 'Index of /imunify360/ubuntu/16.04 xenial InRelease' is not signed.
2019-02-12 12:03:54 ERROR: Exited with returncode 1.
Done
[2019-02-12 12:03:59.118] ERR [panel] 2019-02-12 12:03:57 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2019-02-12 12:03:59 ERROR: W:GPG error: Index of /imunify360/ubuntu/16.04 xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C55A6628608CB71, E:The repository 'Index of /imunify360/ubuntu/16.04 xenial InRelease' is not signed.
2019-02-12 12:03:59 ERROR: Exited with returncode 1.
[2019-02-12 12:04:03.582] ERR [panel] 2019-02-12 12:04:01 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2019-02-12 12:04:03 ERROR: W:GPG error: Index of /imunify360/ubuntu/16.04 xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C55A6628608CB71, E:The repository 'Index of /imunify360/ubuntu/16.04 xenial InRelease' is not signed.
2019-02-12 12:04:03 ERROR: Exited with returncode 1.
Updating license key EXT.05234197.0000: [2019-02-12 12:04:07.526] ERR [panel] 2019-02-12 12:04:05 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2019-02-12 12:04:07 ERROR: W:GPG error: Index of /imunify360/ubuntu/16.04 xenial InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C55A6628608CB71, E:The repository 'Index of /imunify360/ubuntu/16.04 xenial InRelease' is not signed.
2019-02-12 12:04:07 ERROR: Exited with returncode 1.
Done
 
Yes, I did. It comes Internal Error. See logs of detail.
Only I don't find the logfiles. I looked under var/log and expected a directory imunify360 there. Only found the file i360deploy.log.

It says:
Failed (code: 1)
Failed (code: 1)


I want to be able to call my packages normally via plesk.


my Linux is
OS Ubuntu 18.04.1 LTS
and the Error message W:GPG error: Index of /imunify360/ubuntu/16.04 why 16.04?

Best regards stefan

PS.I hope you can read everything, translated it with deepl.com.
 
Who also has this problem, please proceed as follows:

Check if the file /etc/apt/sources.list.d/imunify360* files exists? Should this be the case then delete it and it should work again.

Thank you for your time.
 
Deleting the sources to avoid warnings about the missing public keys to verify the signatures is an interesting way of solving this issue :eek:.

The better approach would be to install the key, if you are using Imunify360:

Code:
wget -O RPM-GPG-KEY-CloudLinux https://repo.imunify360.cloudlinux.com/defense360/RPM-GPG-KEY-CloudLinux
apt-key add RPM-GPG-KEY-CloudLinux
 
Back
Top