本站教程收集整理的这篇文章主要介绍了nginx – 反向代理背后的Gitlab Docker容器，本站教程本站觉得挺不错的，现在分享给大家，也给大家做个参考。
我用正式的Docker容器安装了gitlab：
我正在使用Nginx作为反向代理：
@H_874_6@ upstream gitlab {
server localhost:8002;
}
server {
listen 443 ssl;
listen [::]:443 ssl;
keepalive_timeout 70;
ssl_certificate /etc/letsencrypt/live/git.cedware.com/cert.pem;
ssl_certificate_key /etc/letsencrypt/live/git.cedware.com/privkey.pem;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
server_name git.cedware.com;
client_max_body_size 300M;
LOCATIOn / {
proxy_http_version 1.1;
proxy_pass http://localhost:8002/;
proxy_set_header Host $host;
proxy_set_header X-Forwared-Ssl off;
proxy_set_header X-ForWARDed-For $proxy_add_x_forWARDed_for;
}
}
这一切都很好,直到我将此行添加到gitlab.rb
@H_874_6@external_url 'https://git.cedware.com';
重启容器后,Nginx无法访问gitlab.有人能告诉我我的设置有什么问题吗？
编辑：
这是curl -v https://git.cedware.com的输出：
@H_874_6@* Rebuilt URL to: https://git.cedware.com/
* Trying 37.120.177.116...
* Connected to git.cedware.com (37.120.177.116) port 443 (#0)
* found 175 certificates in /etc/ssl/certs/ca-certificates.crt
* found 700 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
* server certificate verification OK
* server certificate status verification SKIPPED
* common name: git.cedware.com (matched)
* server certificate expiration date OK
* server certificate activation date OK
* certificate public key: RSA
* certificate version: #3
* subject: CN=git.cedware.com
* start date: Wed, 04 Jan 2017 16:58:00 GMT
* expire date: Tue, 04 Apr 2017 16:58:00 GMT
* issuer: C=US,O=Let's Encrypt,CN=Let's Encrypt Authority X3
* compression: NULL
* ALPN, server accepted to use http/1.1
> GET / http/1.1
> Host: git.cedware.com
> User-Agent: curl/7.47.0
> Accept: */*
>
< http/1.1 502 Bad Gateway
< Server: Nginx/1.10.0 (Ubuntu)
< Date: Thu, 05 Jan 2017 08:45:52 GMT
< Content-Type: text/html
< Content-Length: 182
< Connection: keep-alive
<
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>Nginx/1.10.0 (Ubuntu)</center>
</body>
</html>
* Connection #0 to host git.cedware.com left intact
这是Nginx error.log的内容：
@H_874_6@> 2017/01/05 09:47:43 [error] 26258#26258: *1 recv() Failed (104:
> Connection reset by peer) while reading response header from upstream,
> client: 217.7.247.238, server: git.cedware.com, request: "GET /
> http/1.1", upstream: "http://127.0.0.1:8002/", host: "git.cedware.com"
> 2017/01/05 09:47:43 [error] 26258#26258: *1 recv() Failed (104:
> Connection reset by peer) while reading response header from upstream,
> client: 2便宜香港vps17.7.247.238, server: git.cedware.com, request: "GET /
> http/1.1", upstream: "http://[::1]:8002/", host: "git.cedware.com"
> 2017/01/05 09:47:43 [error] 26258#26258: *1 no live upstreams while
> connecTing to upstream, client: 217.7.247.238, server:
> git.cedware.com, request: "GET /favicon.ico http/1.1", upstream:
> "http://localhost/favicon.ico", host: "git.cedware.com", referrer:
> "https://git.cedware.com/"
解决方法:
根据日志中显示的Nginx错误,上游没有响应.这不是Nginx错误.
很可能您的容器已关闭或卡在重启循环中.
使用docker ps查看容器状态.然后使用docker logs< containername>查看它产生的任何错误.
gitlab可能不喜欢你的gitlab.rb修改.日志应该告诉你更多.
本站总结
以上是本站教程为你收集整理的nginx – 反向代理背后的Gitlab Docker容器全部内容，希望文章能够帮你解决nginx – 反向代理背后的Gitlab Docker容器所遇到的程序开发问题。
如果觉得本站教程网站内容还不错，欢迎将本站教程推荐给好友。
本图文内容来源于网友网络收集整理提供，作为学习参考使用，版权属于原作者。
如您有任何意见或建议可联系处理。
