Mark Maunder

Hi Chief,

Tim asked me to come here and try to help. Looking at what you’ve posted I don’t see anything that’s clearly a problem.

I tried to click the link you posted in your initial post in this thread to see what your site looked like when it crashed, but that link doesn’t work anymore.

If you’re seeing a 500 Internal Server Error, then please ask your hosting provider to check the error logs for your web server or check them yourself. Whenever you have a problem in your .htaccess that is causing a 500 error it writes the error to that logfile and it will be quite clear what the problem is.

If you’re not seeing a 500 error then post what you’re seeing as a screenshot and I’ll take another look.

Regards,

Mark.

Firstly please delete the /wp-content/plugins/wordfence directory on your website to repair it.

Then sign into your website. Reinstall Wordfence. Then go to your Wordfence options page.

Please check the following:

Scroll down to where it says:

“Update Wordfence automatically when a new version is released?”

Do you see a red message talking about LiteSpeed web server?

Thanks,

Mark.

While I disagree with “some tables are poorly designed” I’m happy to help. This was a design choice by us because the table simply doesn’t need a primary key. But apparently this backup software does.

Two options come to mind:

1. Exclude wp_wfStatus from all backups. You don’t need to back this up. If your site fails as long as you can create the empty table Wordfence will function fine. The only thing you lose is the status messages of previous scans and Wordfence activity.

2. Run the following SQL which will create a primary key on that table. It won’t interfere with Wordfence function. Just remember that if you remove and reinstall Wordfence you need to recreate this primary key:

alter table wp_wfStatus add id bigint UNSIGNED NOT NULL auto_increment PRIMARY KEY;

Regards,

Mark.

Hi,

Just wanted to confirm that when you enable Falcon we ask you to back up your .htaccess – you probably are aware of this already – so just in case something happens you can restore it.

We don’t ever blank an .htaccess file, we only modify it. Quite a long time ago we had an issue that would corrupt the htaccess, not blank it. But that was fixed – it was due to a quirk in PHP and only happened very rarely. But not a factor now.

Regards,

Mark.

Yes this is a temporary issue and we’re working with the WP team to get downloads enabled again. Should be another few minutes.

Regards,

Mark.

OK I read it and don’t see anything that’s incompatible with what we’re doing.

Will take a look at PHP-FPM on apache with falcon and do some testing.

Regards,

Mark.

Hi Daniel,

Sorry about that – can you email me a ZIP of your plugin and I’ll whitelist it and also get that false positive taken care of. My email is mark at wordfence dot com.

Thanks!!