• Resolved dccorp

    (@dccorp)


    Hi,

    I have several sites installed on a LAMP Ubuntu server managed by Virtualmin/Webmin (on DigitalOcean).
    Wordfence is working ok until now, but each time I’m adding a new site and a new wordfence install, firewall does not activate, but only after restarting Webmin service.
    So, first step is activating firewall (download htaccess etc.) but the message received is that the firewall is not activated yet. Waiting several hours the situation is the same. Proceed to restart Webmin cpanel, and voila, wordfence firewall is now activated.
    Do you have any explanation?

    Thank you,

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfphil

    (@wfphil)

    Hi @dccorp

    This appears to be something you will need to ask DigitalOcean support to investigate and resolve.

    So that I can see how the firewall is being optimized based on the PHP handler being used I would like to have a look at your Wordfence diagnostics report for one website only.

    Please go to the top of the “Diagnostics” tab on the Wordfence “Tools” page. There will be a “SEND REPORT BY EMAIL” button to send the diagnostics report. Enter wftest [at] wordfence [dot] com as the email and @dccorp as the forum username please.

    Once you have emailed me the diagnostics report can you reply here to let me know that it has been sent. This is important in the unlikely event that your installation of WordPress is having an issue with sending mail.

    Thread Starter dccorp

    (@dccorp)

    Hi, thanks for reply.

    I’ve sent the report as instructed. The report is from a test site/domain: farabatranete.ro, hosted under webmin/virtualmin cpanel.
    This is a test domain/site for the moment so if there is any other test needed, most probably I’m able to proceed with it.

    Thank you,

    Hi dccorp,

    In standard PHP-FPM configurations, a typical firewall optimization makes a change to the PHP configuration by adding an auto_prepend_file directive to .user.ini. The .user.ini file by default has a cache TTL of 5 minutes, after which the TTL would expire and the new configuration would be used. If this directive is instead added to php.ini or another higher-level configuration file for the site it may be necessary for the php-fpm service to be manually restarted. Depending on how virtualmin/webmin handles this it is possible that manually restarting the php-fpm service is the only option on your configuration. Most of the documentation I’ve found for virtualmin/webmin appears to indicate that restarting the php-fpm service is necessary when making any change to the PHP configuration.

    Thanks,
    Ram

    Plugin Support wfphil

    (@wfphil)

    Hi

    I see that the firewall is successfully optimized on the website for the diagnostics report that you sent.

    If the auto_prepend_file PHP directive is not being set on new websites via the .user.ini file unless you restart the Virtualmin service then this is something you will need to ask Webmin support about.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Webmin/Virtualmin firewall activation’ is closed to new replies.