• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Issue Some (recent?) upgrade broke the DKIM TXT records

olegburca

New Pleskian
Hi,

Found an issue today.
Some (probably recent) upgrade broke the DKIM TXT records for domains.

I have a domain that I switched to CloudFlare some months ago and at that time I copied the DKIM TXT record that is:
"v=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCi0zwXBrJN2mjpEes5ftzdyMhzroEL9c6n/pkTrVnkEymJklSCyKOjYmkac8QXbaVshBgXQlOchJ0gzR09gGNha1T21Fbl3WZjRHVaw4uq6jNKROH4wXi+enSOgaqF4pJ0C3kYZL10aChaEtmnpiG/VQKMUvmxArD/tBuDvICwSQIDAQAB;"

Now I see the key on Plesk DNS for this domain was updated to:
"v=DKIM1; p=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC029GsCvlnc2Eft+pnemtRcOp/rnDiJPLi33K8SgTqPN/8rjsPl3wbJSp2nujZQvENiPoYw8qBnjntDFBZghrZ4gIcpoYUEDMp6ez9pi9b0BjW6eTe3MeXyZj4BJnaxN+xP3EJZRzZ/Q+VWc+YcfOgPjQv1lJ/KyeIDcDRhAKAoQIDAQAB;"
Please note the doubled p key that makes the DKIM validation to fail.

Same problem observed for multiple domains (that has the DKIM option enabled) on the same server, however not for all of them.

Switch Off and back On the DKIM option for a domain fixes the problem. This is why I suspect it was caused by an update.

My system:
CentOS Linux release 8.3.2011
Plesk Web Host Edition Version 18.0.32 Update #2

Regards,
Oleg.
 
Same here:

v=DKIM1; p=DKIM1; p=DKIM1; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC51znlcK3EP3mvXbK5fkHJBNLHQEIGKUaHTM0e5aV/oJ0gIEUdeUNO4UtXhqpCWO8XE3O1rb5iKzIaS2W9oNNBRyucxADN+zLDGU3jpNzcN0CKt1T2IK34OSg/20CsINBWxSGRk7vJfRNJRDVQui2VWK4E6zqRpXsKbvO2bBgPUQIDAQAB;

This happened after migrating subsciptions to another Plesk server.
 
Back
Top