Nginx：（111：连接被拒绝）同时连接到上游 wordpress 和 docker答案

【问题标题】：Nginx: (111: Connection refused) while connecting to upstream wordpress & dockerNginx：（111：连接被拒绝）同时连接到上游 wordpress 和 docker
【发布时间】：2020-03-17 12:29:36
【问题描述】：

当我调用网站 (blog.mydomain.de) 时，我遇到以下错误的问题：

502 错误网关 nginx/1.14.2

2020/03/14 23:59:08 [error] 7#7: *1 connect() failed (111: Connection refused) while connecting to upstream, client: $IP, server: blog.mydomain.de, request: "GET / HTTP/2.0", upstream: "https://192.168.160.5:443/", host: "blog.mydomain.de"

所以我的问题是使用 WordPress。我还向您展示了 NextCloud 配置，因为它可以正常工作。我也知道 WordPress nginx 配置应该包含更多内容，但如果我什至遇到此错误，并且缺少 fastcgi 和其他东西，我什至会尝试找到它。

worker_processes auto;

include /etc/nginx/modules-enabled/*.conf;

events {
  worker_connections 1024;
}

http {
  gzip            on;
  gzip_min_length 1000;
  gzip_proxied    expired no-cache no-store private auth;
  gzip_types      text/plain text/css text/xml
                  application/javascript application/json application/xml application/rss+xml image/svg+xml;

  server_names_hash_bucket_size 64;

  access_log /var/log/nginx/access.log;
  error_log /var/log/nginx/error.log;

  more_clear_headers 'server';

  ssl_certificate     /etc/letsencrypt/live/mydomain.de-0001/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/mydomain.de-0001/privkey.pem;
  ssl_trusted_certificate /etc/letsencrypt/live/mydomain.de-0001/chain.pem;
  ssl_dhparam         /etc/ssl/dhparam.pem;
  ssl_protocols       TLSv1.2 TLSv1.3;
  ssl_session_cache   shared:SSL:10m;
  ssl_session_timeout 10m;
  ssl_ciphers         "EECDH-AESGCM:EDH+ESGCM:AES256+EECDH:AES256+EDH";
  ssl_prefer_server_ciphers on;
  add_header          Strict-Transport-Security "max-age=31536000; includeSubdomains; preload";

  server {
    listen 80;
    listen [::]:80;
      server_name blog.mydomain.de cloud.mydomain.de;
    return 301 https://$host$request_uri;
    #return 301 https://$server_name$request_uri;
  }

  # NextCloudPi

  server {
    server_name cloud.mydomain.de;

    listen 443 ssl http2;
    listen [::]:443 ssl http2;

    client_max_body_size 100G;
        underscores_in_headers on;

    location / {
          proxy_headers_hash_max_size 512;
          proxy_headers_hash_bucket_size 64;
          proxy_set_header Host $host;
          proxy_set_header X-Forwarded-Proto $scheme;
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

          add_header Front-End-Https on;
          proxy_pass https://nextcloudpi;
    }
  }

  # NextCloudPi Konfiguration Web-Interface

  server {
    server_name cloud.mydomain.de;

    listen 4443 ssl http2;
    listen [::]:4433 ssl http2;

    location / {
      more_clear_headers 'upgrade';
      more_clear_headers 'Strict-Transport-Security';

      proxy_ssl_verify off;
      proxy_pass https://nextcloudpi:4443;

      proxy_pass_header Authorization;

      proxy_set_header 'X-Forwarded-Host' cloud.mydomain.de;
      proxy_set_header 'X-Forwarded-Proto' https;
      proxy_set_header 'X-Forwarded-For' $remote_addr;
      proxy_set_header 'X-Forwarded-IP' $remote_addr;
    }
  }

  # WordPress

  server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    server_name blog.mydomain.de;

      client_max_body_size 200m;
      underscores_in_headers on;

    location / {
      proxy_pass http://wordpress;
      proxy_set_header X-Forwarded-Host $host;
            proxy_set_header X-Forwarded-Server $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header Host $host;
    }

  }
}

我将它与 docker 容器一起使用。撰写文件如下所示：

version: "3"
networks:
  nextcloudpi:

services:
  nginx:
    restart: always
    container_name: nginx
    image: cptdaydreamer/nginx:latest
    ports:
      - 80:80
      - 443:443
      - 4443:4443
      - 6800:6800
    volumes:
      - /media/storage/nginx:/var/log/nginx
      - /etc/ssl:/etc/ssl
      - /etc/letsencrypt/live:/etc/letsencrypt/live
      - /etc/letsencrypt/archive:/etc/letsencrypt/archive
    links:
      - wordpress
    depends_on:
      - nextcloudpi
    networks:
      - nextcloudpi
      - default
  nextcloudpi:
    restart: always
    container_name: nextcloudpi
    image: cptdaydreamer/nextcloudpi:latest
    expose:
      - 80
      - 443
      - 4443
      - 6800
    volumes:
     - /media/storage/data:/data
     - /etc/localtime:/etc/localtime:ro
    networks:
      - nextcloudpi

  portainer:
    image: portainer/portainer
    command: -H unix:///var/run/docker.sock
    restart: always
    ports:
      - 9001:9000
      - 8000:8000
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /media/storage/portainer:/data
    container_name: portainer

  db:
    container_name: mariadb
    image: mariadb:latest
    #ports:
    #  - 3306:3306
    volumes:
      - /media/storage/mariadb:/var/lib/mysql
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: $PRIVATE
      MYSQL_DATABASE: $PRIVATE
      MYSQL_USER: $PRIVATE
      MYSQL_PASSWORD: $PRIVATE

  wordpress:
    container_name: wordpress
    links:
      - db
    #ports:
    #  - 9000:9000
    depends_on:
      - db
    image: wordpress:latest
    expose:
      - "80"
    restart: always
    volumes:
      - /media/storage/wordpress:/var/www/html
    environment:
      WORDPRESS_DB_HOST: db:3306
      #WORDPRESS_DB_HOST: db
      WORDPRESS_DB_USER: $PRIVATE
      WORDPRESS_DB_PASSWORD: $PRIVATE
      WORDPRESS_DB_NAME: $PRIVATE
      WORDPRESS_TABLE_PREFIX: $PRIVATE

我不知道确切的问题是什么。 wordpress的docker容器的日志显示：

[15-Mar-2020 00:50:24] NOTICE: fpm is running, pid 1
[15-Mar-2020 00:50:24] NOTICE: ready to handle connections

有什么想法吗？

根据要求更新：

Wordpress 图片现在是最新的，而不是 7.3-fpm
当前使用的 nginx.conf

【问题讨论】：

标签： wordpress docker nginx

【解决方案1】：

尝试在代理传递脚本中编辑 wordpress:9000 并将 Nginx 配置更改为此。

location / {
    # First attempt to serve request as file, then
    # as directory, then fall back to displaying a 404.
    try_files $uri $uri/ /index.php?$args;
}

location ~ \.php$ {
    fastcgi_split_path_info ^(.+\.php)(/.+)$;
    fastcgi_pass wordpress:9000;
    fastcgi_index index.php;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    fastcgi_param SCRIPT_NAME $fastcgi_script_name;
}

您的理解有误。 wordpress-php-fpm 图像只是在端口 9000 暴露 PHP-FPM 服务，https://wordpress:443 没有运行任何东西，所以 Nginx 将抛出 502 状态。这就是为什么你应该使用 fastcgi_pass 连接到 PHP-FPM 而不是 proxy_pass 像 NextCloud API 已经在端口 4443 公开 https。

当您将堆栈拆分为 2 个 docker-compose.yml 时，一切都会变得更加清晰和独立。

-- wordpress/
--- docker-compose.yml
--- data/

-- nextcloud/
--- docker-compose.yml
--- data/

这就是 Docker 的工作原理。

根据我的经验，使用 Docker 时，只需保持堆栈独立即可。我的意思是 Nextcloud 与数据库一起使用，很好。然后使用 WordPess 和另一个数据库实例创建另一个堆栈。它充分利用了 Docker 的所有优势，并将应用程序彼此分离。

【讨论】：

不可能，因为我知道配置上游，因为它正在获取 wordpress 的内部 docker 容器 IP。我试图配置一个上游，但没有奏效。而且我从来没有将 docker 容器分成堆栈。我将不得不阅读它，它是如何工作的。
我的配置和你写的完全一样。仍然有错误 502。我现在只能使用 wordpress:latest 图像运行它，并且在我的配置中没有 https。但是 docker-compose 尝试听起来很有趣。甚至不知道我可以运行多个撰写文件。但我不知道那时应该变得更清楚。那么我应该在哪里拥有我的 nginx 容器，因为 wordpress 和 nextcloud 需要它。
更新了我当前的配置