• 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 Weak Algorithm Warning (DSA1024) for Plesk Repositories on Ubuntu 24.04 LTS

Everyone, the issues with Grafana, PHP 7.4 and PHP 8.0 and the signing keys should be sorted. Our team released an update:

The GPG signing keys for the PHP 7.4 and 8.0 repositories on Ubuntu 24.04 have been updated addressing apt-get failure “untrusted public key algorithm: dsa1024”. (PPPM-14985)

Please let us know if you continue encountering any errors/warnings.

I cannot provide any ETA for CloudLinux's repositories, at this point.
 
Everyone, the issues with Grafana, PHP 7.4 and PHP 8.0 and the signing keys should be sorted. Our team released an update:



Please let us know if you continue encountering any errors/warnings.

I cannot provide any ETA for CloudLinux's repositories, at this point.
 

Attachments

  • Capture d’écran 2025-06-05 100522.jpg
    Capture d’écran 2025-06-05 100522.jpg
    136.6 KB · Views: 9
@Camel Design
IF you had read post #44 above and then looked at ALL of the Plesk workaround (via the link in that post), then you would not have needed to make your post...
my post is here just for help and indicate all is ok now exept immunify so the problem is not 100% fix.

i have read all post and your, and i have try all solution and is not because you don't use immunify that fix the problem

Immunify work well just before this problem with the last update so we considerate is fix ? i don't know and yes i have try the workarround but is just a temporary patch
 
@Camel Design You posted an image (no words) relating to the weak algorithm warnings (DSA1024) thread, as a response to an earlier post, yet... imunify360 and its (current) weak algorithm warnings (DSA1024) is specifically covered, with advice, by Plesk, in the link that was posted, so you completely missed the point of the previous post... No problem. It's not that important.
 
A this moment my temporary solutions are:

1. For Grafana

sudo nano /etc/apt/sources.list.d/plesk-ext-grafana.list
commented line:
#deb Index of /grafana/deb stable main
added line:
deb [trusted=yes] Index of /grafana/deb stable main

2. For DSA-1024 warning
created file:
/etc/apt/apt.conf.d/99weakkey-warning
with the code:
APT::Key::Assert-Pubkey-Algo ">=rsa2048,ed25519,ed448,dsa1024";

For munify360 is not needed a temporary solution, even it is warning, the update is working.
 
A this moment my temporary solutions are:
1. For Grafana
Grafana is already completely fixed. There's no need for any temp solutions now. See Changelog plus:
2. For DSA-1024 warning
For munify360 is not needed a temporary solution, even it is warning, the update is working.
See / read all of the previous link:
 
Grafana is already completely fixed. There's no need for any temp solutions now. See Changelog plus:

See / read all of the previous link:

Thanks for Grafana solution, I applied it and solved.


This link does not open anything.
 
Thanks for Grafana solution, I applied it and solved.
Great!
This link does not open anything.
Ahhh Yes. The linked article has now been removed by Plesk. Understood.
Effectively, the temp solution was very similar to your own, (slightly different syntax) but the important closing statement on that page, was, that the Cloudlinux team will completely resolve this (in due course) and that the (current) weak algorithm warnings (DSA1024) that are still being generated by imunify360, can be safely ignored. We don't use imunify360 so were / are not affected.
 
Hello, @Michael.P . Imunify360 is a third-party product and it is maintained by CloudLinux. The warnings you get are related to their repositories. As previously mentioned, they are aware of the issue and working on fixing it. However, I cannot provide any ETA on when that will be fixed. At this time, you can safely ignore the warnings.
 
Back
Top