0

I am upgrading an old Gitlab (manually installed) from 5.0 to 8.0 through 5.1, 6.0, 6.1, 7.14 and 8.0. Every steps were ok except the access through HTTPS with git command lines, in all versions.

A git clone over SSH iw working. A git clone over HTTPS returns fatal: Authentication failed for.

If I modify a project by placing it as public, git clone over HTTPS works.

Web interface is working fine and I can log in to without issue.

What I am missing in the configuration ?

The SSL certificate used is a Let's Encrypt certificate.

Improve this question
10
  • You have got users and passwords on your system I assume?
    – NickW
    Aug 1, 2016 at 14:33
  • sure I have ...
    – lazzio
    Aug 4, 2016 at 8:59
  • So, you're doing a command line pull, what option are you using?
    – NickW
    Aug 4, 2016 at 9:38
  • I am doing a git clone https://git.domain.com/toto.git, the system asks me a login and a password. After that, I get le message fatal: Authentication failed for .... but my access are the good ones.
    – lazzio
    Aug 5, 2016 at 10:44
  • I found that in my original installation of gitlab (4.2), I configured it to use LDAP authentication. Now, my LDAP is gone, I disable LDAP authentication too. HTTPS is working. On my test copy of Gitlab (upgraded in 5.0 etc), HTTPS authentication is working anymore. I found that my Gitlab account is still stagged as LDAP account, even if LDAP is disabled. If I create manually a new account, HTTPS authentication is working. So, is there a solution to "migrate" all previously created from LDAP accounts to a normal manually created gitlab account ?
    – lazzio
    Aug 5, 2016 at 10:49

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .