Search results

Or just check the workload that is created as a result of the installation of wordfence that will probably pick out thousands of brute-force attempts on WP? Thousands, per day, per WP instance! Or just check whether the hosting provider has provided an old rubbish server, as opposed to the...

@User22123 There you have it : WP Rocket, Asset Clean Up etc ...... all on the Apache level, hence creating extra workloads for the memory hungry Apache web server. This is what I call a "design flaw" - you did not think of the infrastructure that fits your goals and objectives best. Nginx...

@xonex You are now focusing on "cronjobs" even though the answer is often more obvious. You should first inspect the logs, especially modsec_auth.log ........ it would not surprise me if your sites get bombarded with bad requests. Just inspect the logs first and work from there! Kind...

@becker.enterprises On the one hand, your location config is to strict with : location /cdn/ I cannot verify it, but that location directive should never get the desired result - Nginx will not associate (any or many) requests to that location, so whatever is included in the location...

That is normal, at least when the sites are being "used" by external processes (request to the Apache web server, for instance) or internal processes (from Plesk). Plesk is configured to spin up several PHP processes, in order to create some efficiency when serving web requests. However, some...

@zed2007 Again, you should stick to what is known AFTER you have fully understood what is happening under the bonnet. A simple command like grep -Ri /etc/mysql would have given you insight that the [mysqldump] directive is part of /etc/mysql/conf.d/mysqldump.cnf . In essence, you should...

@User22123 If this is indeed a setting of 24G on a 64G server, then it is no surprise that your SERVER (not WordPress or WooCommerce in specific) is slow. @Peter Debik already mentioned some potential explanations, but the 24G value is the clear indicator that all of his assumptions should...

@larryk In essence, it is highly recommended - at least for the time being - that you (in chronological order) 1 - create a child theme on the staging site, 2 - make all customizations persistent by adding them to the child theme, 3 - install and test plugins on the staging site, 4 -...

@larryk, @Bitpalast, @Peter Debik There is (or was) an excellent WordPress plugin for this particular "challenge", but that plugin is not maintained ...... and even though maintenance is not really necessary, it is not recommended to use that plugin anymore. Nevertheless, the PHP code of...

@Gene Steinberg I agree with @Dave W - this is not the place for DBA optimization. Nevertheless, when having a quick look at your modifications to the MySQL config, I can only ask myself and you : what (the he*&) typ of databases are you running ...... and when are you killing your server...

@zed2007 To be honest, unless you have a monster of a database (which is quite unlikely with a Plesk instance), the default "configuration" is sufficient and optimization is not at all necessary ...... ....... so, no worries! Kind regards.... PS If you do have a monster of a database, then...

@J.Wick Can you provide an abbreviated sample of the directory structure? In essence, it is better to foscus on what is not backed up - this helps identifying the cause thereof. Nevertheless, I am not sure whether this is a bug : it can be very well related to the installation setup (or...

@raha.ab You have configured Apache to be very "free" in resource usage, probably causing the resource overusage and hence the timeouts and issues. The All Export plugin does not require such settings - not at all, never. In addition, the BIG QUESTION here is : which php config file did you...

@Peter Debik I could not agree more with @J.Wick ! In addition, Plesk Backup should be handling hidden directories and files a bit better, as opposed to spitting out error notifications for specific files/directories (and remarkably, for other hidden files/directories, the error notifications...

@JogoVogo The statement is to some extent correct, but also a bit out of context. A full backup will use a lot of space - that is correct. However, when using a full backup, the amount of space used by backups can be significantly reduced by using a limited number of backups to be stored...

@D4NY Apparently, the following applies (in chronological order) : 1 - you have a (second) "bad" domain, using SparkPost (a mail service) to send multiple mails to one or more mail addresses on your server, 2 - each and every mail is forwarded to a backup mail address on Gmail, with the...

@PeterKi, I am pretty sure that it is a language pack related issue on the host server used for hosting your vServers. It is safe to assume that the host server is German in terms of language and that package are installed in German by default. This can be persistent across vServer in a...

@D4NY Just block 54.36.113.226 with the firewall on all ports. Kind regards......

@D4NY You should NOT disable "recidive ban" (I think that you mean to say "recidive jail"). What is not clear to me : what is the IP of your own server? Could that be - coincidentally - 54.36.113.226???? If yes, then do NOT block your own IP address, not on via the Plesk firewall and not...

@D4NY, Are you familiar with the Plesk firewall extension? If so, then it would be recommended to start first by adding 54.36.113.226 193.24.210.61 to a firewall rule that blocks all traffic from these IPs to all ports. Fail2Ban is a good method to detect offending IPs and block them...