Hi,
Did your site originally have a .user.ini file? (You would have been prompted to download it during the installation, if so.) If it did, can you replace that file?
In the .htaccess file, on many setups, there can also be some code related to the firewall — if you can upload the backup copy of .htaccess, that may help as well.
If the .htaccess and .user.ini were restored to the originals, there shouldn’t be anything else causing a redirect loop, but you could try disabling the plugin itself — do you know if the front end of the site was working after the WordPress 4.5 update, but before the Wordfence update?
-Matt R
I was only prompted to download a copy of the .htaccess file.
I’ve reinstated the original .htaccess (stripped out reference to wordfence stuff, now it only has the original wordpress code in there).
I removed the .user.ini file, as well as the wordfence-waf.php file from that root directory. I have also disabled the wordfence plugin.
The site was working perfectly after WordPress 4.5 update, prior to wordfence update. in fact, it was working after wordfence update too — it was only after attempting to setup the firewall that it stopped working…
It still refuses to load.
Adding /index.php to the end of the tld makes it load; other pages will load too (from navigation / direct url) however, images aren’t loading.
Thoughts?
Would WF have touched php.ini at all?
Hi,
Wordfence doesn’t automatically change php.ini. If other pages won’t load, it sounds like WordPress’s permalinks are not working. If the admin pages are working fine, just go to the Settings > Permalinks menu, note the current option (just in case you have further trouble), and save the settings. I don’t think you even have to change them, but Wordfence should update any missing settings internally. I haven’t seen this happen from installing or removing the firewall, so I’m not sure what would cause it.
-Matt R
Interesting… so what does this line in ‘wordfence-waf.php’ actually mean:
// Before removing this file, please verify the PHP ini setting
auto_prepend_filedoes not point to this.
?
However, you were right… it is something to do with the permalinks; setting it back to ‘plain’ (where it uses id’s) seems to be working. Unfortunately, switching back to a custom permalink structure renders the site inaccessible again.
Any thoughts on that one? 🙂 😛