Curl error 35 and SSL certificate not recognized

  • Resolved sos137

    (@sos137)


    2 years, 9 months ago

    Hello community,
    I have same problems with all my websites on OVH hosting with SSL certificate (behind loadbalancer).

    >>> All CRON tasks does not function. I get the message :
    cURL error 35: error:1408F10B:SSL routines:ssl3_get_record:wrong version number (http_request_failed)

    >>> Really Simple SSL plugin does not recognize the SSL certificate. I get those messages (french:):
    – La détection automatique des certificats n’est pas possible sur votre serveur.
    – Le correcteur de contenu mixte n’a pas pu être détecté en raison d’une erreur cURL : cURL error 35: error:1408F10B:SSL routines:ssl3_get_record:wrong version number.

    >>> Let me know if you can help to fix it and if you need more infos to investigate (url of website only in private) ?
    Thanks for any help

    >>> Versions
    WP: 6.0
    Really Simple SSL: 5.3.2
    PHP: 8.1

    >>> Htaccess
    # BEGIN Really Simple SSL Redirect 5.3.1
    <IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteCond %{HTTP:X-Forwarded-Proto} !https
    RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
    </IfModule>
    # END Really Simple SSL Redirect

    # BEGIN Security Headers
    <IfModule mod_headers.c>
    Header always set Strict-Transport-Security: “max-age=31536000” env=HTTPS
    Header always set Content-Security-Policy “upgrade-insecure-requests”
    Header always set X-Content-Type-Options “nosniff”
    Header always set X-XSS-Protection “1; mode=block”
    Header always set Referrer-Policy: “no-referrer-when-downgrade”
    Header always set X-Frame-Options: “SAMEORIGIN”
    Header always set Permissions-Policy: “”
    </IfModule>
    # END Security Headers

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ – [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>
    # END WordPress

    p.s. Impossible to use the support form on your website (https://really-simple-ssl.com/letsencrypt-support/) because captcha is inactive.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    Hi @sos137,

    If found this topic on your specific error message:
    https://stackoverflow.com/questions/50840101/curl-35-error1408f10bssl-routinesssl3-get-recordwrong-version-number

    But I’m not sure if that is the issue in your case as well. Did you check your SSL certificate on https://ssllabs.com? As CURL is not working, Really Simple SSL might not be able to correctly verify your certificate.

    As for the support form: because reCaptcha tracks users, we have to ask consent for marketing level cookies to use reCaptcha. This is not clear in the support form, so I’ve updated it with a short message behind the captcha, which should explain that accepting consent is necessary to submit the form. Thanks for reporting!

    If you can send your domain to support(at)really-simple-ssl.com, we can take a look at your certificate. But if it’s the issue as described on the forum thread I posted above, the issue is probably in the proxy configuration.

    Thread Starter sos137

    (@sos137)

    Thank you @rogierlankhorst for your answer.
    I did send you some URLs on your support adress.
    Certificate is recognized on ssllabs.
    All my 30+ websites hosted on different OVH servers have same problems.

    Plugin Support jarnovos

    (@jarnovos)

    Hi @sos137 and community,

    This has been followed up via e-mail. As described in this article (under cURL error 35) and seeing as this only occurs on OVH hosted environments, the issue is expected to be related to a misconfiguration on the server which can be addressed by the hosting provider.

    I will therefore mark the thread as resolved for now.

    Kind regards,
    Jarno

    I’m following on this thread since I’m having the same issue.
    Did you guys @jarnovos and @sos137 got a way to fix this?
    OVH has been less then helpfull…

    Thanks in advanced

    Plugin Support jarnovos

    (@jarnovos)

    Hi @claudiof,

    As the cURL error 35 is related to the server configuration, and seems to occur solely on OVH hosted environments, I had referred @sos137 to the OVH team to request a fix for this issue.

    We have not received confirmation from their side about a solution yet.

    Kind regards,
    Jarno

    Thanks @jarnovos OVH is less then helpfull.
    Awfull OVH support. Anyhow, thanks for replying.

    Thread Starter sos137

    (@sos137)

    Hi @claudiof @jarnovos
    I finally received a fix from OVH. The problem is due to their old CDN configuration.

    The fix is to switch to their new CDN paid offers or to desactivate the CDN on each domains (Hosting > Multisite > click on “…” > Modify > Uncheck “Enable CDN”, click on ‘Next’ then on ‘Validate’).

    That fixed the CURL and CRON problems.
    But i still get the error message that the automatic certificate detection is not possible on the server !

    Thanks @sos137 for the update.
    I’ll give it a go. But you did managed something I didn’t… Getting OVH to actually look into it…

    This was also impacting my cron tasks, but as a temporary fix, I’ve used OVH’s cron setup to trigger it.

    Thanks

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Curl error 35 and SSL certificate not recognized’ is closed to new replies.