Skip to content

Instantly share code, notes, and snippets.

What would you like to do?

unicorn config file

Edit file /home/gitlab/gitlab/config/unicorn.rb

Find line listen "#{app_dir}/tmp/sockets/gitlab.socket" and comment it. Uncomment line listen ""

required modules for apache

  • sudo a2enmod proxy
  • sudo a2enmod proxy_http
<VirtualHost *:80>
# Custom log file locations
ErrorLog /var/log/apache2/gitlab_error.log
CustomLog /var/log/apache2/gitlab_access.log combined
ProxyRequests Off
ProxyPreserveHost On
ProxyPass /
<Location />
ProxyPassReverse /
Order deny,allow
Allow from all

This comment has been minimized.

Copy link

commented Jun 4, 2013

@steve-todorov, has you changed something in gitlab.yml or config.yml to do work gitlab? Thanks in advance!


This comment has been minimized.

Copy link

commented Jul 9, 2013

Thanks for this gist, but it looks like 5-3-stable doesn't have a unicorn.rb. Should the configuration be changed elsewhere?


This comment has been minimized.

Copy link

commented Aug 19, 2013

@DawsonG - Check puma.rb. You should be able to comment out the socket and enable the TCP listener.


This comment has been minimized.

Copy link
Owner Author

commented Nov 20, 2013

@proverbface nothing more than getting gitlab to start and being able to pull/push from repositories.
@DawsonG I haven't updated to 5.3 yet. By the time I made this gist I believe my version was 4.0 (or something).

Anyway, the main idea here is that you have gitlab listening on a port and you're using apache as a proxy which is forwarding all of the requests coming from to (or whatever port gitlab is running on)

Sorry all for the late response but I haven't checked my account for quite some time. Hope you managed to solve your problems. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.