Recent content by Greg Voronov

Hello Peter, Wordpress Toolkit 2.5.1 is the current version based on WordPress Toolkit - Plesk Extensions It seems some of the previous updates of Wordpress Toolkit did not completed successfully and did not apply changes on Wordpress Toolkit sqlite database. Could you please share the version...

Hello Mark, Unfortunately htaccess to nginx does no magic with existing htaccess files. One needs to proceed to 'Websites & Domains' -> 'Apache & nginx Settings' and put some additional configuration to make Wordpress permalinks work on nginx. The extension will help you to convert your...

Thank you! Most likely your account language doesn't set to Spanish for whatever reasons. Please clarify who is going to be the owner of the subscription? If you create a subscription for Administrator, please proceed to 'Profile & Preferences' on the left tab, make sure interface language is...

Could you please specify the versions of Plesk and Wordpress Toolkit extension?

When sending these reports, Let's Encrypt uses the domain name, which is decoded from the certificate itself, not the name of Plesk domain. So if you had certificates for the same domain name assigned to different Plesk domains, you would receive such notification.

There are certain limitations with using the same certificates for securing domains and Plesk itself at the same time, see Domain certificate cannot be renewed: One of the certificates you are going to delete is used for securing Plesk for instance. It is recommended to use separate certificates...

Based on your report I can see, that you use the same certificate for securing domain and Plesk (and mail). Currently Let's Encrypt extension does not allow to auto-renew such certificates due to limitation in Plesk 17.5 platform. This behavior will be fixed in upcoming Plesk 17.8, that is...

Most likely the subdomain was not entirely removed from Plesk. Please try to create it again and see what happens.

See there is a 'Scan' button on the screen you've sent before. Click on it and wait till scan is over. It should find this Wordpress instance and add it to Wordpress Toolkit. After that you may delete it like any other Wordpress installation.

Probably it was detached before. Please run server-wide scan to find it. Once you find it, you will be able to remove it as suggested. Unfortunately there is no way to hide detached Wordpress instances in Security Advisor, we have a bug EXTPLESK-350 for this issue.

Most likely this is 'broken' Wordpress installation. Please check Wordpress toolkit -> Installations tab, this instance should be there with more info about it's origin. If you feel you don't need it, you may remove it from instance details page. BTW, upcoming Security Advisor 1.6 comes with...