• Resolved mpally

    (@mpally)


    Hi,
    After the update there is the new welcome popup.
    When I hit OK, then there is the message-banner on top of the page showing “invalid.
    The welcome popup shows again after reloading the page.
    In the php error log, there is a fatal error:
    wp-content/plugins/defender-security/src/component/notfound-lockout.php on line 267PHP message: PHP Fatal error: Uncaught Error: Cannot use string offset as an array in /www/alpenhirt_734/public/wp-content/plugins/defender-security/src/component/notfound-lockout.php:267

    Could you please help?
    Thanks a lot and kind regards

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter mpally

    (@mpally)

    Hi,
    It looks like this only happens at Nginx Hosting.
    My hosting for this is Kinsta.
    Regards
    Martin

    • This reply was modified 3 years, 3 months ago by mpally.
    Thread Starter mpally

    (@mpally)

    Strange, that the error occurs at live side, but not at staging side.

    Thread Starter mpally

    (@mpally)

    That is the full error message:
    2020/12/31 08:46:57 [error] 95296#95296: *370207 FastCGI sent in stderr: “PHP message: PHP Warning: Illegal string offset ‘nf’ in /www/grischunshop_283/public/wp-content/plugins/defender-security/src/component/notfound-lockout.php on line 264PHP message: PHP Warning: Illegal string offset ‘nf’ in /www/grischunshop_283/public/wp-content/plugins/defender-security/src/component/notfound-lockout.php on line 267PHP message: PHP Fatal error: Uncaught Error: Cannot use string offset as an array in /www/grischunshop_283/public/wp-content/plugins/defender-security/src/component/notfound-lockout.php:267
    Stack trace:
    #0 /www/grischunshop_283/public/wp-content/plugins/defender-security/src/component/notfound-lockout.php(146): WP_Defender\Component\Notfound_Lockout->record_fail_attempt(‘89.248.152.6’, Object(WP_Defender\Model\Lockout_Ip))
    #1 /www/grischunshop_283/public/wp-includes/class-wp-hook.php(287): WP_Defender\Component\Notfound_Lockout->process_404_detect(”)
    #2 /www/grischunshop_283/public/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
    #3 /www/grischunshop_283/public/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #4 /www/grischunshop_283/public/wp-includes/template-loader.php(13): do_action(‘template_redire…’)
    #5 /www/grischunshop_283/public/wp-blog-header.php(19): require_once(‘/www/grischunsh…’)
    #6 /www/grischunshop_283/public/index.php(17): require(‘/www/grischun” while reading response header from upstream, client: 89.248.152.6, server: http://www.grischun.shop, request: “GET /.well-known/assetlinks.json HTTP/1.0”, upstream: “fastcgi://unix:/var/run/php7.3-fpm-grischunshop.sock:”, host: “www.grischun.shop”

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @mpally,

    We haven’t faced such an error before so I’m afraid its tough to say what exactly would cause this at the moment. Since it works fine in your staging, could we know whats the PHP Version you are currently running in the website? Could we know do you notice any difference if you reinstall the plugin?

    I’m also bringing this into our team’s attention to double-check what might be causing for such an error to occur.

    Will keep you updated once we get further feedback asap. Sorry for any inconvenience due to this. Have a nice day ahead.

    Regards,
    Nithin

    Thread Starter mpally

    (@mpally)

    Hi,
    We tried everything at the hosting side.
    PHP is 7.3
    Completely deleting the plugin is not possible, because the settings cannot be changed.
    If trying to save, then the error appears.
    I tried with databasecleaner to remove also all the database entries, but did not work.
    When reinstalling, the situation is the same.
    Regards
    Martin

    Hi Martin,

    Can you please try to enable Opcache save comments by contacting Kinsta live chat? This may solve your issue.

    Thread Starter mpally

    (@mpally)

    Hi Roy,
    It works now!
    Thanks a lot!
    Kind regards
    Martin

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Fatal Error after updating to v2.4.5’ is closed to new replies.