Getting a 503 error when trying access gitlab

I completely erased my gitlab instance and set everything up all over again. I am now getting a 503 error in firefox and i’m not sure why.

I am running this on CentOS 7.2, Using apache instead of nginx, remote postgres sql

Here is my config got gitlab.rb

sudo cat /etc/gitlab/gitlab.rb | grep -v '^$\|^\s*\#'
external_url 'http://gitlab1.borg.local'
 gitlab_rails['time_zone'] = 'CST'
 gitlab_rails['db_adapter'] = "postgresql"
 gitlab_rails['db_encoding'] = "unicode"
 gitlab_rails['db_database'] = "gitlabhq_production"
 gitlab_rails['db_username'] = "gitlab"
 gitlab_rails['db_password'] = "Infotech5!"
 gitlab_rails['db_host'] = ""
 gitlab_rails['db_port'] = "5432"
 postgresql['enable'] = false
 web_server['username'] = 'gitlab-www'
 web_server['group'] = 'gitlab-www'
 gitlab_ci['db_adapter'] = "postgresql"
 gitlab_ci['db_database'] = "gitlab_ci_production"
 gitlab_ci['db_username'] = "gitlab_ci"
 gitlab_ci['db_password'] = 
 gitlab_ci['db_host'] = ""
 gitlab_ci['db_port'] = 5432
 ci_unicorn['port'] = 8181
 ci_nginx['enable'] = false
sudo cat /etc/httpd/conf.d/gitlab.conf
  ServerName gitlab.borg.local
  ServerName gitlab1.borg.local
  ServerSignature Off
  HostnameLookups Off
  ProxyRequests Off
  ProxyPreserveHost On
  Options +Multiviews +FollowSymLinks
  DocumentRoot /opt/gitlab/embedded/service/gitlab-rails/public

  # Ensure that encoded slashes are not decoded but left in their encoded state.
  AllowEncodedSlashes NoDecode
  <Location />
    # New authorization commands for apache 2.4 and up
    Require all granted

    #Allow forwarding to gitlab-workhorse
    ProxyPass http://gitlab.borg.local:8081
    ProxyPassReverse http://gitlab.borg.local:8081

  # Apache equivalent of nginx try files
  #RewriteEngine on

  #Forward all requests to gitlab-workhorse
  #RewriteRule .* http://gitlab.borg.local:8081%{REQUEST_URI} [P,QSA,NE]
  <Proxy gitlab.borg.local>
        Require ip
  # needed for downloading attachments
  #DocumentRoot /home/git/gitlab/public

  #Set up apache error documents, if back end goes down (i.e. 503 error) then a maintenance/deploy page is thrown up.
 # ErrorDocument 404 /404.html
 # ErrorDocument 422 /422.html
 # ErrorDocument 500 /500.html
 # ErrorDocument 503 /deploy.html

  # It is assumed that the log directory is in /var/log/httpd.
  # For Debian distributions you might want to change this to
  # /var/log/apache2.
  LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b" common_forwarded
  ErrorLog /var/log/httpd/gitlab.borg.local_error.log
  CustomLog /var/log/httpd/gitlab.borg.local_forwarded.log common_forwarded
  CustomLog /var/log/httpd/gitlab.borg.local_access.log combined env=!dontlog
  CustomLog /var/log/httpd/gitlab.borg.local.log combined

Logs don’t say much.

1 Like