And now, ladies and gentlemans, nothing changed and everything works again...
I have still the DO version 1.3.2-119 but the entries on DO side are all correct.
Maybe has DO rollback an braking API-update?
Could somebody please inform the plesk developers about the chaning frame conditions?
Hello,
I can confirm this bug since yesterday evening while refresh the Let's Encrypt certificates.
Details:
CentOS Linux 7.9.2009 (Core)
Plesk Obsidian Version 18.0.42 Update #1
DigitalOcean DNS in version 1.3.2-119
First time bug seen: Wed, 06 Apr 2022 19:56:11 +0200
This bug is high...
Same problem after update to:
Plesk Obsidian Version 18.0.20 Update #2
I created a daily cron with
rm -f /etc/alternatives/mta && ln -s /usr/lib64/plesk-9.0/postfix-sendmail-wrapper /etc/alternatives/mta && /usr/sbin/postsuper -r ALL
Where can I report this bug?