【问题标题】:HTTPS not working in nginx reverse proxy (docker compose)HTTPS 在 nginx 反向代理中不起作用(docker compose)
【发布时间】:2021-11-14 14:06:42
【问题描述】:

我有一个 Rails 应用程序,一个 mysql 数据库,我正在尝试使用 nginx 配置反向代理服务器。 HTTP 连接顺利,但无论我尝试什么 - HTTPS 连接都不会成功。 nginx 服务器不会监听 443。我尝试了很多解决方案(例如123),但都没有成功。

我使用我们自己的证书而不是letsencrypt 或其他类似的可能性。

docker-compose.yml:

version: "3"
services:
  proxy:
    image: jwilder/nginx-proxy
    container_name: proxy
    restart: always
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock
      - /home/ssl:/etc/nginx/certs
      - /home/log/nginx:/var/log/nginx
    environment:
      - DEFAULT_HOST=app.test
    
  db:
    container_name: db
    image: mysql:8.0
    restart: always
    .
    .
    .
    ports:
      - "3306:3306"

  app:
    container_name: app
    .
    .
    .
    environment:
      - VIRTUAL_HOST=app.test
      - VIRTUAL_PORTO=https
      - HTTPS_METHOD=redirect
      - CERT_NAME=app.test

运行 docker exec -it proxy ls -l /etc/nginx/certs 显示证书已安装:

total 8
-rw-rw-r-- 1 1000 1000 1391 Nov  8 14:36 app.test.crt
-rw-rw-r-- 1 1000 1000 1751 Nov  8 14:29 app.test.key

运行docker exec -it proxy cat /etc/nginx/conf.d/default.conf:

# If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
# scheme used to connect to this server
map $http_x_forwarded_proto $proxy_x_forwarded_proto {
  default $http_x_forwarded_proto;
  ''      $scheme;
}
# If we receive X-Forwarded-Port, pass it through; otherwise, pass along the
# server port the client connected to
map $http_x_forwarded_port $proxy_x_forwarded_port {
  default $http_x_forwarded_port;
  ''      $server_port;
}
# If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any
# Connection header that may have been passed to this server
map $http_upgrade $proxy_connection {
  default upgrade;
  '' close;
}
# Apply fix for very long server names
server_names_hash_bucket_size 128;
# Default dhparam
ssl_dhparam /etc/nginx/dhparam/dhparam.pem;
# Set appropriate X-Forwarded-Ssl header based on $proxy_x_forwarded_proto
map $proxy_x_forwarded_proto $proxy_x_forwarded_ssl {
  default off;
  https on;
}
gzip_types text/plain text/css application/javascript application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
log_format vhost '$host $remote_addr - $remote_user [$time_local] '
                 '"$request" $status $body_bytes_sent '
                 '"$http_referer" "$http_user_agent" '
                 '"$upstream_addr"';
access_log off;
                ssl_protocols TLSv1.2 TLSv1.3;
                ssl_ciphers 'ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384';
                ssl_prefer_server_ciphers off;
resolver 127.0.0.11;
# HTTP 1.1 support
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $proxy_connection;
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 $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Ssl $proxy_x_forwarded_ssl;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
# Mitigate httpoxy attack (see README for details)
proxy_set_header Proxy "";
server {
        server_name _; # This is just an invalid value which will never trigger on a real hostname.
        server_tokens off;
        listen 80;
        access_log /var/log/nginx/access.log vhost;
        return 503;
}
# app.test
upstream app.test {
        ## Can be connected with "test_default" network
        # app
        server 192.168.176.4:3000;
}
server {
        server_name app.test;
        listen 80 default_server;
        access_log /var/log/nginx/access.log vhost;
        location / {
                proxy_pass http://app.test;
        }
}

如您所见,没有创建 443 个子句。尝试联系时,我在 chrome 上收到 ERR_CONNECTION_REFUSED 消息,但 access.logerror.log 均未记录任何内容。

有什么想法吗?过去三天我一直在尝试破解它。

【问题讨论】:

    标签: docker-compose nginx-reverse-proxy


    【解决方案1】:

    解决方案已经出现here,需要将CERT_NAME添加到proxy环境中,并将证书目录也挂载到应用中:

    docker-compose.yml:

    version: "3"
    services:
      proxy:
        image: jwilder/nginx-proxy
        container_name: proxy
        restart: always
        ports:
          - "80:80"
          - "443:443"
        volumes:
          - /var/run/docker.sock:/tmp/docker.sock
          - /home/ssl:/etc/nginx/certs
          - /home/log/nginx:/var/log/nginx
        environment:
          - DEFAULT_HOST=app.test
          - CERT_NAME=app.test
        
      db:
        container_name: db
        image: mysql:8.0
        restart: always
        .
        .
        .
        ports:
          - "3306:3306"
    
      app:
        container_name: app
        .
        .
        .
        volumes:
          .
          .
          .
          - /home/ssl:/etc/ssl/certs:ro
        environment:
          - VIRTUAL_HOST=app.test
          - CERT_NAME=app.test
    

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 2020-07-29
      • 2018-05-31
      • 1970-01-01
      • 1970-01-01
      • 2020-06-23
      • 2019-05-03
      • 1970-01-01
      • 2020-11-28
      相关资源
      最近更新 更多