Passing public key to Wordfence Central fails

Hello @swedman

Could you please send over diagnostics from the Wordfence > Tools > Diagnostics > Send Report by Email to [email protected] — please enter your forum username in that second field as well.

If you would, please let me know here when those are sent over and I’ll take a look for you.

Thanks,
Scott

Has been sent.

Thanks Scott

Thanks for that! I took a look. Right now it looks like you have error logging turned off, but you can usually turn it on without actually showing errors on your site by making a change to the wp-config.php file:

There you can change
define('WP_DEBUG', false);
to define('WP_DEBUG',true);

and add
define('WP_DEBUG_DISPLAY',false); and
define('WP_DEBUG_LOG',true);

The site will then add errors to wp-content/debug.log

You can try connecting Central a few more times and then send that log, if you could.

Thanks again,
Scott

Done and resent.

Thank you Scott.

I see for this specific function Central is trying to complete there is a Maximum execution time of 30 seconds exceeded occurring in your logs. I noticed you are on an older version of PHP. It’s possible updating to one of the PHP 7.x versions would help in this case.

Scott

Will try, however the customer account level on GoDaddy currently only allows 5.6.

Thanks Scott.

Finally got the site updated to PHP 7.2 but now seeing this error:

HTTP 401 received from Wordfence Central: {“errors”:[{“status”:401,”title”:”The server encountered an error processing your request.”,”detail”:”Token has expired”}]}

Thanks Scott.

Thanks for the update. Could you please remove the site from the Connection Errors area of Central (and double check in your WordPress site’s main Wordfence dashboard page that it is disconnected) and then try re-adding the site again in Central. Are you then getting the same error?

Thanks for your patience!

Removed and confirmed then re-added. Same error.

Thanks Scott.

Thanks for checking for me. Here’s another thing to try, and keep in mind, we are working through various connectivity errors as Central is still quite new, so with each update we will be doing our best to make this process more simple for our users.

If you could please, go into your Wordfence dashboard on your site and open up the browser console. In the console, paste the following WFAD.ajax('wordfence_wfcentral_disconnect', {}, function() {}); and then hit enter. That should completely disconnect the site from Central.

Head back over to Central and make sure you do not see it in the main page or the Connection Errors tab. Then again, if you could, please try adding that site.

Hopefully we have a different outcome, but let me know what you see there.

Scott

You’ve solved it. All working now.

Thank you very much Scott.

That is a nice little trick our QA team has shared with us to forcefully disconnect the site if there may be a lingering issue where the site is not fully removed, and having trouble connecting.

I’m glad that worked for you. Feel free to reach out to us if you have any other issues.

Scott

I am not quite understanding the “If you could please, go into your Wordfence dashboard on your site and open up the browser console” instruction. I can open up the WordFence dashboard on my site, but I do not see a “browser console option or feature in the dashboard.

If you are using CHROME. While you are in your dashboard–click “VIEW”>
Developer>Javascript Console——-your Browser Console on the right will appear.

Thank you. Found it in Safari’s Developer menu.

still can’t get it to connect, but I fear it’s because the site is on GoDaddy which doesn’t allow PHP past 5.4 without an expensive upgrade my client won’t want to do.