Optimizing firewall says The changes have not yet taken effect.

  • Resolved wzshop

    (@wzshop)


    3 years, 11 months ago

    Hi,
    So after clicking the optimize firewall button, I get the message below. Once I refresh the page, the message is gone and the firewall page says ‘Protection Level
    Extended Protection: All PHP requests will be processed by the firewall prior to running.’ Does this mean that optimizing the firewall is configured correctly and now active? Thanks

    The changes have not yet taken effect. If you are using LiteSpeed or IIS as your web server or CGI/FastCGI interface, you may need to wait a few minutes for the changes to take effect since the configuration files are sometimes cached. You also may need to select a different server configuration in order to complete this step, but wait for a few minutes before trying. You can try refreshing this page.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support WFAdam

    (@wfadam)

    Hello @wzshop and thanks for reaching out to us!

    Can you send a diagnostic report to wftest @ wordfence . com? You can find the link to do so 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.

    Thanks!

    Thread Starter wzshop

    (@wzshop)

    Hi,
    Thanks, did just that.
    Did find out that the tool said:

    Connecting back to this site
    wp_remote_post() test back to this server failed! Response was: cURL error 60: SSL certificate problem: unable to get local issuer certificate

    Is that problematic? Thank you!

    Plugin Support WFAdam

    (@wfadam)

    Thanks for sending that diagnostic over!

    Usually, the cURL error 60 is due to something going wrong with SSL or something interfering with it.

    I tested your SSL and it looks to have some issues: https://www.ssllabs.com/ssltest

    I would provide this information to your host so they can look into what might be causing it. While they work to resolve that we can try optimizing your site manually.

    It says your Server API is LiteSpeed. Using FTP or a file manager, navigate to your htaccess file and make sure this code is in it, also make sure the php_value auto_prepend_file path is pointed to your wordfence-waf.php correctly:

    # Wordfence WAF
<IfModule LiteSpeed>
    php_value auto_prepend_file '/path/to/waf/wordfence-waf.php'
</IfModule>
# END Wordfence WAF

    Let me know what you find!

    Thanks!

    • This reply was modified 3 years, 11 months ago by Yui. Reason: link removed
    Thread Starter wzshop

    (@wzshop)

    Hi,
    Thanks for getting back to me. The SSL ‘issue’ seems to be related to the under construction page/plugin, so no worries there.

    The htaccess file shows the code below. Let me know if I need to do some manual optimizing. Thanks again!

    PS: Please, could you remove my URL from your post?

    # Wordfence WAF
<IfModule LiteSpeed>
php_value auto_prepend_file '/path/to/waf/wordfence-waf.php'
</IfModule>
<IfModule lsapi_module>
php_value auto_prepend_file '/path/to/waf/wordfence-waf.php'
</IfModule>
<Files ".user.ini">
<IfModule mod_authz_core.c>
	Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
	Order deny,allow
	Deny from all
</IfModule>
</Files>

# END Wordfence WAF
    • This reply was modified 3 years, 11 months ago by wzshop.
    Plugin Support WFAdam

    (@wfadam)

    You can remove all of that except for the:

    # Wordfence WAF
<IfModule LiteSpeed>
    php_value auto_prepend_file '/path/to/waf/wordfence-waf.php'
</IfModule>
# END Wordfence WAF

    Make sure that you adjust your php_value auto_prepend_file path to the correct path to your wordfence-waf.php file.

    I will reach out to a mod to have your URL removed as it’s too late for me to adjust it.

    Thread Starter wzshop

    (@wzshop)

    Hi,
    Thanks again. Do I really need to remove it or can I leave it as it is and is it working now as well…?
    Any idea what caused the extra (false) lines to appear?

    Thanks

    Plugin Support WFAdam

    (@wfadam)

    You just want to make sure that your Firewall page says your WAF is 84% (which is the highest our free customers can obtain).

    If it’s 84% then everything should be good. If not, you will need to adjust that code.

    Thanks!

    Thread Starter wzshop

    (@wzshop)

    Hi,
    Did you mean 64% (as displayed on the Dashboard) and 55% (as displayed on the Firewall page)? Since the docs show:

    Free users can reach a max of 64% (as displayed on the Dashboard) and 55% (as displayed on the Firewall page).
    https://www.wordfence.com/help/firewall/?utm_source=plugin&utm_medium=pluginUI&utm_campaign=docsIcon#firewall-status

    I have this 64% and 55% score, so all should be good?
    Also, did you already reach out to a mod to remove my URL from your post?
    Thanks

    Plugin Support WFAdam

    (@wfadam)

    You could send me another diagnostic and I will tell you if it’s set up completely now.

    As for the post:
    The forums are managed by www.ads-software.com. We have no control over their rules, policies, or procedures.
    My team lead asked the forum mods to remove the link in question. The forum mods cited their policy of not removing or editing posts.
    If you wanted to ask them directly, you can reach out by joining the www.ads-software.com slack instance. You will want to join the “forums” channel.

    These are the instructions for joining:
    https://make.www.ads-software.com/chat/

    Sorry about the post!
    Thanks again!

    Thread Starter wzshop

    (@wzshop)

    Hi,
    I rather not send another diagnostic, but based on the percentage my configuration should be fine right?
    I will try and ask the people from wordpress, thanks.

    Plugin Support WFAdam

    (@wfadam)

    Everything looks good from what you have mentioned.

    Let me know if you need anything else!

    Thanks!

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Optimizing firewall says The changes have not yet taken effect.’ is closed to new replies.