@prohtex opened this Issue on March 2nd 2017

The PHP package bundled with Apple's Server.app uses SecureTransport, not OpenSSL. This causes multiple errors on Mac OS X. Is there planned support for SecureTransport?

https://forum.piwik.org/t/curl-exec-ssl-invalid-ca-certificate-1-offset-0-in-bundle/22561

@mattab commented on March 21st 2017 Owner

Would be great to support this, and a Pull Request is welcome/wanted!

@mattab commented on March 21st 2017 Owner

Note that easiest way to solve this is to install openSSL on your PHP by following these instructions http://stackoverflow.com/questions/26461966/osx-10-10-curl-post-to-https-url-gives-sslread-error

@prohtex commented on April 5th 2017

While it's not difficult to do this if you're relying on your own LAMP stack (MacPorts, Homebrew, MAMP, that Swiss guy who used to offer a pre-compiled solution, roll your own etc.), for those of us using Apple's Server.app and bundled Apache, this is another story.

Maybe it would be a good idea to offer some user-facing message about SecureTransport? As of the current version, install works but there are a lot of odd errors that pop up during upgrade.

@mattab commented on May 25th 2017 Owner

Errors reported in the post https://forum.piwik.org/t/curl-exec-ssl-invalid-ca-certificate-1-offset-0-in-bundle/22561/5

  • Marketplace = curl_exec: SSL: invalid CA certificate #1 (offset 0) in bundle. Hostname requested was: plugins.piwik.org
  • Plugin install = curl_exec: SSL: invalid CA certificate #1 (offset 0) in bundle. Hostname requested was: plugins.piwik.org
  • main screen administration = curl_exec: SSL: invalid CA certificate #1 (offset 0) in bundle. Hostname requested was: plugins.piwik.org

Does the problem also occur when clicking "Check for updates" link in the box in the Admin area? (wondering if api.piwik.org still can be connected via securetransport and onlyp plugins.piwik.org would be affected)

@prohtex commented on May 25th 2017

I just upgraded successfully to 3.0.4. Like the upgrade to 3.0, 1, 2, 3, I got several SSL errors during the upgrade but despite saying "Upgrade failed" it worked fine. Here is what I see in my Admin panel:
screen shot 2017-05-25 at 8 53 52 am

@prohtex commented on June 23rd 2017

Any updates on this one? To answer your question @mattab, no, when I click "check for updates", I do not get an error.

Powered by GitHub Issue Mirror