WordFence Central connection failes

  • Resolved Kipperlenny

    (@kipperlenny)


    4 years, 1 month ago

    I try to add a site to wordfence central, but it shows: “The server encountered an error processing your request.”

    The Debug Log shows:

    [27-Oct-2020 19:36:23 UTC] PHP Fatal error:  Uncaught RangeException: Internal check failed. in /htdocs/wp-includes/sodium_compat/src/Core32/Curve25519.php:1552
Stack trace:
#0 /htdocs/wp-includes/sodium_compat/src/Core32/Ed25519.php(305): ParagonIE_Sodium_Core32_Curve25519::ge_frombytes_negate_vartime('\xABCA\t\x08\x9ED~\x86U\xE4\xC1\xBF\x89\xA4...')
#1 /htdocs/wp-includes/sodium_compat/src/Crypto32.php(1652): ParagonIE_Sodium_Core32_Ed25519::verify_detached('\x05\N\x85\x8E\xAB\x1A\xEF\xD6\x81z\xF9q4\x84...', 'f8ba6cef7240343...', '\xABCA\t\x08\x9ED~\x86U\xE4\xC1\xBF\x89\xA4...')
#2 /htdocs/wp-includes/sodium_compat/src/Compat.php(2877): ParagonIE_Sodium_Crypto32::sign_verify_detached('\x05

    N\x85\x8E\xAB\x1A\xEF\xD6\x81z\xF9q4\x84…’, ‘f8ba6cef7240343…’, ‘\xABCA\t\x08\x9ED~\x86U\xE4\xC1\xBF\x89\xA4…’)
    #3 /htdocs/wp-content/plugins/wordfence/lib/rest-api/wfRESTAuthenticationController.php(106): ParagonIE_Sodium_Compat::c in /htdocs/wp-includes/sodium_compat/src/Core32/Curve25519.php on line 1552
    [27-Oct-2020 19:36:31 UTC] PHP Fatal error: Uncaught RangeException: Internal check failed. in /htdocs/wp-includes/sodium_compat/src/Core32/Curve25519.php:1552
    Stack trace:
    #0 /htdocs/wp-includes/sodium_compat/src/Core32/Ed25519.php(305): ParagonIE_Sodium_Core32_Curve25519::ge_frombytes_negate_vartime(‘\xABCA\t\x08\x9ED~\x86U\xE4\xC1\xBF\x89\xA4…’)
    #1 /htdocs/wp-includes/sodium_compat/src/Crypto32.php(1652): ParagonIE_Sodium_Core32_Ed25519::verify_detached(‘\x05`N\x85\x8E\xAB\x1A\xEF\xD6\x81z\xF9q4\x84…’, ‘f8ba6cef7240343…’, ‘\xABCA\t\x08\x9ED~\x86U\xE4\xC1\xBF\x89\xA4…’)
    #2 /htdocs/wp-includes/sodium_compat/src/Compat.php(2877): ParagonIE_Sodium_Crypto32::sign_verify_detached(‘\x05`N\x85\x8E\xAB\x1A\xEF\xD6\x81z\xF9q4\x84…’, ‘f8ba6cef7240343…’, ‘\xABCA\t\x08\x9ED~\x86U\xE4\xC1\xBF\x89\xA4…’)
    #3 /htdocs/wp-content/plugins/wordfence/lib/rest-api/wfRESTAuthenticationController.php(106): ParagonIE_Sodium_Compat::c in /htdocs/wp-includes/sodium_compat/src/Core32/Curve25519.php on line 1552`
    `

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @kipperlenny, thanks for reaching out, providing your diagnostic and the above log entries. I have quoted your other post below so that we can continue working together here.

    I try to connect an existing site (WP and WF up to date) to WordFence central.
    But “Unable to communicate with Wordfence plugin. Please verify Wordfence is installed and activated on this site.”

    WordFence is activated, wp-admin is not renamed, deactivating Sucuri (no WAF), iThemes and WP Rocket does not help.

    I tried to connect it from wordpress site as well, same error.
    The URL is afterwards not showing in “Connection issues”.

    I have send you the diagnostic report (URL is csscons******.de)

    I will take a look through your details now and get back to you about how you can move forward to solve this.

    Thanks,

    Peter.

    Plugin Support wfpeter

    (@wfpeter)

    Hi again @kipperlenny,

    You have sent us the diagnostic for csscons******.de but could you also send us the diagnostic for the site that produced the debug log at the top of this topic?

    As we only had one debug log, one diagnostic and one URL I had assumed both of your tickets referenced the same issue. I apologise for any misunderstanding.

    Thanks,

    Peter.

    Thread Starter Kipperlenny

    (@kipperlenny)

    Ok just did (with my Username: Kipperlenny). I thought it’s not needed because of the error log ??

    Plugin Support wfpeter

    (@wfpeter)

    Hi @kipperlenny thanks for the additional diagnostics.

    We can see from the diagnostic that you’re on a 32 bit system which would be why PHP_INT_SIZE is 4 instead of 8 and displaying the error logs you’re seeing.

    The error itself could be a bug with the sodium_compat library. We are currently considering including a newer version in an upcoming plugin release. However, as I am unable to guarantee timescales on this, if you are able to, install the libsodium PHP extension on your server, which should work around this issue in the meantime.

    Please contact your host’s support channels if you cannot install the libsodium extension yourself, as they may be willing to place this on your server for you.

    Thanks,

    Peter.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @kipperlenny,

    Hopefully your host were able to also help you out with libsodium as well as the PHP_INT_SIZE. If you would like any further Wordfence help going forward, you can open up a new topic where we’ll always be glad to help out.

    Thanks again,

    Peter.

    goldatlas

    (@goldatlas)

    Hi, I like to report a strange behavior:

    A customer who accidentally writes the username in Hebrew is locked out in on the first try. I can not find a way to prevent it?
    Please look the picture: https://1drv.ms/u/s!AlJM7dNlHfVYoORM1cMk8a-hTUJQ0A?e=GpHHmV

    It is happens when he/she attempt to recover password account. locked account happens after first try. Although 10 attempts are set

    I think the user is “writing” the user name in Hebrew by mistake, I think this is an error, since a plugin still needs to allow 10 failed login attempts and no matter what language it is written in, you do not think?
    Thanks for help

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘WordFence Central connection failes’ is closed to new replies.