• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Bad RSA signature - DKIM fails

Josch

New Pleskian
Hi,

I've searched a lot and need to clarify something.

I have a problem when trying to validate via dkimvalidator.com. I get

Validating Signature​


result = fail
Details: bad RSA signature

I checked, if the TXT record for default._domainkey.example.com is the same on all nameservers, described here:


and the domainkeys are different.

Now I read, that the DNS zones may not be updated. Here is the support article:


I checked

cat /etc/bind/rndc.key

and

cat /etc/named.conf

and the secrets are not the same. Do these both secrets have to be exact the same ones?

In rndc.key I have the following:

Code:
key "rndc-key" {
    algorithm hmac-sha256;
    secret "some-long-secret-key-with-44-digits";
};

and in named.conf I have

Code:
key "rndc-key" {
    algorithm hmac-md5;
    secret "another-secret-key-with-24-digits";
};

Could that be the cause of my problem?

Any help is appreciated.

Thanks in advance and regards

Josch
 
Back
Top