• Resolved Syxguns

    (@syxguns)


    Hello Wordfence, I was following the instructions here: https://www.wordfence.com/help/firewall/optimizing-the-firewall/ and received the following error message:
    The following errors were encountered while processing your request:
    OneHphpvar::saveini failed: Invalid value for variable auto_prepend_file ignored.

    I continued with the instructions and have turned off the following:
    display_errors = Off
    auto_globals_jit = Off

    I still have the same error located above. I know that SiteGround incorporated Nginx into their hosting environment and this may be the issue. Needless to say, I can’t get WordFence firewall to activate with the auto_prepend_file.

    The link I was using for the auto_prepend_file was:
    auto_prepend_file = ‘/home/XXXX/public_html/wordfence-waf.php’

    Do you have another way to accomplish this task without the auto_prepend_file? Is it possible for you to update the tutorial for the new SiteGround setup they are using?

    I hope you have a solution to this issue I’m facing. Many thanks, and I hope to hear back about this subject. Also, is the display_error and auto_globals_jit being off an issue, and do I need to turn them back on?

    Thank you,
    Syxguns

    This was a question I submitted to [email protected]. The response was that I should ask in the forums. Not sure if anyone else has faced this issue as of yet.

    • This topic was modified 6 years, 4 months ago by Syxguns.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Syxguns

    (@syxguns)

    It seems that I made the error in this case. The following link I placed was incorrect.

    auto_prepend_file = ‘/home/XXXX/public_html/wordfence-waf.php’

    Should have been:

    /home/XXXX/public_html/wordfence-waf.php

    That corrected my issue.
    I wish WordPress would allow me to edit the above post so you didn’t have to read it all.

    Syxguns

    Plugin Support wfphil

    (@wfphil)

    Hi @syxguns

    I was about to reply to say that we have seen this before and it is a misconfiguration by the user and you found your error.

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

The topic ‘SiteGround Instructions’ is closed to new replies.