Recent content by Raul A.

Looks like your server can't connect to check-updates.plesk.com. The address is reachable for me.

When you enable GoAccess on an existing website, it will calculate statistics for you, using the new statistics tool, GoAccess. Once I accessed the statistics, I had historical data in GoAccess, not just data from the current logs.

You can try a different plugin to hide wp-login.php: https://support.plesk.com/hc/en-us/articles/12376958314775-Autodetection-of-WordPress-login-URL-does-not-work-properly-in-Plesk-WP-Toolkit

Plesk calculates disk usage during the nightly maintenance task. You can also try to refresh the disk usage using: Plesk is able to manage servers running multiple WordPress instances. WP-Toolkit is a great tool for WordPress management.

Hi Jan, Did you try plesk installer? Do you have Extended Lifecycle Support (ELS) by Plesk? You should upgrade or migrate to a new server running a newer Debian version.

In order to manually compile and install memcached, you can run the following: dnf install libmemcached-devel.x86_64 plesk-php84-devel plesk-php83-devel plesk-php82-devel make gcc cpp cd /var/tmp/ wget https://pecl.php.net/get/memcached-3.4.0.tgz tar -zxf memcached-3.4.0.tgz cd...

https://support.plesk.com/hc/en-us/articles/12388040127383-A-website-hosted-in-Plesk-fails-to-load-ModSecurity-Response-body-too-large will help you with that.

GoAccess replaces Awstats and Webalizer. You access it from the same place:

Hi, You can use the following commands: #install dependencies dnf install libmemcached-devel.x86_64 plesk-php84-devel plesk-php83-devel plesk-php82-devel make gcc cpp # set the custom temp folder pear config-set temp_dir /var/tmp # compile and install for PHP 8.4 export...

What commands?

You can't install ioncube_loader with pecl on PHP 8.1, 8.2 and 8.3. I also recommend not using PHP 8.1 since it's already EOL. Download the loader archive from here: ionCube Loader - A website add-on for running ionCube encoded files, deploy the .so files, load them and reload the PHP-FPM and...

You are seeing the "Not secure" warning because 82.165.98.82 is not a domain name in the installed certificate. The certificate is also expired. You can change the expired certificate or issue a new one, from Tools & Settings > Security: SSL/TLS Certificates > Let's Encrypt. In your case...

It looks like redrings1893-lb.de has a proper certificate installed now: The website does indeed load for me, without any certificate warnings.

I don't understand your questions. Can you please write in English and elaborate on the issue you are encountering?

The MX record will affect only email receiving. You reported a website issue.