GitLab7升级到了8.2后无法push解决方法

我把gitlab7升级到了8.2，发现http协议下无法push，错误如下，ssh协议可以。error: Cannot access URL https://git…/repo.git/, return code 22 fatal: git-http-push failed error: failed to push some refs to ‘https://git…/repo.git’整了半天，因为我们是用自己的nginx的，没用gitlab内置的，问题就在这里。新版的gitlab搞了个啥gitlab-workhorse。其实把nginx配置成如下就可以解决问题了。特此记录一下这个。## GitLab
##
## Lines starting with two hashes （##） are comments with information.
## Lines starting with one hash （#） are configuration parameters that can be uncommented.
##
##################################
## CONTRIBUTING ##
##################################
##
## If you change this file in a Merge Request, please also create
## a Merge Request on https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests
##
##################################
## CHUNKED TRANSFER ##
##################################
##
## It is a known issue that Git-over-HTTP requires chunked transfer encoding [0]
## which is not supported by Nginx < 1.3.9 [1]. As a result, pushing a large object
## with Git （i.e. a single large file） can lead to a 411 error. In theory you can get
## around this by tweaking this configuration file and either:
## - installing an old version of Nginx with the chunkin module [2] compiled in, or
## - using a newer version of Nginx.
##
## At the time of writing we do not know if either of these theoretical solutions works.
## As a workaround users can use Git over SSH to push large files.
##
## [0] https://git.kernel.org/cgit/git/git.git/tree/Documentation/technical/http-protocol.txt#n99
## [1] https://github.com/agentzh/chunkin-nginx-module#status
## [2] https://github.com/agentzh/chunkin-nginx-module
##
###################################
## configuration ##
###################################
##
## See installation.md#using-https for additional HTTPS configuration details.upstream gitlab {
server unix:/var/opt/gitlab/gitlab-rails/sockets/gitlab.socket fail_timeout=0;
}upstream gitlab-workhorse {
server unix:/var/opt/gitlab/gitlab-workhorse/socket;
}## Normal HTTP host
server {
## Either remove "default_server" from the listen line below,
## or delete the /etc/nginx/sites-enabled/default file. This will cause gitlab
## to be served if you visit any address that your server responds to, eg.
## the ip address of the server （http://x.x.x.x/）n 0.0.0.0:80 default_server;
listen 0.0.0.0:80 default_server;
listen [::]:80 default_server;
server_name YOUR_SERVER_FQDN; ## Replace this with something like gitlab.example.com
server_tokens off; ## Don"t show the nginx version number, a security best practice
root /opt/gitlab/embedded/service/gitlab-rails/public; ## Increase this if you want to upload large attachments
## Or if you want to accept large git objects over http
client_max_body_size 20m; ## See app/controllers/application_controller.rb for headers set ## Individual nginx logs for this GitLab vhost
access_log /var/log/nginx/gitlab_access.log;
error_log /var/log/nginx/gitlab_error.log; location / {
## Serve static files from defined root folder.
## @gitlab is a named location for the upstream fallback, see below.
try_files $uri $uri/index.html $uri.html @gitlab;
} ## We route uploads through GitLab to prevent XSS and enforce access control.
location /uploads/ {
## If you use HTTPS make sure you disable gzip compression
## to be safe against BREACH attack.
# gzip off; ## https://github.com/gitlabhq/gitlabhq/issues/694
## Some requests take more than 30 seconds.
proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_redirect off; proxy_set_header Host $http_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_set_header X-Frame-Options SAMEORIGIN; proxy_pass http://gitlab;
} ## If a file, which is not found in the root folder is requested,
## then the proxy passes the request to the upsteam （gitlab unicorn）.
location @gitlab { ## https://github.com/gitlabhq/gitlabhq/issues/694
## Some requests take more than 30 seconds.
proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_redirect off; proxy_set_header Host $http_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_set_header X-Frame-Options SAMEORIGIN; proxy_pass http://gitlab;
} location ~ ^/[w.-]+/[w.-]+/gitlab-lfs/objects {
client_max_body_size 0;
# "Error" 418 is a hack to re-use the @gitlab-workhorse block
error_page 418 = @gitlab-workhorse;
return 418;
} location ~ ^/[w.-]+/[w.-]+/（info/refs|git-upload-pack|git-receive-pack）$ {
client_max_body_size 0;
# "Error" 418 is a hack to re-use the @gitlab-workhorse block
error_page 418 = @gitlab-workhorse;
return 418;
} location ~ ^/[w.-]+/[w.-]+/repository/archive {
client_max_body_size 0;
# "Error" 418 is a hack to re-use the @gitlab-workhorse block
error_page 418 = @gitlab-workhorse;
return 418;
} location ~ ^/api/v3/projects/.*/repository/archive {
client_max_body_size 0;
# "Error" 418 is a hack to re-use the @gitlab-workhorse block
error_page 418 = @gitlab-workhorse;
return 418;
} # Build artifacts should be submitted to this location
location ~ ^/[w.-]+/[w.-]+/builds/download {
client_max_body_size 0;
# "Error" 418 is a hack to re-use the @gitlab-workhorse block
error_page 418 = @gitlab-workhorse;
return 418;
} # Build artifacts should be submitted to this location
location ~ /ci/api/v1/builds/[0-9]+/artifacts {
client_max_body_size 0;
# "Error" 418 is a hack to re-use the @gitlab-workhorse block
error_page 418 = @gitlab-workhorse;
return 418;
} location @gitlab-workhorse { ## If you use HTTPS make sure you disable gzip compression
## to be safe against BREACH attack.
# gzip off; ## https://github.com/gitlabhq/gitlabhq/issues/694
## Some requests take more than 30 seconds.
proxy_read_timeout 300;
proxy_connect_timeout 300;
proxy_redirect off; # Do not buffer Git HTTP responses
proxy_buffering off; # The following settings only work with NGINX 1.7.11 or newer
#
# # Pass chunked request bodies to gitlab-workhorse as-is
# proxy_request_buffering off;
# proxy_http_version 1.1; proxy_set_header Host $http_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;
} ## Enable gzip compression as per rails guide:
## http://guides.rubyonrails.org/asset_pipeline.html#gzip-compression
## WARNING: If you are using relative urls remove the block below
## See config/application.rb under "Relative url support" for the list of
## other files that need to be changed for relative url support
location ~ ^/（assets）/ {
root /opt/gitlab/embedded/service/gitlab-rails/public;
gzip_static on; # to serve pre-gzipped version
expires max;
add_header Cache-Control public;
} error_page 502 /502.html;
}更多GitLab相关教程见以下内容：Ubuntu 14.04下安装GitLab指南 http://www.linuxidc.com/Linux/2015-12/126876.htm如何在Ubuntu Server 14.04下安装Gitlab中文版 http://www.linuxidc.com/Linux/2015-12/126875.htmCentOS源码安装GitLab汉化版 http://www.linuxidc.com/Linux/2015-10/124648.htm在 Ubuntu 12.04 上安装 GitLab http://www.linuxidc.com/Linux/2012-12/75249.htmGitLab 5.3 升级注意事项 http://www.linuxidc.com/Linux/2013-06/86473.htm在 CentOS 上部署 GitLab （自托管的Git项目仓库） http://www.linuxidc.com/Linux/2013-06/85754.htm在RHEL6/CentOS6/ScientificLinux6上安装GitLab 6.0.2 http://www.linuxidc.com/Linux/2014-03/97831.htmCentOS 6.5安装GitLab教程及相关问题解决 http://www.linuxidc.com/Linux/2014-05/101526.htm升级GitLab到8.2.0 http://www.linuxidc.com/Linux/2015-12/126220.htmGitLab 的详细介绍：请点这里
GitLab 的下载地址：请点这里 本文永久更新链接地址