As suggested by Marko @capote, I investigated NinjaFirewall to replace Wordfence in WordPress.
All was working fine with WordPress and NinjaFirewall in the default directory (/var/lib/html).
When I installed NinjaFirewall in WordPress in a Vhost, it didn’t want to switch to Full WAF.
After exchanging with Marko, he found that in the file
/etc/httpd/conf.d/virtualhosts.conf, I have to delete the “/” at the end of the line
SetHandler (in 4 lines for each vhost), then restart httpd.
After the suppression of the “/” (in 4 lines for each vhost), all was working fine and NinjaFirewall was able to swtich to Full WAF in all Vhost directories.
After more investigations, I found that the reason it was working in the default directory and not in the Vhost one, was that in the file
/etc/httpd/conf.d/ www.conf , there is no “/” at the end of the line
Why there is an ending “/” in
/etc/httpd/conf.d/virtualhosts.conf and not in
Why the difference between GUI 980 and GUI 9090:
I think the bug is in the setting of the PHP version on both GUIs.
Thank a lot to Marko,
P.S. I prefer to use GUI 980 for the Vhost creation as it will use the name given to the vhost to create the vhost directory as GUI 9090 is using an hex number; is that the reason for the bug?
A name is easier to see than an hex number when you have multiple Vhosts.