403 Forbidden A potentially unsafe operation has been detected in your request t

  • Resolved copc

    (@copc)


    6 years, 6 months ago

    Ok here it goes, so had site all set and client wanted to change domain names. So I backed up files and DB, got them moved and working on new URL.

    She then said when saving things in the admin she would get an error.

    
403 Forbidden
A potentially unsafe operation has been detected in your request to this site.

Generated by Wordfence at Wed, 23 May 2018 3:36:42 GMT.
Your computer's time: Wed, 23 May 2018 03:36:43 GMT.

    Did some reading about changing to learning mode, tried all kinds of things with no resolution. I finally decided to remove WF with option to remove tables on deactivation enabled.

    I still get the error? How do I get a WF error with now WF?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter copc

    (@copc)

    Nobody?

    Hi @copc

    Switching the firewall status into “Learning Mode” should help in this case, if you already tried that and it didn’t work, then I wonder if you have a caching plugin installed? perhaps you need to disable the database caching feature?

    Also, the deactivation process might be went wrong for some reason that wordfence-waf.php is still loaded, I suggest checking “.htaccess” or “.user.ini” and remove any Wordfence related entries, then recheck this issue. After that you can reinstall the plugin and reconfigure the firewall again.

    Thanks.

    Thread Starter copc

    (@copc)

    Figured it out on my own, thx

    I am having similar issue , would you please tell me how you resolve this issue by your own so i will try so.
    Thanks

    Im having a 403 error when a model tries to update her profile as well. Everytime! Anyone could help me pls?

    I had the same problem on a fresh WordPress install without WordFence plugin installed. But I had another WordPress in the root directory with WordFence active. So it seems WordFence once activated has impact on other WordPress sites when those are located in a subdirectory of a directory where an earlier WordPress config is located. I de-activated WordFence on the original site and now I can do the things I need to do on my fresh WP config without any 403 errors. Once done I’ll make WordFence active again.

    I have done all I can do to fix this 403 error when trying to re-authenticate the admin account in phpbb.

    I have deleted the wordfence plugin from every wordpress on the domain. I have gone into the MySQL and deleted all tables referring to wordfence. I have checked that adm and other folders in phpbb were set with 755 permissions. I have deleted the entire phpbb from the server and then reinstalled it. I have opened the phpbb discussion board in multiple browsers, including browsers that were never used.

    It doesn’t matter. The wordfence 403 error still happens when I try to go into the Admin area of phpbb.

    Why am I held hostage to this plugin, to which phpbb discussion boards does not even use?

    @broignatius1
    Did you already posted your issue on the WordFence support forum? -> https://www.ads-software.com/support/plugin/wordfence/

    • This reply was modified 5 years, 6 months ago by hendrikv.
    • This reply was modified 5 years, 6 months ago by hendrikv.

    As someone mentioned above, if you have another WordPress installation on the same server with Wordfence activated, disable that first then try again. This worked for me. Thanks!

    I thought about that. This means going into a dozen or more wordpress over multiple domains. erg.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘403 Forbidden A potentially unsafe operation has been detected in your request t’ is closed to new replies.

Tags