Tony221268

Turns out that the issue appears to be related to using cloudflare CDN to serve the site. I am guessing that non-wp parts of their version stopped me seeing resolution when I cloned what was a working wp site.

I disabled that at Siteground and the SSL immediately checked out fine.

Thank you for your responses.

Thank you for this reply.

Yes the staging site URL returns without an arror but

wp eval ‘print_r( wp_remote_get( “https://www.franchise.co.uk/?amp”, array( “sslverify” => true ) ) );’
WP_Error Object
(
[errors] => Array
(
[http_request_failed] => Array
(
[0] => cURL error 51: SSL: no alternative certificate subject name matches target host name ‘www.franchise.co.uk’
)

)

[error_data] => Array
(
)

)

A little Googling indicates that this error is something to do with old SSL version.

I think maybe I will regenerate the SSL certificate manually at some point and post back once I have done that.

Hi, Not sure if this is the same error but rather than open a new thread.

When I try to activate Paired Mode on live site hosted at Siteground

https://www.franchise360.co.uk/

I get

Paired mode activated! However, there was an error when checking the AMP validity for your site. cURL error 35: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

Running AMP 1.0.2 WP5.1

Local site works fine

solved it by removing those out of loop widgets thank you!

Probably get attacked for being strictly off topic here but it strikes me that as I understand it, the wp importer is generally too restrictive when it comes to images/ files.

Given that this is usually being done by people who are not entirely technophobic then would it be so daft to have a few options on the importer?

For example, how about an option to just update the domain part of a URL to a new one (implicitly “because I’ll ftp the actual images to the right place myself”).

In my case I want that as I have a local machine for dev and for various reasons our live server just won’t upload the images from there. I don’t care to solve those reasons why.

FWIW I use the “ventrilqstman” method (see above)

If you are determined to validate with the current validators, I did notice an easy work around; just use a text field with label “Email” and appropriate regex (an easy google). Unless Mike can see an issue I think that works.