ianro

wynot – just to thank you again – I did manage to make the change – and it solved the upgrade problem. Thanks

Thanks Wynot. Because I am not a programmer, and because this is a bug recently introduced (after meny many years of using Contact 7), I was assuming and hoping that the bug would automatically be removed by a later update.

Clearly, if that is not going to be the case, I will get onto my hosting company and see if they can do the modification you suggested. My reluctance is down to the fact that past experience has shown me that even simple changes can often have unintended consequences!

Thanks again for your time. Much appreciated

I have exactly the same problem since the last contact 7 update – any ideas?

Thanks again for such a prompt reply

I will look into these and update

Thanks again

Ian

Thanks for taking the time to reply

Fortunately my web hosting company cleared all the listed malicious files. I have taken some extra precautions cleaning up the site, so I will wait to see if it happens again.

I will mention a couple of things, in case they are of interest. After the site had been cleaned, the wordfence scan kept stopping. The hosting support had to up execution time for php limits several times to get it to run the full test. When I then tried it on Firefox, it stopped again. However, when I ran it on Chrome it worked fine.

The other thing, which I appreciate may not be relvant, is that there were several subdirectories not associated with WordPress. All the index files in these subdirectories (which did not show up on the wordfence scan) had been renamed by adding a .bak to the name (so index.html became index.html.bak) and a malicious file index.php added.

Finally (and again this may not be relevant to you) WordPress itself picked up a critical issue (not reported on Wordfence) as the following
Some files are not writable by WordPress:
index.php

Thanks again
Ian

Thanks for that information

Asecommended, I have deleted the old copy of Wordfence and re-installed, and at the moment the website seems to be working fine.

The only problem is that since re-installing Wordfence, it is finding two “high severity problems” that wordfence did not previously identify. These are:

* Unknown file in WordPress core: wp-includes/class-wp-hoook.php_bk
* Unknown file in WordPress core: wp-includes/functions.php_bk

(please notice the 3 “o”s in wp-hoook.php_bk – where not even Google has any reference to that spelling)

Hi

Is there any progress on this please?

Thanks

ian

Hosting company is Kualo – kgix.com
Server Information
Item Detail
Hosting Package MultiSite
Server Name hector
cPanel Version 86.0 (build 21)
Apache Version 2.4.43
PHP Version 7.0.33
MySQL Version 10.2.31-MariaDB-log-cll-lve
Architecture x86_64
Operating System linux
Shared IP Address 91.197.231.144
Path to Sendmail /usr/sbin/sendmail
Path to Perl /usr/bin/perl
Perl Version 5.16.3
Kernel Version 3.10.0-962.3.2.lve1.5.31.el7.x86_64

Thanks
Ian

Hi Alison

I think you may be onto something with the Wordfence scan.

If you go back on this thread and look at the graphs of my resource usage, there are fairly regular spikes (light green and very difficult to see). I suspect that these could be the Wordfence scans.

However, the fact that only one of your sites is affected, suggest to me that it might be worth listing the differences between that site and the others (eg a different plugin or theme or setting). (Sorry, but I am only guessing here). However, if any of your differences match any of my plugins/settings it might identify a potential cause.

Thanks

Ian

Hi asaracena

If we both have the problem after upgrading plugins, it seems to me that is could be one of those plugins that is making Wordfence crash. Thus if we try to see which plugins we have in common, we may be able to identify the plugin that is the problem.

You can probably work out from the hyperlink in my previous post, 5 plugins that I recently updated. eg broken link checker etc. Do you have any of the same plugins?

Thanks

Ian

Hi Gerroald

Thanks for such a prompt reply.

I will try that. However I still think this is somehow related to the error message from a week ago when updating a set of plugins. That message was as follows:

“Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Wordfence Security.

First, visit your website (https://www.perceptiondynamics.info/) and check for any visible issues. Next, visit the page where the error was caught (https://www.perceptiondynamics.info/wp-admin/update.php?action=update-selected&plugins=broken-link-checker%2Fbroken-link-checker.php%2Clitespeed-cache%2Flitespeed-cache.php%2Cstring-locator%2Fstring-locator.php%2Cupdraftplus%2Fupdraftplus.php%2Cw3-total-cache%2Fw3-total-cache.php%2Cwp-file-manager%2Ffile_folder_manager.php%2Cwp-staging%2Fwp-staging.php%2Cwordpress-seo%2Fwp-seo.php&_wpnonce=3b1252721a) and check for any visible issues.”

There seem to be others on the forum who are having similar problems. Is it worth checking if they have also had this error message?

However, I will try resetting wordfence as you suggest, and see what happens

Thanks

Ian

Hi Gerroald

Unfortunately, this is the reply I received from my web hosting support:

“Unfortunately, increasing this value is not possible within our shared hosting environments. That said, I would also not see this as improving performance, as your database activity is limited by the total computing resources available to your account, and since you had exhausted this increasing wouldn’t make a positive impact.”

Regards

Ian

Hi @wfgerald

Thanks for the reply

Below are the links to the screenshots and logs requested

resource

server error logs

php error logs

wordfence was disabled at 12-43 june 2nd (about the middle of the graphs) – where the faults stopped occurring on the resources CPU usage graph

Thanks again
Ian

Hello – is this plugin now dead/not suitable for recent WordPress versions? It seems a shame that such a good plugin has such a trivial bug that makes it unsuable after a WordPress upgrade. Any advice on the previous issue in this thread would be appreciated.

Sorry, but I am confused. I had the same problem yesterday. However, I am showing Version 2.8.4 – without any marker showing that an upgrade is needed.

My host provider has solved the problem by copying the file down – but I want to stop the problem happening again and do not know how to do that

Thanks for any help you can give