Fatal WORDFENCE error preventing deactivation

  • Resolved europeanwilderness

    (@europeanwilderness)


    4 years, 3 months ago

    Hi,
    we have difficulties logging in and we cannot deactivate Wordfence anymore.. creating a major headache and possible loss of the site..

    here the error:

    Fatal error: Uncaught SodiumException: Argument 2 must be CRYPTO_SIGN_SECRETKEYBYTES long. in /homepages/21/d552708976/htdocs/clickandbuilds/LIFEstockProtect/wp-content/plugins/wordfence/crypto/vendor/paragonie/sodium_compat/src/Compat.php:2282 Stack trace: #0 /homepages/21/d552708976/htdocs/clickandbuilds/LIFEstockProtect/wp-content/plugins/wordfence/lib/wfCentralAPI.php(284): ParagonIE_Sodium_Compat::crypto_sign_detached() #1 /homepages/21/d552708976/htdocs/clickandbuilds/LIFEstockProtect/wp-content/plugins/wordfence/lib/wfCentralAPI.php(233): wfCentralAuthenticatedAPIRequest->fetchToken() #2 /homepages/21/d552708976/htdocs/clickandbuilds/LIFEstockProtect/wp-content/plugins/wordfence/lib/wfCentralAPI.php(51): wfCentralAuthenticatedAPIRequest->getToken() #3 /homepages/21/d552708976/htdocs/clickandbuilds/LIFEstockProtect/wp-content/plugins/wordfence/lib/wfCentralAPI.php(539): wfCentralAPIRequest->execute() #4 /homepages/21/d552708976/htdocs/clickandbuilds/LIFEstockProtect/wp-includes/class-wp-hook.php(287): wfCentral::sen in /homepages/21/d552708976/htdocs/clickandbuilds/LIFEstockProtect/wp-content/plugins/wordfence/crypto/vendor/paragonie/sodium_compat/src/Compat.php on line 2282
    There has been a critical error on your website. Please check your site admin email inbox for instructions.

    Learn more about debugging in WordPress.

    The page I need help with: [log in to see the link]

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

    (@wfadam)

    Hello @europeanwilderness and thanks for reaching out to us!

    If you are locked out and not receiving unlock emails but can’t wait for lockout time to expire and need immediate site access, please use FTP/SFTP — or any file manager your web host provides via their administration panel. Look inside the /wp-content/plugins/ directory and rename the wordfence directory. Once you have logged in to your WordPress admin you can name the folder back again and change the setting that caused you to be locked out.

    In this case, this can happen during an automatic and is being performed while the site is receiving traffic.

    Let me know if this helps!

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Fatal WORDFENCE error preventing deactivation’ is closed to new replies.