Conflict with Yoast SEO Premium when using redirects (“SECURE_AUTH_COOKIE”)

  • Resolved djnels

    (@djnels)


    1 year ago

    I’m currently working on a site that is part of a WordPress (v6.4.3) multisite installation on a server running PHP v8.1.26 that has both Wordfence Security (v7.11.1) and Yoast SEO Premium (v22.0) plugins installed and activated.

    When the “Redirects” feature of Yoast SEO is used on this site to enable 301 and 307 redirects, a 500 error occurs as the result of a PHP fatal error:

    PHP Fatal error: Uncaught Error: Undefined constant "SECURE_AUTH_COOKIE"

    I’ve seen this same or very similar problem reported here in these support threads, but I haven’t seen a solution in any of them unfortunately despite the fact that they’ve all be marked as resolved:

    I reached out to Yoast support, and this was their response, which is why I’m reaching out to Wordfence Security support now:

    “We’d still expect Yoast to work with WordFence. However, as WordFence sometimes modifies parts of the server for security purposes, it takes some additional steps and configuration to make it work with Yoast.

    “We already have a feature request to alert users of possible issues when using security plugins like WordFence, and users can fix it by adjusting their security configuration. As of now, that is still pending with our development team.

    “In the meantime, we’d recommend you work directly with WordFence to resolve the issue, as there is the expectation that the WordFence plugin needs to be configured first to be able to work with Yoast.”

    Any help you are able to provide in this matter is greatly appreciated. If there’s something in the Wordfence configuration that needs to be adjusted, please let me know what that is. Thank you.

Viewing 1 replies (of 1 total)
  • Plugin Support wfmark

    (@wfmark)

    Hi @djnels, Thank you for reaching out.

    The SECURE_AUTH_COOKIE message is generally caused by a plugin or mu-plugin (Must Use plugin) loading WordPress core files out of order, before pluggable functions are loaded. That can trigger parts of Wordfence that should happen later in WordPress’s loading process, because they’re causing parts of WordPress itself to run before they should.

    ?The best way to find which plugin is doing that is disabling them temporarily. If it turns out to be a mu-plugin, it requires temporarily renaming them manually in the wp-content/mu-plugins directory, or turning them off in a plugin’s settings (if another plugin created them and is able to add/remove them.)

    If you don’t have a staging site, you could use a maintenance mode plugin so site visitors don’t see a broken site.

    Thanks,
    Mark.

Viewing 1 replies (of 1 total)
  • The topic ‘Conflict with Yoast SEO Premium when using redirects (“SECURE_AUTH_COOKIE”)’ is closed to new replies.