wfscott
Forum Replies Created
-
Thanks for your feedback and for being a long-time Wordfence user. I’ve reviewed the support ticket, and based on the timeline, your site appears to have started experiencing issues after the host made a change to the environment. We have been following up daily since the issue was reported and have responded to each of your questions, including a response earlier today. I understand the troubleshooting process can feel slow when your site is affected, and I apologize for any inconvenience.
We’re committed to getting this resolved for you and will continue to work with you via Premium support.
Thanks
Hello, @densitysk
Thanks for reaching out.
Can you please confirm your IP detection is configured properly on your site? For that, first note your device’s IP address. Then, navigate to the Wordfence > All Options > General Wordfence Options section, and under How Does Wordfence Get IPs, check the Detected IP(s) and Your IP with these Settings fields. That should show your personal IP.
If you’re seeing a different IP, try selecting the “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.” option, if you haven’t already. If that is already selected, and the IP detection is still incorrect, try cycling through the other options. Remember to use the Save Changes button if you make any changes.
If the IP detection was misconfigured and you make a change to correct it, that should fix the issue the users were seeing.
The block message the users are seeing is due to breaking the rule for Immediately block the IP of users who try to sign in as these usernames in Wordfence > All Options > Brute Force Detection.
You may have a username listed there that is close to a real username on the site, or a user may have tried logging in with an incorrect username that is on that list. Please note that the usernames added there will only result in a block if they are not registered usernames on your site.
Let us know if you have any questions.
Thanks,
ScottHello, @bobjgarrett
Wordfence will not display rate limiting blocks when Rate Limiting is set to “Unlimited” unless an active block is still in effect from your prior Rate Limiting settings. You can check for active blocks in the Wordfence > Firewall > Blocking > Current Blocks for your site section. If you’re seeing a block that doesn’t show a Wordfence logo on the block screen, the block is likely coming from a different plugin or security configuration on your site.
If you’re seeing a block that shows the Wordfence logo, please let us know the reason shown in the red text on the block screen. At that point, I recommend also checking the Wordfence > Firewall > Blocking > Current Blocks for your site section for any blocks that reference your IP or an IP you frequently use. You will see a reason for the block in that section and can remove it there if necessary.
If you have any questions, please let us know.
Thanks
Hello, @pointsofyou
Can you confirm whether you’re seeing any direct indication that Wordfence is blocking the details from being sent? Are you seeing any blocks in the Wordfence > Tools > Live Traffic section at the exact time those should be sent, or any additional details via your raw access logs?
Thanks
Hello, @goaskmrsg
Thanks for your patience.
Can you confirm if you’re seeing a Wordfence block or otherwise while trying the Sign in with Google functionality?
Additionally, please send us diagnostics via the “Send Report by Email” button at the top of the Wordfence > Tools > Diagnostics page. Please add your forum username where indicated, and send those to wftest@wordfence.com. Please respond here after you have sent those.
Thanks
Hello,
Please send an email to lockout@wordfence.com and provide the email address associated with the Wordfence account, and we’ll assist you with the account access there.
Thanks,
ScottThanks for your patience here. I see from your diagnostics that most of the Wordfence database tables are missing. This could be due to a database permission issue. Before checking with your host and reviewing the MySQL logs, can you try deactivating the Wordfence plugin and then reactivating it from your Plugins section? At that point, try the license installation again. In some cases, this will create the tables and allow the license to be installed. If the issue persists at that point, I recommend checking with your hosting provider to determine why the database tables are not being created. You can see the table status in the Wordfence > Tools > Diagnostics > Database Tables section.
Thanks,
ScottHello, @blakemcclung
This can sometimes be a plugin or theme conflict, or due to a database issue, such as a corrupt table or database permissions. If you are able to access the Wordfence > Tools > Diagnostics section, you can check the Database Tables area to see if any Wordfence tables, such as wfconfig are labeled as corrupt or crashed.
From the Wordfence > Tools > Diagnostics section, at the top, please use the Send Report by Email button and send the diagnostics to the default wftest@wordfence.com email address. Please put your forum username in the second field there.
Let us know here when that is sent and we’ll take a look.
Thanks
Thanks for the feedback and for your review, @ideaup. We’re happy to hear you’re protecting all of your sites with Wordfence!
For the Premium version, you can consider reaching out to us at
presales@wordfence.comto discuss our bulk discounts.Forum: Reviews
In reply to: [Wordfence Security - Firewall, Malware Scan, and Login Security] Das BesteThanks, @hanspeterdohr. We appreciate you taking the time to share your feedback!
Hello, @mahioo
Thanks for sending over the information. The error you’re seeing could be due to a file-locking issue. The recommendation is to switch to our MySQLi storage engine, which stores the firewall data in the database rather than in files in the wflogs folder.
Our documentation on putting that in place is here: https://www.wordfence.com/help/firewall/mysqli-storage-engine/#switching-to-the-mysqli-storage-engine
For that, you will need to add the following line to your “wordfence-waf.php” file (if your firewall is optimized):
define('WFWAF_STORAGE_ENGINE', 'mysqli');If you have not optimized the firewall, you could add the line to the WordPress “wp-config.php” file as described on our constants help page instead.
You can check whether the firewall is optimized by going to Wordfence > Firewall > All Firewall Options > Protection Level. If you see an Optimize Wordfence Firewall button, then the firewall is not currently optimized. I recommend backing up any files before modifying them.
Let us know if that helps or if you have any questions.
Thanks,
ScottThanks for your patience.
Do you have any server logs from around the time the issue occurred? If so, you can send those to the
wftest @ wordfence . comemail with your forum username as the subject, and let us know here when those are sent.Additionally, if you’re able to lower your maximum_execution_time to 30, I recommend trying that for a period as well to see if the issue persists.
I also recommend enabling debugging in WordPress to see if any errors show at the time you’re experiencing the issues. You can find more information about how that’s done here: https://wordpress.org/documentation/article/debugging-in-wordpress/.
For that, you would add (or edit) these three lines to your wp-config.php:
define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, false );Let us know what you see there or if you have any questions.
Thanks,
ScottHello, @rinart73
Can you please send over diagnostics from Wordfence > Tools > Diagnostics > Send Report by Email to
wftest @ wordfence . comPlease put your forum username in the second field there, and let us know here when those are sent.
Thanks
Hello, @richardkent001
Thanks for reaching out.
Those errors may be displayed due to a setting with the hosting provider, or if
define('WP_DEBUG_DISPLAY',true);is defined in your wp-config.php file.Via the wp-config.php file, I recommend setting that directive to false, like so:
define('WP_DEBUG_DISPLAY',false);That should prevent the errors from displaying on the page.Thanks
Hello, @alberg15
Can you please confirm if you see the same error if you log in via an Incognito/private window?
Also, please send over diagnostics via the Wordfence > Tools > Diagnostics > Send Report By Email button. Send those to the default
wftest @ wordfence . comemail with your forum username in the second field. Please let us know here when those are sent.Thanks