• Hi

    I have next case:

    1. Install wordfence and setup IP blocking for admin area

    2. Open site/wp-admin not from ip 88.208.6.49 and see block error (its ok)

    3. Open site frontend not from ip 88.208.6.49 and see block error (not ok)

    4. Open site frontend not from ip 88.208.6.49 and from another browser and see site (ok)

    Why when I firstly open wp-admin and then frontend I see block error on frontend?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @devsquadcore, thanks for your detailed description of what you’re seeing.

    Just as a piece of general information, we don’t recommend using “Allowlisted IP Addresses that bypass all rules” unless absolutely necessary, or that you can guarantee this IP will not be reassigned. That may not be a concern for you, but thought I’d mention it if anybody else searches out this topic.

    I would start by looking at your Live Traffic from when the “(not ok)” block on the frontend happened. Recreate the scenario if it isn’t easily found right now so it’s more recent in your list. The cause for that particular block will be shown in red text when expanding the entry by clicking it (or using the “eye” icon). This might reveal the block is connected to your Brute Force or Rate Limiting rules. It may also show if there’s a false-positive block happening or any your other settings are too strict for scripts that load on the frontend. Copy the red text here to us if it’s not immediately apparent to you what needs to change.

    Thanks,
    Peter.

    Thread Starter devsquadcore

    (@devsquadcore)

    Hi

    Here log

    And you can see options via import 4a18a83ceef855e824ce4ea8a1e3d0ebaf44d81e052a42c80238ef7dd5773d6a87a7268320227f5a874bd75f7f40da1790692237ff9ff8b5230d5e63e8b0a006

    Thread Starter devsquadcore

    (@devsquadcore)

    @wfpeter can you help me?

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Why block all site’ is closed to new replies.