SUCCESS WITH FIREWALL 6.1.4

  • I’ve really slaved over this, but no way I’m going to run security software that isn’t chugging along at 100%. So once I’d familiarized myself with everything, I contacted Liquid Web hosting support and it looks like they got everything working after a couple of hours. I have three WordPress sites on one server, with only one default php.ini file. The tech support guy had to break that down. Here is his summary.

    Backup copy the cPanel PHP wrapper script and then I edited the wrapper to check first for a php.ini in the public_html, then if none is found check the user dir, then if none is found to
    check in the normal location of the global php.ini. Then I copied the cPanel PHP wrapper script to a more permanent location in case I recompile Apache at some point. Then I created
    local php.ini files for the three domains, using the directive needed for each in the corresponding local php.ini file, corrected perms, and restarted Apache.

    And so on. It took a few crashed websites and like I said, hours. I hope it’s worth it.

    MTN

    https://www.ads-software.com/plugins/wordfence/

Viewing 1 replies (of 1 total)
  • Thread Starter mountainguy2

    (@mountainguy2)

    So, I go to check my main website to see how Wordfence is doing. It’s deactivated!

    Has anyone had Wordfence deactivate on its own? Was pretty alarming.

    MTN

Viewing 1 replies (of 1 total)
  • The topic ‘SUCCESS WITH FIREWALL 6.1.4’ is closed to new replies.