403 issues on plugin saves

  • Resolved Starhorsepax2

    (@starhorsepax2)


    6 years, 6 months ago

    We seem to be getting lots of 403 on some of our websites when working in the Dashboard. Oddly we can often get to other pages, just not whatever page /plugin we saved that triggered it.

    Our web host claims (I take this with a block of salt and suspect passing the buck) that Wordfence htaccess in the sub directories is the issue.

    So far its happened repeatedly with a plugin called WP Google Map Pro by Flippercode and some with Toolset.

    Here is a sample of the errors in cpanel( with details xxx out) [:error] [pid xxx:tid xxxxxxxxx] [client xxxxxxxxxx] client denied by server configuration: /home/xxxx/public_html/client/xxxx/wp-admin/admin-ajax.php, referer: https://xxxx/client/xxxxx/wp-admin/admin.php?page=toolset-settings

    The map plugin had similar error.

    We did NOT get any ‘this operation may be unsafe’ kind of thing, or warning asking if we want to whitelist, hence my skepticism that it is Wordfence. But I thought I should check with you just in case. It’s the latest Wordfence and its on auto update.

    Is there any conflict with Wordfence and these plugins that would cause it?

    Is there any setting on a server that would conflict with Wordfence? The shared hosting server was updated sometime right before this started as well but I don’t know the details.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support wfphil

    (@wfphil)

    Hi @starhorsepax2

    As you have mentioned that you are not seeing the Wordfence firewall block page then something else is causing this. Here are some possibilities:

    1) Misconfiguration on a server firewall.

    2) Your own custom HTACCESS file code.

    3) Another security plugin, if you have any installed.

    As you say that this is happening on a number of your sites, and if they are all hosted by the same provider, then if the only common denominator is point 1 above then I would ask your hosting provider to investigate further.

    Thank you,

    Plugin Support wfphil

    (@wfphil)

    Hi,

    Since I haven’t heard back from you I am assuming that the instructions solved your issue so I am marking this topic as resolved.

    If however, for whatever reason, you are still experiencing this issue and it is not resolved please respond to the post, which moves it back up the queue, and mark this topic as “not resolved”.

    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘403 issues on plugin saves’ is closed to new replies.