After further investigation, here is what I found.
Directed CloudFlare away from site; still no dice.
Checked and triple checked for conflicting plugins. Nope and Nope.
Checked and re-checked hardened server… all is good in server world…
But, the devil is in the details……. Anyway, it was NOT cloudFlare. (Do check that though OP if you do have them or similar solution.)
Had whitelisted WF IP in both installations… WHAT GIVES?
THEN I saw it. Site 1–the site which registered a-ok; was in LEARNING MODE, but, that is NOT the critical piece of info. ENHANCED PROTECTION WAS OFF…. I had not configured it yet….. (Optimize the WordFence Firewall, listed in the WF dashboard.)
Here’s the piece you need to know. WF writes to your user.ini and your .htaccess file. Now, this is a GOOD thing, and we want this. The thing is though, with that enabled, you can click buttons inside WF till you are blue in the face; and nope, nada, nothing to see here. As in .htaccess and WF is doing its job in turning away a PHP attack…
If this is even your issue OP–that is. Of course there could be something else entirely.
Anyway, off with its head–I turned off WF firewall optimization, tried again; that did exactly jack…. Zilch, Zip, Nada…
Turned OFF the firewall… NOT EVEN…
Now it’s time to compare the .htaccess files….. Did it REALLY erase the entries??
PS: …Can anyone tell I REALLY want WF central? ??
Anyway… This journey continues Manjana….
There IS the possibility that CloudFlare is taking its sweet time changing its scripts….
Meanwhile… WF gurus??? What are your next suggestions for what to do?
On a VPS and not afraid to get my hands dirty….