If you are a free customer, please post your issue in these forums.
Priority support for paid premium customers is available at:
As a premium paid customer you can open tickets on the site above and you will receive priority support. Free customers can also visit the site above and search our knowledge-base for known issues.
If you're a free customer you're welcome to post in these forums and we will read and respond to your post. If you'd like to get a fast and friendly response from us, please help us by following these simple etiquette guidelines:
Please keep your posts as short as possible. It lets us respond to more posts per day because we have less to read in order to understand your problem and respond.
Do not hijack someone else's post. If you have a problem and hope to get help, please start your own thread. Don't reply to someone else's thread saying "I have the same problem, here's my information, how can I fix this.". Only reply if you're adding information that may help the original poster and don't need help yourself.
NOTE: When we ask for your "web server error log" we do not mean your "access log". Three out of four people post entries from their "access log" when we ask for their "error log". This does not help us help you and delays the process because we then need to tell you that you posted the wrong thing and we actually need your "error log". So please make sure you understand the difference and send us the correct data. Your access log only shows who has accessed your site and we don't need that data. Your web server error log (usually your Apache error log if you're using Apache web server) is where your web server writes errors and that's what we need. If you're unsure where to find it, log a support call with your hosting provider and ask them for it.
If you can't get scans to start or if they're not completing, please get access to your web server error log (see above) and then try to start a scan. When it fails, check the error log and post the newest entries here making sure passwords, usernames and other sensitive info is removed. You'll probably see an error that you've run out of memory, a process has been killed or a PHP error naming a Wordfence file and a line number. That's what we need you to share with us to be able to help you.
If you're a technical user and know how to get around in a linux shell, can give us temporary SSH access to your server which includes the ability to tail your error log and also give us temporary admin access to your WordPress site, let us know in the post and we MAY provide free priority support for you. The reason we do this is because it gives us full diagnostic access with a high likelihood of solving your problem which may provide a solution for other users. Plus working with highly technical users consumes much less time. We're happy to help the less technical folks on the forums but it may take slightly longer.
We do read every post that appears here and we make every effort to give you a timely response. We value our free community as much as our paid customers.
Thanks for choosing Wordfence!!
Wordfence Founder & Feedjit Inc. CEO.