• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • 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 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