Jelena

Hi,

Thanks for your question.

The ‘Enforce Email Authentication’ option is located under the main Security Zones menu. Select ‘Login’ (click the gear icon next to it), then go to the ‘2FA: Email’ tab.

In your case, make sure the ‘administrator’ user role is included in the ‘Enforce Email Authentication’ list field.

We also have a complete guide on this here.

Hope this helps.

Jelena

Hi,

Thanks so much for your thoughtful and supportive review! 🙂

We’re really glad Shield is making a difference for your site and that you’ve had a positive experience with both the features and our support. Feedback like yours motivates us to keep improving.

Thank you especially for suggesting geo-location blocking in Shield — we’ve definitely noted it for review.

Geo-blocking is based on IP addresses, which aren’t always reliable. That’s why Shield doesn’t offer country-based IP blocking—IP addresses can be spoofed, and botnets often use thousands of different IPs and we block them automatically.

If you want to block traffic from certain countries, you may check if your hosting provider supports server-level GeoIP blocking—they may be able to set it up for you.
Additionally, you can combine Shield’s automatic IP blocking with Cloudflare’s geo-blocking and CDN. Shield blocks malicious IPs, while Cloudflare improves performance and filters traffic by region. Together, they create a strong defense against threats and improve sites performance by stopping harmful traffic before it reaches your site.

Hope you find this helpful in some way…

Regards and we truly appreciate you being part of the Shield community.

The Shield Security Team 🛡️ 🙂

Hi Amanda,

Sorry to hear about the continued trouble with this.

Since the issue was previously resolved by disabling Shield’s HTTP Headers options, it’s possible that something has changed after that—such as a WordPress update or another plugin/theme—that’s causing the issue to return.

Here’s what you can try:

Confirm Header Settings: Re-check if the HTTP Headers settings are still disabled in Shield. If they were re-enabled, disabling them again might fix the issue.

Clear and Disable Cache: Sometimes, caching can cause outdated settings or pages to load. If you’re using a caching plugin or browser, consider clearing cache and temporarily disabling it, force refresh the site (F5) and testing the issue again.

Check for Plugin or Theme Updates: If any other plugins or theme were updated just before the problem reappeared, there could be a compatibility issue affecting the Customizer’s functionality.

Review Console & Network Tab: Checking the browser console and network tab (as previously suggested) might reveal new errors that weren’t there before.

Test on a Different Theme: If the issue is theme-related, switching to a default theme could help determine if the theme itself is conflicting with Shield.

Temporarily Disable Other Plugins: Even though Shield’s HTTP Headers were previously identified as the cause, another factor—such as a recent plugin or theme update—might now be contributing to the issue. I recommend disabling one plugin at a time and testing the Customizer after each deactivation to see if the issue is resolved. You can do the same with themes. This can help pinpoint if any other plugin/theme is causing the conflict.

Let me know how it goes,

Thanks.

Hi Alvaro,

The CrowdSec should be automatically cleaned. If it’s not, then there’s likely an issue with the site’s cron jobs not running correctly. You should check for errors in the server logs and use a tool like WP Crontrol to monitor and debug any cron issues.

You can cleanup the Crowdsec table manually by using a tool like phpMyAdmin, which is available in most web hosting control panels. Access the database for the site in question and locate the table named wp_icwp_wpsf_crowdsec_signals. Then, “truncate” the table (this will clear its data but keep the table structure intact). Again, this should be processed by a correctly functioning of WP Cron.

Also, may see some errors in the logs for up to ~30 seconds after truncating the table, as Shield detects that the table is empty. It will then automatically rebuild the table, and you should be back to normal.

Jelena

No, snapshots isn’t a separate feature and can’t be disabled because that’s a part of the Shield’s functionality.

When Shield is running, it creates 1 set of tables for the site, around 20 tables.
The more features, the more tables that are required; the less features, the less tables are needed. The number of entries in those tables will depend on your site’s activities. We run a very tight ship, however, and we designed these tables and how Shield queries the database with performance in-mind.

Regarding your related question about the wp_icwp_wpsf_crowdsec_signals table here, if it’s causing issues with overloading your database, you can disable Crowdsec feature from Security Zones main menu > Bots & IPs zone > Crowdsec IP Blocking.

Additionally, if your site is buys (active), perhaps you can also use the Log Retention option to automatically purge WordPress Activity and Request Logging (traffic) entries from the related tables – events older than the set period will be removed from the database automatically.
(If you’re using the free version of Shield, the max retention is 7 days. You can set it to 2 or 3 days if needed.)
Please also note that the Request Logging (traffic) expiry will depend on the WordPress Activity Log as the Activity Log relies on data from the traffic log too.

Hope this helps.

It’s been three days since your last message, so I’ll close this out for now. If you still have any questions about Shield, you can always reopen the conversation.

Thanks.

Hi Raffaella,

If you’re able to delete some tables but not others, it’s likely due to permission or database-specific issues (restrictions) with those particular tables.

I suggest checking with your web host to see if this is the case, or asking them to remove the tables for you, including the autoload.