Search results

Thank you for the report, @theunknownstuntman. Could you please provide us with the exact steps to reproduce the issue as it seems like you are using a custom status page? Thank you in advance.

At present, with Imunify, you can set up your custom script for notification. How to enable e-mail alerts via hooks or notifications in ImunifyAV+ It shouldn't matter where the script is located as long as it has execute permissions.

This is an expected behavior. What you can do is to manually export the Contacts. You may find the steps here. I hope that helps.

Hey, everyone. We are sorry to hear about the issue you are all experiencing. I discussed the case with our team and we are currently investigating it. I will keep you posted on the matter.

Thank you. Upon reviewing the autoinstaller log I can see the following error logged: That might be caused by a stuck install process. Please check if there is such: If there's a stuck process, please try killing it: If there are no stuck install processes, the issue might be related to...

Hey, everyone. I would like to inform you that the issue with the incorrect timestamps during restores is fixed in Plesk Obsidian 18.0.65. If you have automatic updates enabled (or already run Plesk version 18.0.65) this update should be installed already.

Hey, everyone. I would like to inform you that the issue with the incorrect timestamps during restores is fixed in Plesk Obsidian 18.0.65. If you have automatic updates enabled (or already run Plesk version 18.0.65) this update should be installed already.

From Plesk 18.0.65 you are able to copy the DNS records values shown in the “How to configure external DNS” pop-up window with a click. Thank you for your suggestion.

I will further discuss both cases with our team and we will do our best to provide some finality on them. Thank you in advance for your understanding in the meantime.

I am sorry to hear about the issue you experienced during the update. Could you please check /var/log/plesk/install/autoinstaller3.log and provide the latest entries? It stores logs of Plesk updates.

Our team is currently working on linking the completed ideas to the new update, Maarten. :) Apologies for the delay.

Thank you for the update. I believe your suggestion about the system time might be correct. Could you please try the following workaround? Although the guide is for Google Authenticator, it is also applicable for the MFA extension.

Hey, Stephan. It is likely that there is a leftover package psa-kav8, which is supposed to be removed when the extension is uninstalled, but it still remains in the system. Please try executing the following command: If it returns an entry, the solution would be to remove the package manually...

@Kaspar, the behavior was identified as a bug with ID PPPM-14656. Thank you once again for bringing it to our attention. We will introduce a fix in one of the feature releases. Unfortunately, I cannot provide any ETA at the time being.

Thank you for the report, Kaspar. The issue with the placeholder was fixed in Plesk 18.0.64.1 and we are unable to reproduce it. In case you continue experiencing it after the upgrade, could you please provide us with additional details on how to reproduce it on our end?

I tested the MFA extension on a CentOS 7.9 server with Authenticator app for Android and I was not able to encounter any issue. At what stage exactly the process fails, please? Do you encounter any error/issue when scanning the QR code from MFA through your local authentication app? If possible...

This error usually indicates an incorrect name in the SSL certificate of the domain or default Plesk certificate being used. Instead of renewing the SSL, could you please try removing the current SSL altogether and installing a brand new one?

Given that users can install an SSL through the panel without an issue the priority assigned for this bug is low. Therefore, the resolution takes longer as there are other more pressing and urgent matters to be addressed by our team. Unfortunately, I cannot provide any ETA at the moment. Thank...

Thank you for the report, Kaspar. I was able to reproduce the behavior on a test environment and forwarded it to our engineers for further review.

Kaspar, our team confirmed that this behavior is by design. With the Power User view domains are first organized by groups and then listed alphabetically.