Search results

I've raised priority of this bug, so hope to see it soon ;)

Hello, thank you for your patience! This bug is not resolved yet, but it is planned to be fixed in one of the next releases.

Hello, At the moment "webmail.<domain>" may be only included as a Subject Alternative Name into certificate for main domain. LE certificate for "forwarding" domains can not be issued in an automatic manner. It is because LE requires to pass http challenge (put special file with verification...

Thank you for your report! We confirm this behavior as a bug (bug ID EXTWPTOOLK-3417). It will be fixed in one of the next releases.

Hello, This is a known behavior. "Keep secured" functionality were implemented in Let'sEncrypt extension by requests of hosting providers. The way to enable it- is to add a plan item in service plan. At the moment "Keep websites secured" switcher in SSLit is just an alias for plan item in...

Thank you for the information! Yep, we confirm this as a bug. It will be fixed in one of the next releases of SSLit extension. Please refer to the following bug's ID: EXTSSLIT-462

Hello, I'm unable to reproduce such behaviour when URLs are not changed after the Clone operation. Could you please describe your issue in more details? Are you using different databases for source and destination instances? Or both WP instances are using one database? URLs were not changed in...

Thanks a lot for your investigation. Are you using local DB server (placed on the same server as the WP Toolkit) or a network connected external DB server?

Hello Peter, have you contacted our support team with the permissions problem? I've just seen ticket with most likely the same problem as yours. If yes, then your problem should be solved already :) If not, please check the following: 1. Run # plesk repair fs -n to check if it reports any...

Hello, thank you for your report, Actually the problem is in the following: before the clone operation, we are using mysqlcheck to check that database is Ok. If not, clone operation become blocked. We are going to change this behavior in the nearest update of WordPress Toolkit. Please refer to...

Thank you for this information. I've just checked workflow as you reported and we confirm a bug. It will be fixed in one of the nearest releases. UPDATE: issue number EXTWPTOOLK-2397

Hello, FAPM, let's fix your WordPress first: 1. Check that wp-config.php file contains correct define( 'DB_PASSWORD', '<password>' ); directive. If there is no such directive, please paste it into /** MySQL database password */ section. If you aren't sure that you can remember password...

I've found your report regarding incorrect language when WP is installed via service plan. We've checked several scenarios and were not able to reproduce such an issue :( Have you contacted Support with detailed information about your configuration?

How many WP instances do you have in WP Toolkit? How long the listing operation lasts? I'm going to check your report regarding language issues and see if we can increase it's priority

Hello, Have you used "Detach" operation for several WP instance at once or detached them one-by-one? Had these instances used separate databases for each WP or it was one database for several instances? Such behavior looks like a "Remove" operation, nor as a "Detach". Do you have a backup which...

I've just re-checked "Bot protection" feature and was not able to reproduce such an issue. Could you please let us know some an additional information: 1. Your Plesk's version; 2. Your webserver configuration (IIS, Apache+Nginx as a proxy, Apache/Nginx standalone) 3. Everything works well in...

Thank you for your investigations and suggestions! I think, that it is quite a brutal workaround, but I'm glad, that your websites works well. We will check what may be wrong with "define('SUNRISE', 'on');" in multisite configuration.

Reverting of new security measures should help. But we can not check or apply security measures if this instance is shown as "broken" in WordPress Toolkit. Mostly "Multisite" instances are shown as "Broken" if corresponding wp-config.php file was customized in some way. So first of all we need...

Hello, thank you for your report! Please describe your issue in more details: 1. Your WordPress website stopped working or your WordPress site is shown as "broken" in WordPress Toolkit, but works correctly when accessing it by URL? 2. Where and when did you get mentioned error? In "Security...

Thank you for your report! It is very strange behaviour. I can not imagine how it can be performed. But of course we will try to reproduce this issue. I'm going to investigate this issue and let you know a results or request some an additional information. I hope to get back to you on...