Applications & Extensions
Plesk applications and extensions installation/management articles. WordPress, Joomla, Let's Encrypt, CloudFlare and etc.
- [FIXED BUG] mod_rewrite stopped working. All pages on WordPress sites show 404
- ModSecurity ruleset update error in Plesk installed on Debian-based OS (Debian, Ubuntu): "modsecurity_ctl failed: modsecurity_ctl: unrecognized option '--apache'"
- Plesk Premium Email shows the warning on Plesk server: Necessary packages are not installed
- Let's Encrypt extension in Plesk shows that certificate will no longer be used for example.com even if it is correctly installed
- WordPress functionality is broken in Plesk after changing domain PHP version to 8.0: Uncaught TypeError: implode(): Argument #2 ($array) must be of type ?array,
- Unable to activate or update the Comodo rule-set in Plesk ModSecurity: Error interacting with https://waf.comodo.com/doc/meta_comodo_apache.yaml: <urlopen error [Errno 113] No route to host>
- Can't login to Wordpress from Plesk dashboard
- Websites hosted on a Plesk server with Imunify360 are intermittently unavailable: Error establishing a database connection
- How to install Magento for a domain in Plesk
- The Plesk Email Security dashboard keeps loading, or statistics are not updated
- Mail stuck in queue when Plesk Email Security installed on SELinux enforced server
- Cannot change Node.js application root in Plesk: Class 'CommonPanel_Validate_FileSharing_FolderName' not found
- RapidSSL and GeoTrust paid SSL certificates provided by SSL It! extension are not supporting www and SAN
- Unable to clone instance or apply SmartUpdates on Wordpress Toolkit in Plesk: Smart Update was unable to correctly clone your website for further analysis
- Unable to update Wordpress: WordPress version requires PHP version 5.6.20 or newer
- Amavis is not installed/removed along with Plesk Email Security
- Server with Plesk Email Security no longer sends/receives emails: [127.0.0.1]:10024: Connection refused
- Unable to access SSL/TLS Certificates for a domain: Argument 3 passed to BaseComponentChecker::getCertificateStatus() must be an instance of PleskExt\SslIt\Certificate
- Unable to install WordPress instance for the domain: Unable to unpack archive
- Unable to open Composer extension for a Plesk domain: Could not open input file: /usr/local/psa/var/modules/composer//composer.phar
- Unable to access the SSL/TLS certificate page: Reduce of empty array with no initial value
- Moodle install/update through Plesk fails: Non-zero exit status returned by script
- Scheduled remote backup on Dropbox was not created: upstream connect error
- Let's Encrypt notifications are received for an already renewed certificate
- Unable to issue Let's Encrypt Certificate: During secondary validation: Invalid response. <title>Captcha</title>
- Unable to issue SSL certificate for a domain: error 400
- WordPress instance can not be removed via Plesk applications catalog
- SpamAssassin configured in Plesk shows the messages in log: connect to spamd on ::1 failed, retrying (#1 of 3): Connection refused
- Can't install plugin via Wordpress Toolkit: destination folder already exists
- Unable to install the Plesk Email Security: ERROR: Missing required additional modules: DBD::mysql