Problem with Rename WP Login feature

  • Hello,

    I have activated this option, and it worked… until I encoded my access codes.
    I was then faced with this message:
    “You were blocked by the WordPress Simple Firewall. Something in the URL, Form or Cookie data wasn’t appropriate.”

    Weird, because my static IP address is whitelisted in the “Dashboard” page.
    I tried from another computer, using a different IP address: same result!
    In the end, I used the forceOff file to regain access, and disable the option.

    It is a single site WP, installed via FTP, nothing special…

    Did I go wrong somewhere?
    Or is there a bug?

    Regards,
    Francois

    https://www.ads-software.com/plugins/wp-simple-firewall/

Viewing 6 replies - 16 through 21 (of 21 total)
  • Thread Starter Fran?ois G.

    (@frg62)

    And when the not whilisted address trie to connect, here is what appears in the Audit Trail Viewer:

    Event
    firewall_block

    Message
    Page parameter failed firewall check. The offending parameter was “redirect_to” with a value of “https://XXX.XXX/wp-admin/”. Firewall Trigger: Leading Schema. Firewall Block Response: Visitor connection was killed with wp_die() and a message.

    Username
    unknown

    Category
    3

    It seems that the redirect option is a bit unstable, or am I wrong?

    Plugin Author Paul

    (@paultgoodchild)

    What’s happening here is that the Firewall option to block “schema” is actually blocking your login redirect.

    This isn’t a “problem” with the firewall – it’s actually performing correctly based on its configuration.

    I don’t personally use the block schema option for the firewall, but it was originally included as this plugin started a continuation from the “Firewall 2” plugin. That option isn’t enabled by default when the Simple Firewall is installed.

    There are multiple features running on the firewall and the rename works fine in principle, but if you have URL components that otherwise trigger the Firewall component of your plugin, then it doesn’t matter if its your WordPress login URL or any other page on your site, the Firewall will trigger and then block you.

    Does that make more sense?
    Thanks for reporting back your findings, appreciate your efforts and feedback.
    Paul.

    Thread Starter Fran?ois G.

    (@frg62)

    You are right indeed!
    That option was differently configurated on those two WPs.

    Thanks for the explanation.

    I would recommend a note, to be dispalyed next to the redirect option (or next to the “Block Leading Schemas” option), to avoid the same confusion from other users…

    Regards,
    Fran?ois

    Thread Starter Fran?ois G.

    (@frg62)

    Thinking further, I think this behaviour is quite puzzling, because it means that the “Ignore Administrators” option is simply ignored in that specific case…

    Plugin Author Paul

    (@paultgoodchild)

    Yes, the ignore administrators is an “old” option before whitelists became global.

    It’s still a relevant option if you don’t have a global IP whitelist and you’re already logged-in. It wouldn’t take effect with the rename wp-login because according to WordPress, you’re not administrator because you’re not logged in ??

    Cheers,
    Paul.

    Thread Starter Fran?ois G.

    (@frg62)

    It makes sense…

    Regards,
    Fran?ois

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘Problem with Rename WP Login feature’ is closed to new replies.