Mark Maunder

Hi,

We don’t have an export function but will have this in the near future.

Regards,

Mark.

I’m sorry I don’t understand this part:

“I end up with even Wordfence Your API Key”

Regards,

Mark.

Thanks Damon, I think what’s happening here is that you’re right, the site is generating 404’s and the reason this happens is because we call those functions in a rather unorthodox way.

If you look at the URL’s you’ll notice that we hit the home page and set some query string vars which are intercepted by Wordfence which then generates the test results.

We’re considering changing this, but until then…

What usually causes these to malfunction is the customer theme which is doing something non-standard with home page requests. I can’t really suggest a workaround other than changing your theme if you can (not really an option for most folks).

We’ll change the way this works in a future release.

Regards,

Mark.

Hi,

We are introducing a new feature in the next release that lets you define usernames where if a hacker tries to sign-in using one of the usernames, they will be immediately blocked.

You can thank my co-founder Kerry for this – she literally mentioned that we need to get this feature in the next release less than an hour ago because many of our users are asking for it. It sounds like it will solve your problem.

Regards,

Mark.

Hi,

The warning at support.wordfence.com was a temporary SSL certificate issue – our provider FreshDesk upgraded our cert without giving us time to make a DNS change which resulted in the warning, we’ve backed out the change and it’s fixed now.

Please post a screenshot if you can.

Regards,

Mark.

Hi,

You can find an answer to this on our support site here:

https://support.wordfence.com/solution/articles/1000010693-i-ve-locked-myself-out-of-my-site-i-ve-tried-the-email-unlock-feature-and-it-didn-t-work-what

Please note that our ticketing system provider is busy upgrading our SSL certificate so just ignore the warning you get when you try to visit that URL. (Not our fault, sorry)

I’m going to paste the whole page here to save you time:

The following instructions are for site owners. If you are trying to regain access to a site that you do not manage, please contact the site owner for access.

First please make sure that it’s actually Wordfence that is locking you out of your site. There are many plugins that offer a “lock out” feature and quite a few of them that don’t work well.

If you are locked out by Wordfence you’ll see a message giving you a reason you’re locked out and explaining how to unlock access to your own site. Whenever Wordfence locks a user out it provides a “Reason:” with a reason describing why you’re locked out. You can use this reason to determine which firewall rule you need to modify to prevent this from happening in future.

If you post on the forums, make sure you include the “Reason: [explanation]” text or a screenshot of the locked-out page so that we can tell you what to change to prevent getting locked out in future.

Here’s how you regain access to your site: The easiest way to solve this problem immediately is to simply delete the Wordfence files from your WordPress installation. You can do that as follows:

Connect to your server using the method your normally use to upload files. Most people either use FTP or SFTP to do this.
Remove the Wordfence directory (or folder if you prefer). If your site has the standard WordPress structure, you can do this by simply deleting the wp-content/plugins/wordfence/ directory and everything underneath it.

The above procedure will immediately unlock your site. If you are still seeing a message that you’re locked out, make sure you disable any caching plugins like W3 Total Cache, or clear their cache. If you can’t access the site to disable the caching plugin, you may have to temporarily rename the caching plugin directory to disable it. You may also have to clear any caches on a front-end caching proxy if you have an advanced configuration.

In the highly unusual case that you don’t have access to your own files on your server, you will need to log a support call with your web hosting company or whoever manages your server and ask them to delete the wp-content/plugins/wordfence folder.

How to reinstall Wordfence once you’re regained access:

Once you have disabled Wordfence, if you reinstall it, you may be locked out again. Here is how you avoid this from happening:
Don’t install or activate Wordfence yet.
Install the Wordfence Assistant plugin. You can find it by going to Plugins and Add New. Then do a search for “wordfence assistant” without quotes. You can also find it on this page in the official Wordfence plugin repository.
Activate the plugin.
Go to the “WF Assistant” menu.
Click the button to disable the Wordfence firewall.
Now you can install and activate Wordfence itself and you won’t be locked out.
Once Wordfence has been activated, disable the feature of Wordfence that locked you out.
Then reactivate the Wordfence firewall by going to the Wordfence options page and checking the box to activate the firewall and hit Save.
You can optionally uninstall the Wordfence Assistant plugin.

Hi,

@netcentsii: You’re using LiteSpeed web server and were suffering from an error which was fixed in the latest release. Please upgrade and you should be fine.

@duffdaddy: As a paying customer please log a support ticket at http://support.wordfence.com/ and we’ll get you squared away with priority support.

If you already have, please let me know and I’ll chase it up.

Regards,

Mark.