• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Resolved The repository 'https://autoinstall.plesk.com/grafana/deb stable InRelease' is not signed

learning_curve

Golden Pleskian
Server operating system version
Ubuntu 24.04.2 LTS
Plesk version and microupdate number
18.0.70
Previous issues with Grafana / Monitoring & Plesk are numerous and have been posted by many.
Fortunately, we've had minimum problems with both to date, but it seems our time has finally come, with the advent of Plesk Obsidian 18.0.70 :D
The Grafana Extention auto-update via Plesk Panel just errors out, so we removed it via CLI, cleaned up and the important parts (from all of the errors), are:
Bash:
plesk bin extension --install grafana
ERR [extension/grafana] The execution of post-install.php has failed with the following message:
ERR [extension/grafana] Execution repository has failed with exit code 1, stdout: , stderr: gpg: keybox '/tmp/tmp1z59bopn.plesk.gpg.home/pubring.kbx' created
~~
ERROR:root:Unable to create repository configuration: apt-get failed to perform update
W: GPG error: https://autoinstall.plesk.com/grafana/deb stable InRelease: The following signatures were invalid: 8BADC1A02FC9C07FB8C20EC0BD11A6AA914BDF7E (untrusted public key algorithm: dsa1024)
E: The repository 'https://autoinstall.plesk.com/grafana/deb stable InRelease' is not signed.
~~
Meantime, again in CLI, we've removed both Grafana and Monitoring to avoid lots of repetitive errors during normal updates
FWIW The plesk-ext-grafana.list content is shown below and plesk-ext-grafana.gpg does exist in /etc/apt/keyrings/
Bash:
deb [signed-by=/etc/apt/keyrings/plesk-ext-grafana.gpg] https://autoinstall.plesk.com/grafana/deb stable main
Can Plesk shed any light on why this has occurred and / or perhaps more importantly, suggest a resolution?
 
~~~
I am facing the same issue.
There's several different threads now, all, with either the same and / or very similar, Plesk related issues.
Plesk will provide a resolution for these, pretty soon (we think!)

Examples:
Post #2 in this thread
etc etc
 
Hi.
Is this problem on my end or I am still missing something?
apt-get update
Hit:1 Index of /pool/PSA_18.0.70_16953 noble InRelease
Get:2 Index of /PHP81_17 noble InRelease [4,009 B]
Get:3 Index of /PHP82_17 noble InRelease [4,009 B]
Get:4 Index of /PHP83_17 noble InRelease [4,009 B]
Hit:5 Index of /PHP84_17 noble InRelease
Get:6 Index of /grafana/deb stable InRelease [7,016 B]
Hit:7 Index of linux/ubuntu/ noble InRelease
Hit:8 Index of /ubuntu noble-security InRelease
Hit:9 Index of /ubuntu noble InRelease
Hit:10 Index of /imunify360/ubuntu/24.04/ noble InRelease
Hit:11 Index of /ubuntu noble-updates InRelease
Hit:12 Index of /ubuntu noble-backports InRelease
Err:6 Index of /grafana/deb stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E9299045CE550E57
Hit:13 Index of /ubuntu/24.04/slot-1/ noble InRelease
Hit:14 Index of /ubuntu/24.04/slot-2/ noble InRelease
Hit:15 Index of /ubuntu/24.04/slot-3/ noble InRelease
Hit:16 Index of /ubuntu/24.04/slot-4/ noble InRelease
Hit:17 Index of /ubuntu/24.04/slot-5/ noble InRelease
Hit:18 Index of /ubuntu/24.04/slot-6/ noble InRelease
Hit:19 Index of /ubuntu/24.04/slot-7/ noble InRelease
Hit:20 Index of /ubuntu/24.04/slot-8/ noble InRelease
Fetched 12.0 kB in 2s (5,943 B/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: Index of /grafana/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E9299045CE550E57
W: https://repo.imunify360.cloudlinux.com/imunify360/ubuntu/24.04/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: https://download.imunify360.com/ubuntu/24.04/slot-1/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: https://download.imunify360.com/ubuntu/24.04/slot-2/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: https://download.imunify360.com/ubuntu/24.04/slot-3/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: https://download.imunify360.com/ubuntu/24.04/slot-4/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: https://download.imunify360.com/ubuntu/24.04/slot-5/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: https://download.imunify360.com/ubuntu/24.04/slot-6/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: https://download.imunify360.com/ubuntu/24.04/slot-7/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: https://download.imunify360.com/ubuntu/24.04/slot-8/dists/noble/InRelease: Signature by key 9EE467641C635726A184D64B8C55A6628608CB71 uses weak algorithm (dsa1024)
W: Failed to fetch https://autoinstall.plesk.com/grafana/deb/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E9299045CE550E57
W: Some index files failed to download. They have been ignored, or old ones used instead.
 
The issue with Grafana should be sorted out now. Please do let us know if you continue encountering any errors or warnings.
In short, even after cleaning the apt cache we've still got the no public key related (not untrusted public key algorithm: dsa1024) error:
Bash:
GPG error: https://autoinstall.plesk.com/grafana/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E9299045CE550E57
Is there a replacement key now?
 
~~~ Is there a replacement key now?
FWIW The complete error syntax.
This is after an # apt cache clearance and a # plesk installer update which upgrades us to 18.0.70 MU #1
Bash:
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://autoinstall.plesk.com/grafana/deb stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E9299045CE550E57
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.imunify360.cloudlinux.com/imunify360/ubuntu/24.04 noble InRelease: The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
W: Failed to fetch https://repo.imunify360.cloudlinux.com/imunify360/ubuntu/24.04/dists/noble/InRelease  The following signatures were invalid: 9EE467641C635726A184D64B8C55A6628608CB71 (untrusted public key algorithm: dsa1024)
W: Failed to fetch https://autoinstall.plesk.com/grafana/deb/dists/stable/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E9299045CE550E57
W: Some index files failed to download. They have been ignored, or old ones used instead.

There's this: https://support.plesk.com/hc/en-us/...ions-in-Plesk-do-not-load-Dashboard-not-found
However both the Grafana & Monitoring Extensions DO load & we CAN see the dashboard etc
So that ^ option appears to be a little overkill. We'll wait for your next post @Sebahat.hadzhi
 
Back
Top