Support » Plugin: W3 Total Cache » No minify assets with self signed SSL

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @furioussnail

    Thank you for your inquiry and I am happy to assist you with this.
    The issue is not related to W3TC minify but with your self-signed cert. You can try the following:
    1.Download “cacert.pem” from here: http://curl.haxx.se/docs/caextract.html.
    2.Save the cacert.pem file anywhere on your system.
    3.Open your php.ini file. If your php.ini file doesn’t have the curl.cainfo line, just add it to the end of the file, then add the file path where you saved your cacert.pem file:
    Change:
    ; curl.cainfo =
    To:
    curl.cainfo = “C:\PHP\Extras\SSL\cacert.pem”;
    Restart your server.`
    Thanks!

    Thread Starter Mos Craciun

    (@furioussnail)

    That doesn’t solve the issue with self signed certificates. Adding:
    ‘sslverify’ => false
    to w3-total-cache/Util_Http.php after line 36 does help with the test.
    However, since it is hard to follow the code logic through debugging I don’t know yet why W3 Total Cache fails to generate the assets.

    Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @furioussnail

    Adding: ‘sslverify’ => false does not solve the issue but covering the real issue and that’s the self-signed cert.
    So as I mentioned before, it’s not related to W3 Total Cache as cURL error 60: SSL certificate problem means that the problem is with the cert.
    Thanks!

    Thread Starter Mos Craciun

    (@furioussnail)

    The test fails because it can’t access a local website served through a self signed certificate. How that isn’t a W3 Total Cache issue? And how using a self signed certificate on a local site used for development is the real issue? The solution you provided above has nothing to do with self signed certificates. The Certificate Authority list found on the link above only provides an up to date CA list.

    • This reply was modified 3 months, 4 weeks ago by Mos Craciun.
    Plugin Support Marko Vasiljevic

    (@vmarko)

    Hello @furioussnail

    Thank you for the info.
    It sounds like a virtual host and/or DNS/hosts file issue. So this is an environmental issue.
    So to assist you with this and find the issue in your we need much more information like environment hosting environment: site URL, virtual host config, document root path, ABSPATH, etc.
    The best way to solve this is to offer you our premium support to investigate the compatibility issue.
    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.