Search results

O.k., not a problem. You are right, I am wrong. Good luck.

Your description points to either a hardware issue or an issue with the operating system itself. You're trying to blame it on Plesk in your previous post, but Plesk only takes what's in the system and offers an easy-to-use user surface to manage system services. If they install system services...

Great, you're almost at your goal. The reason for the issues here is that you have a script that runs way too long. Normally, website scripts run a fraction of a second. When you are doing uploads it might take longer, but for regular operations anything beyond a few seconds is too long. This is...

You need to update your website content first (e.g. update Elementor to the latest version), then you can update PHP to a newer version. Your Wordpress is outdated, too. The "Error" shown above is just fine. ModSecurity is blocking Bytedance, which is what you want if Fail2Ban hasn't done it.

It seems that the operating system itself has incorrect permissions. This is something that Plesk cannot fix. I believe it is best to reinstall the server from scratch, especially the OS. I doubt that it is possible to obtain a clean installation state on your current system given the log...

Random reboots are logged to journalctl. It is impossible that there are no entries regarding the cause. There must be entries right before the reboot that point to the cause.

Change "dynamic" to "on demand" and reduce the max script runtime (not shown in your screenshot) to a value like 10 or 20 seconds.

The name of your incoming/outgoing mail server entries of your local mail application is wrong. Instead of what you've currently configured in your mail application use the hostname of your server, because that's the one you have a cert for.

The new regex seems to be a big improvement. How did you come up with the changes applied (how did you know or where did you find out that the obviously much longer, more complicated expression results in faster processing)? My hypothesis is that it is faster as a break condition is met earlier...

Plesk does not support EOL operating systems. Unofficially, when CentOS 8 was EOL, Plesk continued support for a few weeks, but I'd not bet on it. EOL of CentOS 7 has been anticipated for years and it should be top priority for all CentOS 7 users to upgrade to Alma 8 now. There is no reason why...

Probably the mysql_upgrade was not run. In this case it could help to run MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin on the command line so that MariaDB updates all table definitions to the new MariaDB version requirements.

No, it means that a function that was included in a previous (older) PHP version is no longer available in the new PHP version you have set for your website. Your PHP version is too new for your old software or your software is too old for your new PHP version. You need to either downgrade your...

This means that in your wp-config.php file you have lines that defines WP_DEBUG_DISPLAY and WP_MEMORY_LIMIT a second time. Only keep the ones that are really needed. This means that the Eventon plugin is outdated. It uses PHP functions that are no longer present in the PHP version that you are...

That seems to be a glitch that I did not know.

Yes, in theory. In practical application I've been through dozens of "surprises" even with the conversion from CentOS to Alma although all started out from seemingly perfect "default" systems. I bet there will be hundreds of deviations between Rocky and Alma. You have to figure that every Plesk...

You must name your domain correctly from the start. If your domain is hosted elsewhere, you would not add the domain to the Plesk installation. If you know that you name your domain lists.<domain>, then you add lists.<domain> as your domain name, not your main domain name that is hosted...

It means that a transaction in the website violates ModSecurity Comodo rule no. 214940, hence it is blocked by the "Web Application Firewall" (ModSecurity). If you trust the transaction, you could add the rule ID as an exception to the Web Application Firewall settings.

You do not need a subscription. You still have the plugin (without subscription), which is outdated.

Your WP Rocket plugin needs an update.

What keeps you from issueing it?