From bfe4af846d04f3b6f5554860e7a8843a3a84672c Mon Sep 17 00:00:00 2001 From: crazyscience Date: Mon, 6 May 2013 20:17:57 -0700 Subject: [PATCH] Fixed a nginx configuration For some reason, if the nginx configuration is bound to an IP, it breaks the install, causing all git clone/push/pull operations to die with a 'fatal: The remote end hung up unexpectedly' message. Changing this configuration seems to fix the problem. I reckon that this is just a temporary fix. I don't know the ins and outs of GitLab well enough to vouch for this change, but I do know that these instructions are broken, and that this update will fix them. --- doc/install/installation.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/install/installation.md b/doc/install/installation.md index 9734034bf..56c9cdc50 100644 --- a/doc/install/installation.md +++ b/doc/install/installation.md @@ -253,9 +253,10 @@ Download an example site config: Make sure to edit the config file to match your setup: - # Change **YOUR_SERVER_IP** and **YOUR_SERVER_FQDN** - # to the IP address and fully-qualified domain name - # of your host serving GitLab + # **YOUR_SERVER_FQDN** to the fully-qualified + # domain name of your host serving GitLab. Also, replace + # the 'listen' line with the following: + # listen 80 default_server; # e.g., listen 192.168.1.1:80; sudo vim /etc/nginx/sites-available/gitlab ## Restart -- 2.11.0