Trance-Man

I have the same issue, “Readability: Not available” usually it tells me ‘OK etc.

Says “Not enough content: Please add some content to enable a good analysis.”
But I have “Word count: 2181”

Screenshot
Screenshot Here

• This reply was modified 2 years, 9 months ago by Trance-Man.

WFSupport, thanks, I use Westhost as the backend hosting company, I spoke with them, this was the fix and it has worked, it allowed me to get the “Your Wordfence API Key:”

And I can do a scan now of the site, thank you, conversation with Westhost below shows the fix.

One Q, will this change effect anything on my site in your opinion? Westhost said they have seen no issues making this code change but wondering in your opinion if you see a problem with this change I made to wp-includes/class-http.php file?

===== Start Westhost.Com Support Discussion====
BC: [10:59:17 AM] Installing Wordfence (Plugin) on my blog located at: https://www.WEB.com/blog/

When running Click to test connectivity to the Wordfence API servers I get Error saying wp_remote_post() test to noc1.wordfence.com failed! Response was: error:0D0890A1:asn1 encoding routines:ASN1_verify:unknown message digest algorithm

When talking to Wordfence support they tell me “This particular error means that either curl or openssl needs to be updated on your web server. This is something that your hosting provider likely will have to do.”

Any ideas how to make this workout so I can use this Plugin correctly on my account for WEB.com?

Jeremy G.: [11:01:21 AM] In this case the
problem is due to the version of CURL that is installed with PHP. This old version of CURL doesn’t support the SSL version that is installed on the WordPress servers when trying to run an update or download plugins. The simple fix for this is to just follow these instructions to have WordPress not use SSL.

../wp-includes/class-http.php
and in that file you will need to modify the
following line from

curl_setopt( $handle, CURLOPT_SSL_VERIFYPEER, $ssl_verify );

to

curl_setopt( $handle, CURLOPT_SSL_VERIFYPEER, false );

BC: [11:02:08 AM] Will that effect anything, that change?

Jeremy G.: [11:04:03 AM] It will allow the plugin to work. The change tells the plugin that is does not need to use an SSL verify in order to run. It is not a problem since you are making the change yourself and you know what the plugin is doing and who is from.

BC: [11:04:53 AM] OK, On WordPress page WORDPRESS/wp-includes/class-http.php

BC: [11:15:38 AM] Will this changing of code effect anything at all? You said no, but any ideas?

[11:16:30 AM] No more errors on Wordfense now, so this DID FIX this one issue. I now have a “Your Wordfence API Key:”

Jeremy G.: [11:16:41 AM] OK Good! I have had other clients also change this setting and have never seen any issues. One of the upper level support technicians is the one who figured out the work around.

BC: [11:19:45 AM] ok that’s all for now, thank you
===== End Westhost Support Discussion====