堆栈内存溢出
  简体   繁体   English

反向代理后面的Gitlab Docker容器

[英]Gitlab Docker container behind reverse Proxy

 原文  2017-01-05 08:26:49  5   2    nginx/ docker/ gitlab

问题描述

I installed gitlab with the offical Docker container: 我用正式的Docker容器安装了gitlab：

docker run -d -p 8002:80 -v /mnt/gitlab/etc/gitlab:/etc/gitlab -v /mnt/gitlab/var/opt/gitlab:/var/opt/gitlab -v /mnt/gitlab/var/log/gitlab:/var/log/gitlab gitlab/gitlab-ce docker run -d -p 8002：80 -v / mnt / gitlab / etc / gitlab：/ etc / gitlab -v / mnt / gitlab / var / opt / gitlab：/ var / opt / gitlab -v / mnt / gitlab / var / log / gitlab：/ var / log / gitlab gitlab / gitlab-ce

I'm using nginx as reverse proxy: 我正在使用nginx作为反向代理： 

    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;
        }
}

This all works totally fine, until I add this line to the gitlab.rb 这一切都很好，直到我将此行添加到gitlab.rb 

external_url 'https://git.cedware.com';

After restarting the container, nginx can't reach gitlab. 重启容器后，nginx无法访问gitlab。 Can someone tell me what's wrong with my setup? 有人能告诉我我的设置有什么问题吗？

Edit: This is the output of curl -v https://git.cedware.com : 编辑：这是curl -v https://git.cedware.com的输出： 

* 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

And this is the content of the nginx error.log: 这是nginx error.log的内容： 

> 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: 217.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/"

2 个解决方案

解决方案1
 2 已采纳  2017-01-05 08:56:18

As per the nginx error shown in the log the upstream is not responding. 根据日志中显示的nginx错误，上游没有响应。 This is not a nginx error. 这不是nginx错误。

Most likely your container is either down or stuck in a restart loop. 很可能您的容器已关闭或卡在重启循环中。

Use docker ps to see the container status. 使用docker ps查看容器状态。 Then use docker logs <containername> to see any errors it generates. 然后使用docker logs <containername>查看它生成的任何错误。

It is possible that gitlab doesn't like your gitlab.rb modification. gitlab可能不喜欢你的gitlab.rb修改。 The log should tell you more. 日志应该告诉你更多。

解决方案2
 0  2018-01-19 01:35:54

You should expose 443 port of container since you are using https for gitlab. 您应该公开443端口的容器，因为您使用https进行gitlab。

Also your location in host system's Nginx settign should be https://localhost:some_443_port/ 您在主机系统的Nginx设置中的位置也应该是https：// localhost：some_443_port /

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Gitlab vs Registry in docker 容器后面的代理错误 - Gitlab vs Registry in docker container behind proxy ERROR 让 GitLab 在 Nginx 反向代理后面运行 - Get GitLab running behind Nginx Reverse Proxy Nginx反向代理背后的Gitlab 5.3 - Gitlab 5.3 behind nginx reverse proxy Nginx 反向代理背后的 Gitlab Kubernetes 代理 - Gitlab Kubernetes Agent behind Nginx Reverse Proxy 如何从另一个容器访问其公共地址上的反向代理后面的 docker 容器 - How to access a docker container behind a reverse proxy on it's public address from another container 反向代理位置到Docker容器 - Reverse proxy location to docker container 反向代理 Nginx Docker 容器 - Reverse Proxy Nginx Docker Container Nginx 作为 docker 容器上的反向代理 - Nginx as reverse proxy on docker container gitlab docker nginx 反向代理到子路径 - gitlab docker nginx reverse proxy to a sub path 用于保护Docker容器的Docker Nginx反向代理 - Docker Nginx Reverse Proxy for Protection of Docker Container
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM