Updating Failed When Wordfence is Enabled

  • Resolved adamscriptinside

    (@adamscriptinside)


    4 years, 9 months ago

    Hi there,
    Been using Wordfence on my separately hosted WordPress site for months with no problem.

    All of the sudden I have found it is giving me several problems, including updating or adding a new slideshow with the Metaslider plugin (Error: “Error fetching list of slideshows”) and even updating a page within my site (Error: “Updating Failed”).

    There a probably more issues that I haven’t come across. I know it is Wordfence as when it’s deactivated these actions work perfectly fine.

    I narrowed down the metaslider issue to being an access problem, trying to access the JSON route gave me nothing, whether or not this proves the above i’m not entirely sure, just assumed. Leading me to believe a certain, common updating action/request has been blocked through Wordfence.

    No expert though, seeing as why I’ve come here! Please help! Thanks.

Viewing 8 replies - 1 through 8 (of 8 total)

  • Hey @adamscriptinside,

    Can you please switch the Firewall into Learning Mode and let me know if it helps?

    https://www.wordfence.com/help/firewall/learning-mode/

    Please give this a try and let me know how it goes.

    Thanks,

    Gerroald

    Thread Starter adamscriptinside

    (@adamscriptinside)

    Hi @wfgerald thanks for your fast response. Putting into learning made no difference.

    Hey @adamscriptinside,

    Thanks for the update.

    Do you see any errors in the browser console when trying to save the slider? If so, can you please share a screenshot of them?

    https://www.wordfence.com/help/advanced/troubleshooting/#how-to-inspect-the-browser-console

    Can you check the Live Traffic entries for the block that happens when trying to update the slider and share the expanded Details for it? This may give us a clue as to what’s happening.

    Also, can you try disabling all other plugins with the exception of the slider and Wordfence and let me know if you’re still running into the issue?

    Please let me know.

    Thanks,

    Gerroald

    Thread Starter adamscriptinside

    (@adamscriptinside)

    Hi @wfgerald

    There’s just one error when trying to update a page:
    https://gyazo.com/34d489757ded7720cc7aade707355022

    A few more when using the Metaslider plugin, two seem to be generated by Metaslider:
    https://gyazo.com/f856fc48a31cdf1ecacbfb43777e2531

    Not sure how to see Live Traffic Entries as you mentioned, all I can see from Live Traffic within WF are blocked login attempts etc.

    Unfortunately, the site is live and running and certain functions are dependant on the plugins enabled so I cannot disable them for diag.

    I did disable Firewall as well as putting it into Learning mode which still did not make any difference, in case this narrows things down at all.

    Thanks for your continuing support.

    Thread Starter adamscriptinside

    (@adamscriptinside)

    Just an update,

    This has become a more serious issue now I have realised that when Wordfence is activated, people are unable to continue to paypal from checkout when on a mobile device – it works fine on desktop.

    This seems really random but I have tried deactivating Wordfence and it works fine when deactivated.

    Hey @adamscriptinside,

    Are you able to share your PHP error logs? If you’re not sure where these are your host can provide them to you. They likely contain more details about the 500 error when trying to reach the REST API endpoint.

    Also, do you have any plugins that you’re aware of that has the capability to block the REST API?

    For the mobile PayPal issue, can you please navigate to Wordfence > All Options > Additional Options and make sure the Block IPs who send POST requests with blank User-Agent and Referer feature isn’t enabled?

    Please let me know.

    Thanks,

    Gerroald

    Thread Starter adamscriptinside

    (@adamscriptinside)

    Hi @wfgerald

    The issue is fixed now. I contacted my Host and asked for the PHP Error logs which were:

    Backend fatal error: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32768 bytes)

    So they doubled Memory Limit to 256MB and post_max_size to 128MB and it seems to be working now.

    Not entirely sure why it wasn’t an issue when Wordfence was deactivated.

    Thanks for your help!

    Hey @adamscriptinside,

    Thanks for the update, and happy to hear it!

    This is a standard PHP memory error. Having Wordfence running was probably just the straw that broke the camels back, but not really specifically related to Wordfence.

    Please let us know if anything else comes up.

    Thanks,

    Gerroald

    • This reply was modified 4 years, 9 months ago by WFGerroald.
Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Updating Failed When Wordfence is Enabled’ is closed to new replies.