From 1add25fcb5b5b7117b2afadf65396a659f1830b6 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Thu, 26 Sep 2024 13:14:04 +0200 Subject: [PATCH] Add SSL certificate problem hint in troubleshooting page --- doc/articles/troubleshooting.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index eda335453..ff0393002 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -247,6 +247,18 @@ please report this [issue](https://github.com/composer/composer/issues). 3. Check if it contains any path to a non-existent file, if it's the case, remove them. +## SSL certificate problem: unable to get local issuer certificate + +1. Check that your root certificate store / CA bundle is up to date. Run `composer diagnose -vvv` + and look for `Checked CA file ...` or `Checked directory ...` lines in the first lines of output. + This will show you where Composer is looking for a CA bundle. You can get a + [new cacert.pem from cURL](https://curl.se/docs/caextract.html) and store it there. +2. If this did not help despite Composer finding a valid CA bundle, try disabling your antivirus + software to see if that helps. We have seen issues where Avast on Windows for example would + prevent Composer from functioning correctly. If this helps you should report it to your + antivirus vendor so they can hopefully improve things. + + ## API rate limit and OAuth tokens Because of GitHub's rate limits on their API it can happen that Composer prompts