How to Increase THRESHOLD

Hi Peter,

Thanks for working on it.

I will now discuss this with the host and let’s what they to resolve it. I will update you about this.

Regards
Farrukh

Hi @faarukh,

Let us know how you get on. For your reference, tickets without further response normally remain open for around 7 days in the forum, so feel free to let us know in that timeframe if there’s a little more time required so that the topic stays active.

Thanks,

Peter.

Hi Peter,

My hosting guy export the database then reimport the data into another database to see if that helps but the scan failed again.

The second thing he told me that he will rebuild the database from scratch but I don’t want to do this on my website.

Anything you can say about this?

Regards
Farrukh

Hi @faarukh,

I think one other thing we can check is when you state the scan failed again in your last message, does it contain the same message about the cronKey or something else this time?

You could check the logs again too, to see if the MySQL server has gone away message or others are still occurring in conjunction with the scan failures. If so, the host may still have unresolved issues.

Thanks again,

Peter.

Hi Peter.

Here is the reply from hosting:

“I looked through the MySQL logs and ran a repair on your databases again but I couldn’t find any errors on my side.

Even with all the scanning options and directories disabled it still fails.”

Regards
Farrukh

Hi @faarukh,

If the host has indeed fixed the initial issue of the MySQL server, I did notice that you are on a LiteSpeed server. There have been cases in the past, where LiteSpeed server will kill PHP processes without warning and without error messages. I think this may be what is happening on your site.

You should be able to prevent this behavior by adding one of the following codes to the .htaccess file that is located in the root of your site.

# BEGIN litespeed noabort
<IfModule rewrite_module>
RewriteEngine On
RewriteRule .* - [E=noabort:1]
</IfModule>
# END litespeed noabort

In some cases, depending on the host’s configuration, the above code may not help. An alternate method which may work is this:

# BEGIN litespeed noabort
<IfModule Litespeed>
RewriteEngine On
RewriteRule .* - [E=noabort:1]
</IfModule>
# END litespeed noabort

OR

# BEGIN litespeed noabort
SetEnv noabort 1
# END litespeed noabort

We have a bit more information on this in this page in our docs: https://www.wordfence.com/help/advanced/system-requirements/litespeed/`

Thanks again,

Peter.

Hi Peter.

This method is not working too.

My hosting guy says that there is something within the database or conflicting data that makes that scan failed.

So what I do next?

Regards
Farrukh

Still waiting for the reply.