Search results

Following the automatic update of Plesk 18.0.61 Update 4 (https://docs.plesk.com/release-notes/obsidian/change-log/?18061-mu4#plesk-18061-mu4) caused a DB Outage this morning at around 06:29 BST. Was there anything in this update which would have caused this outage? Included within the Update...

Great to see the updates to the WordPress Toolkit! Can I check one thing though, is there anymore information that can be given about the following entry: [+] (Plesk) Full-featured integration of WP Toolkit into Plesk Dynamic list is now available

Thanks for your reply. I've had a look at the structure of both of the offending Domains, and spotted two folders with wierd permissions being set on both: drwxr-xrwx 3 xxxx psacln 4096 Feb 2 18:57 blogs drwxr-xrwx 2 xxxx psacln 4096 Feb 5 04:05 tmp Based on my calculations, these...

We use WP Toolkit to keep our WordPress sites upto date and secure. However, there are two of our sites where I keep needing to re-apply the "Restrict access to files and directories" security measure. Its probably the fourth or fifth time in a few months where WP Toolkit marks these two...

When we look at our Server Summary report, it says there are 2 'Sites published with Presence Builder'. We need to track down which Domains these are without manually going through all 400 Domains hosted on our Server. Is there any easy way to do this?

Bump.... Getting this email too.

Is it possible to set ModSecurity to AutoUpdate in Imunify360? We keep getting notifications that the ModSecurity (WAF) ruleset is out of date. The notification mentions that there is an AutoUpdate feature, but I cant seem to find this inside the Imunify360 settings on the dashboard. Thanks

We are running Plesk Obsidian 18.0.50 #2 & Joomla Toolkit 2.5.10 on Ubuntu 22.04.02 LTS In order to test the Joomla! 3 to Joomla! 4 update to ensure everything is working & runs correctly using Joomla 4 & PHP 8.1, we'd like to clone our Joomla Sites onto a separate Domain. Having clicked around...

Yes, this was tried, and it returned 'OK'. However, we've just updated Plesk to 18.0.50, and this seems to have corrected the issue. The affected site (test2.domain.tld) is now showing with the correct certificate via SSLShopper. Odd. Thanks for your help!

Yes @Peter Debik - That is a suitable explanation of the case we are experiencing. Do you have any suggestions as to how to proceed?

The host server uses the sub-domain ‘hosting.’ It’s this certificate the new Domains are picking up rather than the correctly generated certificate. If I was to create a certificate with a sub-domain of ‘foo.’, the certificate would be from ‘hosting.’ despite the correct certificate being...

The main server Domain happens to be a sub-domain itself, and doesn’t appear to be using the wild card certificate. We recently had to restore the server from backups, and it’s since this that we’ve experienced this issue. All sites created before the issue are currently working correctly...

Thanks for getting back to me. The certificate generated for the Domain in question.

Was there ever a resolution to this issue? We’re experiencing the same issue now, Plesk Obsidian 18.0.49 Update #2 and SSL It! 1.12.3-1586. Tried manually installing a LetsEncrypt by SSL It, and also using the CLI. When we check SSLShopper for the respective domain, the Domain is using the...