In addition, you can check your php.ini if extension=php_openssl.* (extension e.g. zip ( ) and replace the path in your php.ini and then restart the server. You can try to extract the bundle from the XAMPP. "C:\xampp7.3\apache\bin\curl-ca-bundle.crt" for my XAMPP installation). using this guide:, depending on your OS).įurthermore, you can check the openssl.cafile option in php.ini that should point to an absolute path containing a more or less recent CA bundle (e.g. I would recommend updating CURL separately (e.g. Curl verifies the certificate using the CA cert bundle that comes with the curl installation." (vsince CURL 7.10).Īs your CURL version is quite old ( released on Oct 7, 2015), I would assume that one of the CA/root certificates it is using is too old. According to the CURL FAQ ( ) section 4.12 (where exactly this error message is mentioned), "it means that curl couldn't verify that the server's certificate was good. I believe this error message is caused by CURL. However still the same error, so I figure this has nothing todo with the original Let's Encrypt or now Cloudflare SSL Certificate. Update: I now moved to Cloudflare as DNS Manager and have the "Full (strict) setting so that the Cloudflare SSL is the one in use. I googled extensively and tried figuring this out but no chance.Īny idea what I have to set on the server to have this go away? I tried modifying the php.ini with the capath and cafile like some threads pointed out but no luck. OpenSSL Error messages:Įrror:14090086:SSL routines:ssl3_get_server_certificate:certificate Only problem I have is that for some reason on the woocommerce checkout page I suddenly get this error message: I generated a Let's Encrypt SSL certificate and the entire site works as expected. I migrated a Wordpress site with a woocommerce shop and payment gateway "Payunity" to a new EC2 machine with a bitnami wordpress stack.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |