Gitlab installation of various pits

Reference: HTTPS://BBS.GITLAB.CC/TOPIC/35/GITLAB-CE-8-7-%E6%BA%90%E7%A0%81%E5%AE%89%E8%A3%85%E6%89%8B%E5%86%8C-CENTOS6-REHL6/2

Architecture: Source installation, database with MySQL, website with nginx

Pit one. Nginx Error

2016/07/19 09:26:11 [crit] 3881#0: *10 connect ( )  to unix:/home/git/gitlab/tmp/sockets/gitlab-workhorse.socket failed  (13: permission  denied)  while connecting to upstream, client: 192.168.1.180, server:  www.gitlab810.com, request:  "get / http/1.1", upstream:  "Http://unix:/home /git/gitlab/tmp/sockets/gitlab-workhorse.socket:/", host: " www.gitlab810.com "2016/07/19  09:26:11 [error] 3881#0: *10 open ()   "/home/git/gitlab/public/502.html"  failed   (13: permission denied),  client: 192.168.1.180, server: www.gitlab810.com,  request:  "get / http/1.1", upstream:  "http://unix:/home/git/gitlab/tmp/sockets/ gitlab-workhorse.socket/", host: " www.gitlab810.com "

This is because my nginx uses a WWW user run, and the/home/git/gitlab/tmp/sockets/gitlab-workhorse.socket/user group is git,

Solution: Add git to the WWW user group and give the implementation permission

Usermod-a-G git wwwchmod g+rx/home/git/

Pit Two: Nginx configuration is not accurate

[[Email protected] git]# cat /usr/local/nginx/conf/vhosts.d/gitlab.conf |grep -v   ' # ' upstream gitlab-workhorse {  server unix:/home/git/gitlab/tmp/sockets/ gitlab-workhorse.socket fail_timeout=0;} server {  listen 80 ;  server_name www.gitlab810.com;   server_tokens off;  access_log  logs/gitlab_access.log;  error_log    logs/gitlab_error.log;  location / {    client_max_body_ size 0;    gzip off;    proxy_read_timeout       300;    proxy_connect_timeout   300;     proxy_redirect          off;     Proxy_http_version 1.1;    proxy_set_header    host                 $http _host;     proxy_set_header    X-Forwarded-Host     "";     proxy_set_header    X-Real-IP             $remote _addr;    proxy_set_header     x-forwarded-for      $proxy _add_x_forwarded_for;    proxy_set_ header    x-forwarded-proto    $scheme;     proxy_pass  http://gitlab-workhorse;  }  error_page 404 /404.html;  error_ page 422 /422.html;  error_page 500 /500.html;  error_page 502  /502.html;  error_page 503 /503.html;  location ~ ^/(404|422|500 |502|503) \.HTML$ { &NBsp;  root /home/git/gitlab/public;    internal;  }} 

Note Line 55th: Proxy_set_header Host $http _host; To change it into your own server_name.

Pit Three:

[Email protected] git]# vim/home/git/gitlab-shell/config.yml---user:gitgitlab_url: "http://www.gitlab810.com/" Http_settings:self_signed_cert:falseauth_file: "/home/git/.ssh/authorized_keys" Redis:bin:/usr/local/redis/ REDIS-CLI Namespace:resque:gitlab host:127.0.0.1 Port:6379log_level:infoaudit_usernames:false

Gitlab_url: "http://www.gitlab810.com/" This is a standard format, I use the form of www.gitlab810.com error

This article is from the "bottom 20,000" blog, please be sure to keep this source http://huwei555.blog.51cto.com/1347480/1827678

Gitlab installation of various pits