• Resolved rewollof

    (@rewollof)


    Hi.
    I can’t publish posts on my test site because of error (redirects to page with 403):

    A potentially unsafe operation has been detected in your request to this site
    Your access to this service has been limited. (HTTP response code 403)

    If you think you have been blocked in error, contact the owner of this site for assistance.

    Block Technical Data
    Block Reason: A potentially unsafe operation has been detected in your request to this site
    Time: Sat, 19 Dec 2020 20:55:17 GMT

    (logo of Wordfence at the bottom and “Click here to learn more: Documentation”)

    I’ve deleted Wordfence on my test site and still see this error. What’s wrong?

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

    (@wfpeter)

    Hi @rewollof, sorry to see you’re having this issue.

    The message you’re seeing sounds like a case for Learning Mode, as for some reason, something about the post operation is being flagged as unsafe.

    From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now try publishing a post again. This will help Wordfence learn that these actions are normal and it will allow them in the future. After you have finished performing the actions, switch the WAF from Learning Mode back to Enabled and Protecting. Now test to see if the publish action is still working correctly.

    https://www.wordfence.com/help/firewall/learning-mode/ is an amazing resource for learning more about the WAF and learning mode.

    Thanks,

    Peter.

    Thread Starter rewollof

    (@rewollof)

    I’ve used the db dump from the production in the test site. There are no problems right now (without any manipulations with wordfence options on the prod.)

    Thread Starter rewollof

    (@rewollof)

    It happened again. I’ve tried to update post on my test site and have seen 403 error with the wordfence notification. I’ve switched it in to the learning mode on the main site and the problem has gone. Why does it happen? How can wordfence block another domain (reminder: i’ve removed wordfence on the test site)?

    Plugin Support wfpeter

    (@wfpeter)

    Hi @rewollof,

    Sometimes due to plugins/themes, especially in the case of something like a page-builder that changes POST data to your database, the action can sometimes be flagged as unsafe if it differs from the default WordPress action. This is not necessarily the reason in your case but a common example. However, as you were performing the action yourself, it is safe to teach Wordfence to allow it.

    Remember to switch the WAF from Learning Mode back to Enabled and Protecting if you haven’t already now that the problem has been rectified.

    Thanks again,

    Peter.

    Thread Starter rewollof

    (@rewollof)

    Ok, i’ll try to work with this knowledge:) Thanks

    Plugin Support wfpeter

    (@wfpeter)

    No problem @rewollof! If you need any further Wordfence advice in future, start a new topic and we’ll be glad to help you out any time.

    Thanks again,

    Peter.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘403 when i want to publish the post’ is closed to new replies.