• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Resolved CentOS 7.x - Stderr:dnssec-keygen: fatal: unknown algorithm EC/AP384SHA384 when attempting to sign DNSSEC

Matt N

New Pleskian
Hi All!

when attempting to sing my domain using Plesk's DNSSEC setup, I get the following error:

Error: Unable to sign the DNS zone. Execution CLI utility is failed: dnsmng. dnsmng: /usr/sbin/dnssec-keygen failed with code 1.
Stdout:
Stderr:dnssec-keygen: fatal: unknown algorithm EC/AP384SHA384


System error 11: Resource temporarily unavailable dnsmng: /usr/sbin/dnssec-keygen failed with code 1.
Stdout:
Stderr:dnssec-keygen: fatal: unknown algorithm EC/AP384SHA384


System error 11: Resource temporarily unavailable

The DNSSEC plugin set up okay, and accepted all of the available Encryption types. However, I get this, with almost any of the available Encryption types (I have not tried them all).

System is running:
Plesk Version : 18.0.32 (update #2) OS : CloudLinux 7.9

I've searched the web - but was not able to find anything that remotely resembles this issue. Looking for ideas of what to try. Because this is related to encryption algorithms, I'm reluctant to just try random stuff.
 
What is the version of your DNSSEC Plesk extension?
As far as I know, this issue was fixed a long time ago in version 1.2.2
 
according to the extension itself, it shows as Version 1.2.3-93.

just wondering whether I should remove and re-add it to see if something failed to update properly.
 
according to the extension itself, it shows as Version 1.2.3-93.

just wondering whether I should remove and re-add it to see if something failed to update properly.

removing then reinstalling the extension fixed it .... weird! :)
Thanks @IgorG!
 
Back
Top