php.ini problem

Hi,

Did the installation work correctly for you on the primary site that you mentioned, but only not on the subdirectory site?

Also, when you attempt the installation on the second site, does go through the steps as if it is working, but just does not take effect? Or does it not let you continue past the first page?

-Matt R

no, it didn’t work on both. i try to disable the plugin on the first to give a try at the second wp but didn’t work, the same when i disable it at the second wp.

in none of them it goes on, after i give ok for the second step and it asks to save htaccess, i did it and after that back to the first step without making a change.

Ok. Can you find any messages in the error logs for either site?

-Matt R

i didn’t find any error log, but it comes this info when i turn back to first step after saving htaccess:

The changes have not yet taken effect. If you are using LiteSpeed as your web server or CGI/FastCGI interface, you may need to wait a few minutes for the changes to take effect since the configuration files are sometimes cached. You also may need to select a different server configuration in order to complete this step, but wait for a few minutes before trying. You can try refreshing this page.

It sounds like the host may not support the method we are using to load the new firewall. Can you tell me what hosting company you are using?

You might be able to complete setup manually following the steps in this section:
SiteGround and other hosts without .user.ini support

We’re looking at automating this in a future version, for any hosts where we need to use alternate methods. If it works for you, let me know.

-Matt R

Also does not work on a Bluehost hosted sub site. Same sequence of events that FunkyCreep experienced.

I’m having no end of issues as well.

I’ve checked the .user.ini file and php.ini file, and the required code is apparently there, but the setup simply doesn’t work.

I’m using an Australia host, Netregistry, using Lightspeed. I don’t have cPanel, so I’m accessing the files directly using Dreamweaver.

Also, is there any security risk if the Wordfence Web Application Firewall is not enabled? Are other aspects of Wordfence suspended or affected?

my host is netsons.com

the solution for siteground do not work for my host (maybemy account is locked from this option), even if i try to create a php.ini for each site.

I had similar problems running apache2 with mod_php. Using a custom php.ini with the SetEnv PHPRC directive in .htaccess didn’t work.
The wordfence-waf.php file was created (after changing the permissions) so I just added:

php_value auto_prepend_file "/path_to_file/wordfence-waf.php"

in my .htaccess and the firewall is loaded.
Is this solution viable?

Where in the .htaccess did you add the code? I’m not that familiar with coding, so not sure of the best location.

Just add it to the end of the file. Just be careful to not put it in between any # …. # blocks because this is code added by a plugin or WordPress which can be changed or removed.
And make sure you run apache2 with mod_php before adding this!

OK, thanks. I’ll hold off doing anything for now and see what happens when the week of WAF ‘learning’ is over and whether everything works out. And it looks like other things are afoot as well, following the ‘positive’ responses to the latest upgrade. ??

Hi,

The support team of my hosting company confirms that they use Apache/suPHP but on shared hosting they do not support .user.ini, neither changes to php variables or custom php.ini.

So the guided setup is not completing successfully and the alternative solutions proposed in the official WAF wiki page are not working.

I tried the solution proposed by pierrer:
just add
php_value auto_prepend_file "/path_to_file/wordfence-waf.php"
at the end of .htaccess, and it works.

@ WFMattR: like pierrer I’m wondering if this is a good solution, it works but it seems to bee too easy/basic that make me think I’m missing something :). Can you confirm and or explain better?

Thanks!

I tried that and it didn’t work.

Are you sure you use mod_php? See here how to determine.