• I updated to Wordfence 6.1.2 today and followed the instructions to enable the new firewall component. It seemed to work fine but it overrode the php.ini with respect to large file sizes.

    It appears that during the setup the wrong path was put into the .htaccess so it was not picking up the php.ini that is created from my web hosting control panel. There is no way I see to change that in wordfence once it has been set. There should be a way to fix that in the WordFence settings. I had to download the .htaccess and manually fix the file path.

    https://wordpress.org/plugins/wordfence/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WFMattR

    (@wfmattr)

    Hi Michael,

    Thanks for the report. Can you post a copy of the .htaccess file for the site, and show which path was replaced? (You can remove sensitive information, if any. And let me know if multiple .htaccess files were involved in the issue.)

    If the .htaccess file is long, you can use a site like pastebin, and just post a link here (due to wordpress.org forum rules.)

    Can you also tell me what hosting company you are using?

    -Matt R

    Thread Starter Michael Aronoff

    (@masterk)

    I have a dedicated server I co-locate that runs the open source Web hosting platform BlueOnyx.

    It is Apache + SuPHP but the path for the suPHP config in the .htaccess was set wrong. WordFence

    <IfModule mod_suphp.c>
    	suPHP_ConfigPath '/home/.sites/85/site23/web'
    </IfModule>

    But it should be:

    <IfModule mod_suphp.c>
    	suPHP_ConfigPath '/home/.sites/85/site23'
    </IfModule>

    On BlueOnyx if you turn on suPHP (it is an option) then the php.ini for each virtual site is kept a level above the public web folder.

    It is easy to change but it took me a few min to trace it down.

    It might be nice if there was a way to change that in the WordFence admin pages rather than having to manually change it.

    Plugin Author WFMattR

    (@wfmattr)

    Hi,

    Thanks for the additional details. I’ve sent this on to the dev team (reference number FB1662) to possibly implement in a future version, to make the setup process work easily with this configuration as well.

    -Matt R

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Firewall and file upload issue’ is closed to new replies.