we had a similiar problem because the frontend http-server (an nginx) used
proxy-buffereing (which is on by default, 1GB i think). so gitlab delivered
the data more quickly than the client could consume it (it was over the
internet). so the reverse proxy 'nginx' buffered the output of gitlab. an
Thanks you a lor Ulrich.
I didn't explain but the goal of this is to resolve a 502 error when
cloning big project from external connection :
*Cloning into 'my-project'...*
*error: RPC failed; result=22, HTTP code = 502*
*fatal: The remote end hung up unexpectedly*
We already raise the timeout
correct:
[url "http://frontend.com/";]
insteadOf = g...@frontend.com:
put this in your ~/.gitconfig
Am Mittwoch, 13. Mai 2015 07:10:56 UTC+2 schrieb Ulrich Schreiner:
>
> hi,
>
> you cannot connect to port 22 (ssh) via an apache server. the apache is a
> reverse proxy for web access (http/htt
hi,
you cannot connect to port 22 (ssh) via an apache server. the apache is a
reverse proxy for web access (http/https). if you want to access your
gitlab instance git "g...@frontend.com" you can put something like
[url "http://frontend.com";]
insteadOf = g...@frontend.com:
so your git-clien
Hi,
I did a lot of searches on internet but I didn't find a solution so I post
my question here.
In my company, there is Gitlab on server Ubuntu 12.04. It's reachable
throught an apache frontend (Apache 2.2.23).
The url of the frontend is : *http://frontend.com/*
A reverse proxy has been confi
