• Resolved lingcreative

    (@lingcreative)


    I have Wordfence free installed together with Jetpack. I have been getting a critical error stating that Jetpack is causing a problem but I just wanted to check that using the Jetpack 2FA isn’t causing a problem with Wordfence. Also are there any specific settings I need to switch on or off in Wordfence to stop any compatibility issues – I have seen something to do with XML-RPC problems but I am not very technically minded and would appreciate any directions on what I should change in Wordfence. Many thanks.

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

    (@wfpeter)

    Hi @lingcreative, thanks for reaching out!

    Jetpack most likely skips the normal WordPress login flow if using SSO, although I believe the 2FA you’ve mentioned is precisely for that feature so shouldn’t necessarily cause a conflict if our Login Security is turned off.

    Would it be possible to see a screenshot or copy/paste of the critical error you’re seeing? I’m just not certain whether it’s a Wordfence critical scan message, or a PHP error being displayed on your site.

    The XML-RPC issues you may have read about are down to a note before you turn on our 2FA to set Require 2FA for XML-RPC call authentication to “Skipped” if you use Jetpack (and the WordPress mobile app). This particular setting shouldn’t be an issue if you’re not using our 2FA.

    Let me know how you get on!
    Peter.

    Thread Starter lingcreative

    (@lingcreative)

    Hi Peter, thank you for getting back to me. It’s a strange one to be honest – when I try to do something in my wp site admin I’ll suddenly get a critical error warning and that an email has been sent with details. The last two emails detailing the errors gave the following info:

    On the site health page I got n error of type E_ERROR was caused in line 3665 of the file wp-content/plugins/jetpack/inc/lib/class.core-rest-api-endpoints.php. Error message: Allowed memory size of 41943040 bytes exhausted (tried to allocate 2621440 bytes)

    On the wp updates page I got the error of type An error of type E_ERROR was caused in line 2383 of the file wp-content/plugins/jetpack/inc/lib/class.core-rest-api-endpoints.php. Error message: Allowed memory size of 41943040 bytes exhausted (tried to allocate 2621440 bytes

    I spoke to my hosts and they tried increasing php and it didn’t change anything, they said it is definitely a plugin error. I tried uninstalling Jetpack and it still happened but I didn’t get an email! The thing is I’ve never had this before using Jetpack alongside WP AIOS. I opted to try Wordfence as it seems to be a far superior security option. Hence my thought that it may be one of my Wordfence settings that’s causing the problem. Hope this helps explain the issue better ??

    Plugin Support wfpeter

    (@wfpeter)

    Hi @lingcreative, thanks for the update.

    I don’t like batting an issue back at hosts, as we always try to find a solution where possible but errors like Allowed memory size of x bytes exhausted (tried to allocate x bytes), or Out of memory (allocated X) (tried to allocate X bytes) error is almost always memory exhaustion occurring outside of PHP somewhere on the server. There’s a chance that Wordfence’s scan, saving settings, or other Live Traffic operations triggered the error due to requiring some memory but it’s not the root cause from our tests with other customers.

    Your operating system/web server log files will likely show if memory is being exhausted somewhere outside of PHP and why. This is usually a job for your hosting company’s support channels as they have access to those logs, diagnose the source and potentially resolve the problem. Shared servers especially could be susceptible to this problem, but that’s just speculation and may not be the case for you.

    Thanks again,
    Peter.

    Thread Starter lingcreative

    (@lingcreative)

    HI Peter, thank you for getting back to me again. The saga continues! I decided to try again using Wordfence, as I would prefer that to AIOWPS, setting up everything without Jetpack. No more critical errors but I have been getting error 500 on some pages that then load on refresh. I also tried again with Jetpack and immediately got a critical error. After uninstalling all aspects of Jetpack it went back to just error 500 intermittently. I have wondered about it possibly being a hosting server problem so I will give them a try and see if they can help.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @lingcreative,

    Please also send us a diagnostic at the same time just in case we can find anything you can change with regards to the 500 errors. The 500 errors may be linked to something we can assist with, but if the memory errors are still occurring on top, they will need to be resolved at the server.

    Send a diagnostic to wftest @ wordfence . com directly using the link at the top of the Wordfence > Tools > Diagnostics page. Then click on “Send Report by Email”. Please add your forum username where indicated and respond here after you have sent it.

    NOTE: It should look as follows – Screenshot of Tools > Diagnostic > Send by Email

    Thanks again,
    Peter.

    Thread Starter lingcreative

    (@lingcreative)

    Hi Peter, diagnostic has been sent, let me know if you see what the problem. Many thanks for all of your help on this one. Lin

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Wordfence settings when using Jetpack’ is closed to new replies.