Skip to content

GitLab

Closed
Created by Administrator@rootOwner

Clone through HTTPS with auth token failing

Created by: valeriansaliou

Hello,

I noticed that my GitLab CI runners (2 runners on 2 separate Macs w/ OSX Mavericks) were unable to fetch data from repository for builds. I first thought of a GitLab CI Runner code bug, but digging more into the matter I noticed it could probably come from GitLab itself.

Here's a log of the error, when I attempt to clone manually w/ the same clone endpoint the GitLab CI Runner uses:

➜  builds git:(master) ✗ git clone https://gitlab-ci-token:[email protected]/jappix/jappix.git
Cloning into 'jappix'...
fatal: git fetch_pack: expected ACK/NAK, got '
0008NAK
0024Counting objects: 14881, done.
002eCompressing objects:  87% (3917/4554)

I am a bit confused as this did not take place prior to GitLab 6.4, plus this seems to be a TCP-level failure.

Issue environment

FYI, here's my server configuration (hosts both GitLab and GitLab CI):

  • Debian 7 32 bits
  • Lighttpd 1.4.31-4+deb7u2
  • 4096 bits SSL key
  • Direct proxy from Lighttpd [HTTPS] to Unicorn [HTTP] via TCPv6

Here's my client configuration:

  • OSX Mavericks 10.9.1
  • Git version 1.8.5.2
  • No proxy or anything between me and the server