Hi @marcguay, I apologize for the delay in getting to your diagnostic which hadn’t reached our inbox. I’ve now tracked it down.
I don’t think the path of /public_html/wp
should be an issue in itself if WordPress and Wordfence were already installed there by default rather than moved. Like you say, file paths, database/file permissions, connectivity to our server and IP detection all seem good.
As you are on FPM/FastCGI, use FTP or a file manager to access your .htaccess file in the root directory and make sure this code is input:
# 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
Then also, in the same directory, add/edit your .user.ini file with this code:
; Wordfence WAF
auto_prepend_file = '/your/path/to/wordfence-waf.php'
; END Wordfence WAF
Make sure to change the path above with the one that you currently see in your .htaccess and ensure auto_prepend_file
is removed from .htaccess once you’ve copied it.
We have seen in rare cases hosts denying configuration of .user.ini/.htaccess to its customers, therefore requiring Wordfence to permanently run in Basic Protection. However, please try the above first. If the firewall isn’t optimized after making those changes, consider consulting your host’s support as to whether you have the ability to modify those settings/files and let us know.
Thanks,
Peter.