Wordfence v7.3.3 Breaking Websites

  • Resolved nhtahoe

    (@nhtahoe)


    5 years, 9 months ago

    Jun 11, 2019, 9:56 PM PST: I got the dreaded “Your Site is Experiencing a Technical Issue” email from my WordPress site. Fixed by deleting the Wordfence plugin directory.

    Looks like 7.3.3 released JUNE 11, 2019 is causing trouble for several other Wordfence users too.

    
Error Details
=============
An error of type E_ERROR was caused in line 6 of the file /home/forge/www.********.com/public/wp-content/plugins/wordfence/vendor/paragonie/sodium_compat/lib/constants.php. Error message: Uncaught Error: Class 'ParagonIE_Sodium_Compat' not found in /home/forge/www.********.com/public/wp-content/plugins/wordfence/vendor/paragonie/sodium_compat/lib/constants.php:6
Stack trace:
#0 /home/forge/www.********.com/public/wp-content/plugins/wordfence/vendor/paragonie/sodium_compat/lib/sodium_compat.php(823): require_once()
#1 /home/forge/www.********.com/public/wp-content/plugins/wordfence/vendor/paragonie/sodium_compat/autoload.php(45): require_once('/home/forge/www...')
#2 /home/forge/www.********.com/public/wp-content/plugins/wordfence/vendor/composer/autoload_real.php(66): require('/home/forge/www...')
#3 /home/forge/www.********.com/public/wp-content/plugins/wordfence/vendor/composer/autoload_real.php(56): composerRequire6d00a11c4faa7bdc4bb08ac266cdf951('3109cb1a231dcd0...', '/home/forge/www...')
#4 /home/forge/www.********.com/public/wp-content/plugins/wordfence/vendor/autoload.php(9): ComposerAutoloaderInit6d00a11c4faa7bdc4bb08ac266cdf951::getLoader()
#5 /home/forge/www.********.com/publi
Viewing 3 replies - 1 through 3 (of 3 total)

  • Same issue show up on it’s own.
    …/public/wp-content/plugins/wordfence/vendor/paragonie/sodium_compat/lib/constants.php
    wp

    Same thing for me too…:
    PHP Fatal error: Class ‘ParagonIE_Sodium_Compat’ not found in …/wwwroot/wp-content/plugins/wordfence/vendor/paragonie/sodium_compat/lib/constants.php on line 6

    Very strange because the “vendor/paragonie/” folder no more exists in the v7.3.3. How can I have an error from a file that does no longer exists?

    Other strange thing, I have 2 of my websites totally broken with the v7.3.3 and all others (15+) who seems to be working fine but with that same error appearing in the log file.

    Is there a load balancing problem somewhere?…

    Hey All,

    This sounds like a WordPress plugin update that didn’t go well. Can you please try reinstalling Wordfence and let me know if it helps?

    https://www.wordfence.com/help/advanced/remove-or-reset/

    Please note that if you use the Wordfence Assistant method the tables below will need to be manually removed. In the next Wordfence Assistant release, these tables will be added to it.

    wfls_settings
    wfls_2fa_secrets

    Please let me know how it goes.

    Thanks,

    Gerroald

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wordfence v7.3.3 Breaking Websites’ is closed to new replies.