Plugin Support
WFAdam
(@wfadam)
Hello @studiokoen and thanks for reaching out to us!
If you could, 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.
I will be able to see exactly what we need to do to finish your firewall setup.
Thanks!
Hello Adam,
I have just send the diagnostics rapport from the WF plugin.
Hope tot hear from you,
best regards, Koen
Plugin Support
WFAdam
(@wfadam)
Thanks for sending that @studiokoen
Looks like your Server API is CGI/FastCGI. If you could use FTP or a file manager to access your htaccess file in the root directory and make sure this code is inputted:
# 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, edit your user.ini file with this code:
; Wordfence WAF
auto_prepend_file = '/var/www/vhosts/robstoop.nl/httpdocs/wordfence-waf.php'
; END Wordfence WAF
Once you have this code in place, your firewall should be optimized. If you visit your Wordfence > Firewall page, you should see 84% (which is the max a free customer can reach).
Let me know if you have any questions!
Thanks!
Thanks a lot. I will try that.
But the thing remains: I do not see a use.ini file in the main directory.
I will send a screenshot by seperate mail.
thanks, Koen
Plugin Support
WFAdam
(@wfadam)
Make sure you don’t have any files hidden. If the user.ini doesn’t exist in your root directory, you can create one and add the code above.
I wasn’t able to locate your screenshot in our inbox. If you can resend it with your forum username as the subject, I will try to find it again.
Thanks!
OK, I pasted your code into the htaccess file, above the existing code. I copied a user.ini file, and changed the code to this site. Uploaded all by FTP.
All is well now. Still do not know what created this problem though, but for now: everything OK.
Thanks a lot for your help!