• Resolved JF::IA

    (@jfacemyer)


    I’m getting these errors with everything updated:

    Notice: Undefined index: SERVER_NAME in /home/vianney/www/shvcamps.com/wp-content/plugins/wordfence/lib/wfUtils.php on line 641
    Notice: Undefined index: HTTP_HOST in /home/vianney/www/shvcamps.com/wp-content/plugins/wordfence/lib/wfCache.php on line 38
    Notice: Undefined index: SERVER_NAME in /home/vianney/www/shvcamps.com/wp-content/plugins/wordfence/lib/wfCache.php on line 38

    https://www.ads-software.com/plugins/wordfence/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hello jfacemyer,
    we have a fix for this in Wordfence 6.1.9 which is just right now being released. Please upgrade to the latest version and you should be fine!

    Let me know how it goes.

    Thread Starter JF::IA

    (@jfacemyer)

    Looks like the update removed the first SERVER_NAME error on line 641, but the other two errors from line 38 are still there.

    Thread Starter JF::IA

    (@jfacemyer)

    BTW, thank you for your attention on this! Much appreciated.

    Hi jfacemyer,
    I have filed a bug for this. Our internal reference number is FB2091. Just a few quick questions.

    1. Are you using Wordfence cache?
    2. When and where are you getting the error?

    Thanks in advance!

    Thread Starter JF::IA

    (@jfacemyer)

    I’m getting this error whenever I do anything on this particular site (no others) with wp-cli.

    I’m using the 2-3x wf-cache setting on this site. Interestingly, it doesn’t happen when I disable it.

    I’m using NGINX, is there any other info that I can share to help diagnose the issue?

    I think that’s all we need to know for now. Thanks jfacemyer!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘WP-CLI errors’ is closed to new replies.