– – –

Scan Stage Failed?A scan stage has failed to start. This is often because the site either cannot make outbound requests or is blocked from connecting to itself. Wordfence will make up to 2 attempts to resume each failed scan stage. This scan may recover if one of these attempts is successful.?Click here for steps you can try.(opens in new tab)

– – –

I’ve had a few problems with the plugin “Failing to Start” scans on my other sites at SiteGround… but I’m generally able to get it working by adjusting a couple of parameters in the plugins options… namely this option to “Start all scans remotely”

The plugin is working correctly on all of the other sites I have on my account at the moment, it’s just this one site. Ironically it’s also the smallest site I have, just a holding page, and the same two plugins that are installed with every new site at SiteGround, (their Security and Performance plugins) which I’ve disabled, and are also running on every site I have at SG. I’ve tried all of the same changes I’ve used to get the scans started on my other sites, and I’ve gone through several of the other possibilities found on the WordFence trouble shooting page, but no luck…

It has something to do with this error, which has also been the case on several of my other sites. Although I’ve always managed to get it working eventually.

– – –

Connecting back to this site — wp_remote_post() test back to this server failed! Response was: cURL error 60: SSL: no alternative certificate subject name matches target host name ‘s3ecuador.com’

Connecting back to this site via IPv6 (not required; failure to connect may not be an issue on some sites) — wp_remote_post() test back to this server failed! Response was: cURL error 7:

– – –

Generally with a couple of easy changes …and, once you manage to get the first scan to start, the error disappears, and all future scans seem to work fine.

Anything else I can try to get this working? Thanks!

Thank you!

Browsers display insecure site warnings when CCL certs expire, and I did not want to play the tinkering game…

Since I use the PRO version, my SSL certificates will be auto-renewed, a week before they expire.

I cannot imagine a simpler way to secure a WordPress site to avoid scaring visitors away.

While I thought Vijay would respond slowly to my questions, that was not the case. Even though he is on Indian Standard time, it was a pleasure to interact with him from Canada.

WP Encryption Pro maintains a free Let’s Encrypt SSL certificate, once configured. That is exactly what a self-hosted WordPress site needs!

I was on a chat with small orange and the guy couldn’t help me though he said I should change the link to the blog which I had linked to using http – I fixed those links on every page of my site to be https and the blog page is showing secure which you can see if you click on the link. The guy on chat also gave me a link that analyzed my home page showing where there were problems. The problems were all tied to the images I was using for my links on my website (not my blog page) and javascript files in the head. I added in front of all the img src and other code for the js files. Two notes on all that – I build my site and I didn’t really know what I was doing, and for some reason the Links link image isn’t showing.

Anyway, I thought that at least that page would show green and secure but it doesn’t.

Main question: does anyone know how to get all my pages showing secure with https? Do I need to do a redirect? I created an .htaccess file in my root directory with php code from the knowledge base site for my host but that didn’t seem to do anything. That php was for I guess redirect of http to https. I’m at a loss how to fix this. I paid for an ssl cert but google doesn’t see it.

Thanks!
Jim
BTW, I have a bunch of youtube videos in my watchlist to hopefully get an answer. YHave to go walk my dog now – check back later.

Can you tell me which stylesheets need fixed so I can get the site off the sh*tlist?

Any help would be greatly appreciated.

Here’s the console info

perfectwoodgrain.com/:72 Mixed Content: The page at ‘https://perfectwoodgrain.com/’ was loaded over HTTPS, but requested an insecure stylesheet ‘https://perfectwoodgrain.com/blog/wp-content/plugins/wp-members/css/wp-members.css?ver=3.1.6.3’. This request has been blocked; the content must be served over HTTPS.

and

(index):1Mixed Content: The page at ‘https://perfectwoodgrain.com/’ was loaded over HTTPS, but requested an insecure stylesheet ‘https://perfectwoodgrain.com/blog/wp-content/plugins/wp-members/css/wp-members.css?ver=3.1.6.3’. This request has been blocked; the content must be served over HTTPS.
css Failed to load resource: the server responded with a status of 400 ()

The auto-renew for the certs failed recently. I’ve been advised that, in order for auto-renew to work properly, I need to use the same nameservers as the main site, that just pointing the A record to the main site’s server won’t work. This essentially means the mapped domains are made to be addon domains on the main site’s server, not just parked domains.

(1) Does anyone know if the above (ie about nameservers) is correct ….

(2) … and, therefore, I should addon (not just park) the mapped domains

(3) And how do I set it up as an addon domain so subsite.mainsite.com (a WP site) works.