CodeIgniter Forums

Full Version: Composer Openssl Error
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I tried to update Composer today on my Mac and got the following error:

composer selfupdate
[Composer\Downloader\TransportException]
The "https://getcomposer.org/versions" file could not be downloaded: SSL operation failed with code 1. OpenSSL Error messages:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Failed to enable crypto
failed to open stream: operation failed


Anyone know what I have to do?
@donpwinston,

Did you do a search to see if anyone else had the same issue as you and was able to resolve it?
I found some complex discussions about it but no solution. (I was messing around with Symfony 4 and I think the computer gods are telling me to stay away)
Just to be clear, you're trying to update composer itself and not a composer install project. Right?

If that's the case, manually download composer.phar are replace your existing version.
https://getcomposer.org is working fine on my browser. No SSL cert issues, etc.
I gave up and did that, but I get the same error when I try to do something like:

composer create-project symfony/website-skeleton sf_test (I was going to learn Doctrine and use it with CI4)

My Composer doesn't like https.
(12-24-2018, 12:29 PM)donpwinston Wrote: [ -> ]I gave up and did that, but I get the same error when I try to do something like:

composer create-project symfony/website-skeleton sf_test (I was going to learn Doctrine and use it with CI4)

My Composer doesn't like https.

I got composer working properly on my home Mac. Must be some sort of network/firewall problem with my Mac at work. Although  my brower doesn't have any problems.
Ooof, gave up on Symfony 4. Turns out Doctrine is a bundle, not a component. Therefore it only works with Symfony. It no longer supports Informix anyway. There's a security component that supposedly can be used with CI4 but it's opaque. Guess I'll stick with my own database and authorization code. Also, I'm convinced once again that CI is the best choice.