Search results

No Probs under Ubuntu 20.04.6 LTS and MariaDB 10.6

Ok... Additional directives for HTTP Any hints?

Hello everyone, I have a problem with the optimizer, which doesn't work if the domain can only use https / port 443, but returns a 410 (service gone) on port 80. Can the optimizer be adjusted to use port 443 instead of port 80?

As I mentioned before, I'm one of those people who has no experience with NGinx - certainly not with porting an existing Apache2 (domain) configuration with http/2 from Apache to Nginx. I configured Apache2 to run very efficiently. (mod_event / php-fpm 8.2.x - static / http/2...) The entire...

I agree with you, but only when it comes to static content. As soon as it comes to content that is constantly changing, such as in forums or WordPress with a forum function, the Apache/Nginx team tends to slow down a server. In addition, the processor load increases significantly. If Apache is...

It's a bit confusing that the "Performance Booster" on Web only works in conjunction with Nginx. Does this have any particular reason? Many, including us, only use Apache because it would be too much overhead and more error-prone to use both. Is there anyone here who would also like to have...

That's an inconsistency. Plesk only notices that the updates are already installed during the morning update check... If you're doing this via ssh on the command line, you'll need some patience.

I experienced with VPS that the SQL server was installed and shared on a completely different server. Then everything (Plesk, Wordpress...) was very slow. In addition, the SQL server was poorly configured in relation to Innodb.

This has only been the case since MariaDB 10.6.x, before that, i.e. with MariaDB 10.5.x, I never had such problems with the Plesk backup and MariaDB. Of course I won't create new users, you're right. Then I'd better just leave NameResolve enabled in MariaDB.

So with this bind-adress = :: the same error occurs if "skip_name_resolve" is activated BackupWarning: So i have to stop "skip_name_resolve". :( That must be an bug/error in plesk and "state intended protocol"

That seems a little crazy to me, but it works. Thanks for the hint. :)

Ubuntu 18.04 LTS MariaDB 10.6.7 Plesk 18.0.42 Backup Error: "Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol. mysqldump: Got error: 1130: "Host '127.0.0.1' is...

Backup Error: "Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2: WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol. mysqldump: Got error: 1130: "Host '127.0.0.1' is not allowed to connect to this MariaDB server"...

Comparing cats and servers is irrelevant. I hope that doesn't catch on with the professionals. ;) You use free software as main components and therefore build a core that configures these main components. There is nothing more expensive about it if you do it right. Your problem is that you are...

Here I would like to join in with my opinion. By default, Plesk has always been a server control center for services offered by a SERVER, which in turn is divided into web servers, database servers, and other, optionally usable services such as DNS servers, services that concern server...

That looks ok so far. With that you shouldn't run into problems again anytime soon. You have to observe this for a few weeks now, at the latest when it gets tight again, report back here ... I would now set the value for Memory_limit to 128 MB and only increase it slowly when errors occur.

https://myplesk.dom:8443/admin/server/optimization-settings Change Prefork to Event here and save new setting.

However, this is a very bad user experience! If an add-on blocks or replaces a service, this should be indicated accordingly. So here PES should be displayed in green instead of Spamassasin, if it is running. With Plesk, the user (s) and their point of view should always be in the foreground...

Addendum: If the Mysqltuner script recommends to set the join_buffer_size higher than 4 MB you should definitely ignore this! 4 MB are completely sufficient here!

Do not use mpm_prefork with Apache2, use mpm_event with the following settings: Path: /etc/apache2/mods-enabled/mpm_event.conf (Settings for: 32GB Ram) <IfModule mpm_event_module> KeepAlive On KeepAliveTimeout 5 MaxKeepAliveRequests 128 ServerLimit 10 StartServers 4...