• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue dkim=neutral reason="invalid (public key: not available)"

Edinho

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian 18.0.64 Update #1 Web Host Edition
Hi guys,
I have a problem that is driving me crazy.
I have a domain that I can't get the DKIM record validated in any way, for all my other domains I managed, but this one I just can't. I have the DNS zone on OVH that takes the key obtained from the plesk configuration, I also checked in the DNS records of plesk if all three were the same. But every time I try to check the record I always get the same problem: dkim=neutral reason="invalid (public key: not available)"

Could it be because this domain is the only one with a slightly more peculiar extension being a .store? Otherwise I cannot understand why all the other domains the DKIM works and this one does not.
Thanks to all
 
Back
Top