When the site is behaving badly

Find the real cause of a problem fast, and fix only the one setting that needs it.

When a site has a problem, the first idea is often "turn the security plugin off". The problem goes away, but so does all protection. And when you turn it on again, the problem comes back, because the setting that caused it is still there.

Pick the problem you see, follow its short list of steps, and open the page that explains the right setting. You fix the cause, and your site stays protected.

BotBlocker Dashboard protection controls

The protection switch and the Secret links button. Open them from BotBlocker → Dashboard.

Three rules that make every fix easier

  1. Look before you change. Find out what really happens: who is affected, what they see, and since when. The visit log in Traffic and audit logs shows why BotBlocker made each decision.
  2. Change one thing at a time. Test after each change. If you change five settings at once, you do not know which one helped, or which one made a new problem.
  3. Pause, do not conclude. The pause switch on the Dashboard is a good test: if the problem stays with BotBlocker paused, BotBlocker is not the cause. But a pause is only a test. Turn protection back on when you know the answer.

If the log shows nothing for a request, BotBlocker probably never saw it. Then the cause is in front of the site (a CDN or firewall) or outside the plugin.

My visitors are blocked

  1. Ask what the visitor sees. A CAPTCHA page, a block message, and a page that never loads are three different problems.
  2. They see a CAPTCHA page. BotBlocker asks for proof. It does not refuse them. Check that the check works on their device. Read CAPTCHA and Verification overview.
  3. They see a block message. Find the visit in the log and read the reason. Read Monitoring overview and Traffic and audit logs.
  4. Only VPN, office, school, or mobile users are affected. Read Network connection types.
  5. Only private windows, ad blockers, or unusual browsers are affected. Read Browser checks.
  6. Only an app's built-in browser is affected (for example Facebook or Instagram). Read In-app browsers.
  7. One form, shop, integration, or payment flow fails. Read Blocks and responses, Responses and API access, and Payment callbacks.
  8. Change the one setting that fits, and ask the visitor to try again.

I am locked out

  1. You can still open the Dashboard. Use the pause switch on the Dashboard, then fix the setting that caught you.
  2. You cannot open the Dashboard. Use your recovery links. Try Disable current check first. Use Fully disable BotBlocker only if that does not help.
  3. An early mode is on. It runs before WordPress. Read Early phase and MU mode and Early Init for how to turn it off.
  4. The login page is the problem. Read Login brute-force protection and Two-factor authentication.
  5. When you are back in, fix the cause before you turn protection on again. Turn on Auto-save administrator IPs, so your own connection is remembered.
  6. If you used a recovery link, regenerate the links and store the new ones.

The site is slow or down

  1. Pause protection and compare. If the site is still slow, look at your host and other plugins too.
  2. Traffic comes in bursts, or one network floods the site. Read Rate limiting. Also think about the Behavioral Analysis add-on for bots that come back.
  3. Slow after contact with the cloud. Read Cloud API, mainly the request timeout.
  4. Pages are slow but visitors are not blocked. Check where BotBlocker stores its data: Performance and storage overview and Cache backends.
  5. Logging grew suddenly. Read Traffic and audit logs. More logging means more load and storage.
  6. Many bots on your block list still load WordPress. Move the IP check earlier with Early phase and MU mode.
  7. The site does not load at all. Pause protection if you can open the Dashboard. If you cannot, use the recovery links. If a recent change caused it, restore your backup.

Something changed after an update

  1. Open the home page and the admin area once, and look carefully at what is different.
  2. An early mode is on. Check it with Early phase and MU mode. Turn it off if the site acts strangely.
  3. Cron jobs, updates, or the site's own requests fail. Read the self-connection settings in Network connection types.
  4. Old content or settings show. Clear the cache: see Cache backends and Clear Object Cache in Maintenance actions.
  5. A rule now fires differently. Compare recent decisions in Traffic and audit logs.
  6. You saved your setup before. You can load it again with Import data and settings in Tools. An import replaces your current setup, so export it first.
  7. Nothing explains it. Restore your full site backup, then change settings again one at a time.

When nothing on this page helps

  • Every path leads nowhere? Pause BotBlocker and test. If the problem stays, the cause is outside BotBlocker.
  • You fixed it, but it comes back? You probably turned protection on again without fixing the cause. Look in the log for the rule that fires.
  • You need help from support? Download the debug log with Download Debug Log in Tools, and describe what changed and when. Never send your recovery links.
  • You cannot explain the change, and the site does not recover? Restore your backup, and import your last BotBlocker export from Tools.