5

I have my own gitlab server, now secured with an letsencrypt SSL certificate.

Now, I want to publish some packages via packagist. But when I enter the git repository url in packagist, I got the following error message (urls changed):

Uncaught Exception: [RuntimeException] Failed to execute git clone --mirror 'https://url.de/gituser/repository.git' '/home/composer/.composer/cache/vcs/https---url.de-gituser-repository' Cloning into bare repository '/home/composer/.composer/cache/vcs/https---url.de-gituser-repository'... fatal: unable to access 'https://url.de/gituser/repository.git': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none

Each browser accepts the certificate. But not composer/packagist.

Any Ideas why?

  • Check the site with [SSLLabs](https://www.ssllabs.com/ssltest/analyze.html). My guess is missing intermediate certificate, i.e. "chain issues" in the report. Browsers often work around such misconfiguration. – Steffen Ullrich Apr 25 '16 at 14:57
  • Ok, Done. "Chain issues" is "incomplete". And on "Certification Paths Path #1: Trusted" under "2." I read "extra download". What means that? –  Apr 25 '16 at 15:36

1 Answers1

5

Ok, I just found my mistake. I have used cert.pem instead of fullchain.pem.

Explained here: https://stackoverflow.com/questions/34189199/how-do-i-use-let-s-encrypt-with-gitlab

Community
  • 1