• Resolved Tony221268

    (@tony221268)


    Basic details: running plugin 1.0.2 WP 5.1 using Siteground hosting

    I cloned this site from a staging site where everything appears to work perfrectly using Paired mode.

    I noticed that there are visual and code differences (logo showing classes of “amp-wp-unknown-size amp-wp-unknown-width”) in the amp version of the cloned live site when compared to the original here:
    https://webtest.greyridge.com/?amp

    Assuming some sort of config issue and to see if I could remove this, I changed from Paired to Classic and back again. When I did this I got the error message:

    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

    Trying this on the staging site gets:

    Paired mode activated! View an AMP version of your site. Please also review 36 issues which may need to be fixed (for one URL at least).

    The SSL certificates for both sites are Let’s Encrypt v3.

    Any idea what is going on?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Weston Ruter

    (@westonruter)

    The AMP plugin is attempting to do a loopback request using WP_HTTP to determine the AMP validity. This loopback request is failing due to a certificate problem it seems. This would also be why the images are showing up with wrong dimensions, as it is not able to fetch the image file to determine the dimensions.

    I’m not sure why there would be an SSL certificate problem, but this would be liable to break other things about WordPress as well, like WP Cron (which also uses a loopback request).

    Are you able to SSH into the server and run:

    wp eval 'print_r( wp_remote_get( "https://webtest.greyridge.com/?amp", array( "sslverify" => true ) ) );'

    Does it return without an error?

    Thread Starter Tony221268

    (@tony221268)

    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.

    Thread Starter Tony221268

    (@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.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘SSL Error’ is closed to new replies.