Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected HTTP error: SSL certificate problem: unable to get local issuer certificate #143

Closed
ostrolucky opened this issue May 11, 2018 · 8 comments

Comments

@ostrolucky
Copy link

C:\tools
λ php phive install composer-require-checker
Phive 0.10.0 - Copyright (C) 2015-2018 by Arne Blankerts, Sebastian Heuer and Contributors
Fetching respository list
[ERROR]    Unexpected HTTP error: SSL certificate problem: unable to get local issuer certificate (while requesting https://phar.io/data/repositories.xml) (Code: 60)
@theseer
Copy link
Member

theseer commented May 12, 2018

This is not a bug in phive.

The curl library in your windows and/or php environment is lagging a way to verify TLS certificates.
One potential way to fix this is by downloading the cacert.pem provided by CURL and setting its path in the php.ini by having it contain curl.cainfo="/path/to/downloaded/cacert.pem".

@theseer theseer closed this as completed May 12, 2018
@theseer theseer reopened this May 12, 2018
@theseer
Copy link
Member

theseer commented May 12, 2018

We might actually handle this situation more gracefully.

@theseer
Copy link
Member

theseer commented Oct 31, 2018

Added additional information for this type of situation to the exception with commit 74a2f55

@theseer theseer closed this as completed Oct 31, 2018
@jrfnl
Copy link
Contributor

jrfnl commented Aug 4, 2021

Hmm... I just ran into the exact same thing (with Phive 0.15.0) and the additional information added in 74a2f55 was not displayed. Should I open a new issue for this ?

@theseer
Copy link
Member

theseer commented Aug 4, 2021

Are you sure you get the same error code?

@jrfnl
Copy link
Contributor

jrfnl commented Aug 4, 2021

@theseer Looks like it:

image

@theseer
Copy link
Member

theseer commented Aug 4, 2021

Interesting. That'd qualify as a bug then indeed. Not sure yet why (let alone how) that could happen but that's of course to be determined.

So yes, please open a dedicated issue.

@jrfnl
Copy link
Contributor

jrfnl commented Aug 4, 2021

@theseer Done: #327

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants