Plugin Conflict?

Hi @jahrat, thanks for asking about this.

The example from the .htaccess above has been edited by the forum to remove markup (I think), but it resembles the code we add when a scan alerts you to a publicly visible .user.ini file:

# Wordfence WAF
<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

That shouldn’t prevent the site from loading, simply viewing the file in a browser. You could choose to omit this if you believe it is causing problems though. The more common problem that could prevent a site from loading is if the path to wordfence-waf.php is incorrect in .htaccess, resulting in a 500 error – which may present as a blank page in a browser:

; Wordfence WAF
auto_prepend_file = '/your/path/to/wordfence-waf.php'
; END Wordfence WAF

Either way, that’s not a plugin conflict, but the firewall will run in Basic Protection rather than Extended Protection if that line is omitted. To combat the problems with your site loading it’s important that the path to wordfence-waf.php is correct, although the Optimization Wizard inside the plugin should detect that path correctly. Are the hosting company able to confirm which .htaccess change was causing the errors from the server logs?

Many thanks,
Peter.

Hi Peter,

Thanks for the reply. They did not indicate a specific line for the problem but rather replaced the entire file with an older copy of a working file. I do not see your auto prepend command in either of those files.

As far as the server log goes, the last entries in the error log are below (redacted)
[core:alert]…/…/gmc-mca.org/.htaccess: # without matching # section
[core:alert]…/…/gmc-mca.org/.htaccess: # without matching # section, referer: https://gmc-mca.org
[core:alert] …/…/gmc-mca.org/.htaccess: # without matching # section, referer: https://gmc-mca.org/events/…/
[core:alert] …/…/gmc-mca.org/.htaccess: # without matching # section
[core:alert] … /…/gmc-mca.org/.htaccess: # without matching # section
[core:alert] … /…/gmc-mca.org/.htaccess: # without matching # section

As mentioned, however, the only references in the htaccess are from waf, rsssl and cache..

Hi @jahrat,

That’s interesting because that might suggest the # Wordfence WAF section was opened without # END Wordfence WAF following it at the end. Is there any chance it presented without the # in the file rather than just here on the forum? Having said that, because the problematic section isn’t specifically named I can’t be certain there wasn’t other code created by another plugin that also wasn’t “closed” in this way.

Thanks again,
Peter.

You are correct in that the excerpt was not accurate. The hashtags are all there.

I will close this topic as it does not seem like a conflict caused by wordfence.

Thanks for your help.