Search results

For affected customers it can be resolved by going to Change settings in the email tab (where you can enable the catch-all functionality) and just clicking "OK" without changing anything. Affected broken email addresses have to be deleted before (they never worked anyways) and then recreated...

@ngrootjen @evcilsehri After we did this, we are now facing a new issue, where when a customer creates a new mailbox, the mailbox is not correctly set up on the mail service node. Only the domain directory as well as the name of the mailbox are created at /var/qmail/mailnames/<DOMAIN>/<NAME>...

Hi @ngrootjen, Thank you for posting this, it saved me a lot of time today, trying to fix our legacy system :D We had to do the following, which is a bit different from your commands: We realized with openssl x509 -in /opt/psa_agent/internal/rootchain.pem -text | grep 'Not After :' on our...

Hi @Peter Debik, any update on this? Thanks! :)

Thank you @AYamshanov, this fixed it for us as well.

Hi everyone, Today, Plesk released a new version of the Let's Encrypt extension (Change Log for Plesk Obsidian) (version 3.1.13). It seems that the extension was also updated on older Plesk versions. We still have a few servers running Debian 9 (yeah, I know...) and for this reason old Plesk...

Hi @sebgonzes, take a look here: https://talk.plesk.com/threads/wordpress-toolkit-product-news.355059/page-2#post-912284

Hi @vbelich, we are running several hundred Plesk servers. On many servers with the new WP Toolkit version, logged in users cannot open the Wordpress Toolkit anymore and get the error message: "Server Error 500 PleskExt\WpToolkit\Api\Exceptions\InternalServerErrorException Could not fetch the...