Nginx中的proxy_pass总是返回502错误的网关错误

编程问答 2022-06-13

问题描述

我有一台服务器，我想部署一个带有几个Docker容器的网站。我使用jwilder/nginx-proxy，并使用此配置，example.com正常工作：

version: "3"

networks:
  Nginx-proxy:
    ipam:
      driver: default
      config:
        - subnet: 172.18.0.0/16

services:
  Nginx-proxy:
    image: jwilder/Nginx-proxy
    container_name: Nginx-proxy
    restart: always
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - certs:/etc/Nginx/certs:ro
      - ./vhostd:/etc/Nginx/vhost.d
      - html:/usr/share/Nginx/html
      - /var/run/docker.sock:/tmp/docker.sock:ro
    networks:
      - Nginx-proxy

  letsencrypt-Nginx-proxy-companion:
    container_name: letsencrypt
    image: jrcs/letsencrypt-Nginx-proxy-companion
    volumes:
      - certs:/etc/Nginx/certs
      - ./vhostd:/etc/Nginx/vhost.d
      - html:/usr/share/Nginx/html
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      DEFAULT_EMAIL: [email protected]
      Nginx_PROXY_CONTAINER: Nginx-proxy
    restart: always
    networks:
      - Nginx-proxy

  auth-service:
    image: auth-service
    restart: always
    command: "bash -c python3 manage.py makemigrations && python3 manage.py migrate"
    volumes:
      - /home/ubuntu/projects/project/microservices/auth/:/home/project/auth
    networks:
      - Nginx-proxy
    environment:
      VIRTUAL_HOST: auth
      VIRTUAL_PORT: 80

  plans-service:
    image: plans-service
    restart: always
    command: "bash -c python3 manage.py makemigrations && python3 manage.py migrate"
    volumes:
      - /home/ubuntu/projects/project/microservices/plans/:/home/project*emphasized text*/plans
    networks:
      - Nginx-proxy
    environment:
      VIRTUAL_HOST: plans
      VIRTUAL_PORT: 80

  web-ui:
    image: web-ui
    expose:
      - 80
    volumes:
      - /home/ubuntu/projects/project/example.com/src/:/var/www/example.com
    restart: always
    environment:
      VIRTUAL_HOST: example.com
      LETSENCRYPT_HOST: example.com
      LETSENCRYPT_EMAIL: [email protected]
    container_name: web-ui
    networks:
      - Nginx-proxy
volumes:
  certs:
  html:

我想将example.com/auth传递给VIRTUAL_HOST auth，并将example.com/plans传递给VIRTUAL_HOST plans。因此在vhostd文件夹中有一个名为example.com_location的文件，并将其放入其中：

location /auth {
  proxy_set_header Host $host;
  proxy_set_header X-Real-IP $remote_addr;
  proxy_pass http://auth;
}

location /plans {
  proxy_set_header Host $host;
  proxy_set_header X-Real-IP $remote_addr;
  proxy_pass http://plans;
}

这些配置似乎没问题，我通过docker-compose.yml运行了第一个sudo docker-compose up -d。容器成功启动。为了测试它，在Postman应用中，我这样调用一个网址：

https://example.com/auth/getsms

，我希望实现的服务器会做出响应。但是每次我得到server error 502. Bad gateway。我将此配置更改为我知道的任何状态，并对此进行了研究，但都收到502错误。

这是Nginx-proxy容器的/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 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
map $scheme $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"';
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.
    listen 80;
    access_log /var/log/Nginx/access.log vhost;
    return 503;
}
server {
    server_name _; # This is just an invalid value which will never trigger on a real hostname.
    listen 443 ssl http2;
    access_log /var/log/Nginx/access.log vhost;
    return 503;
    ssl_session_cache shared:SSL:50m;
    ssl_session_tickets off;
    ssl_certificate /etc/Nginx/certs/default.crt;
    ssl_certificate_key /etc/Nginx/certs/default.key;
}
# auth
upstream auth {
                ## Can be connected with "controller_Nginx-proxy" network
            # controller_auth-service_1
            server 172.18.0.8:80;
}
server {
    server_name auth;
    listen 80 ;
    access_log /var/log/Nginx/access.log vhost;
    location / {
        proxy_pass http://auth;
    }
}
server {
    server_name auth;
    listen 443 ssl http2 ;
    access_log /var/log/Nginx/access.log vhost;
    return 500;
    ssl_certificate /etc/Nginx/certs/default.crt;
    ssl_certificate_key /etc/Nginx/certs/default.key;
}
# plans
upstream plans {
                ## Can be connected with "controller_Nginx-proxy" network
            # controller_plans-service_1
            server 172.18.0.7:80;
}
server {
    server_name plans;
    listen 80 ;
    access_log /var/log/Nginx/access.log vhost;
    location / {
        proxy_pass http://plans;
    }
}
server {
    server_name plans;
    listen 443 ssl http2 ;
    access_log /var/log/Nginx/access.log vhost;
    return 500;
    ssl_certificate /etc/Nginx/certs/default.crt;
    ssl_certificate_key /etc/Nginx/certs/default.key;
}
# example.com
upstream example.com {
                ## Can be connected with "controller_Nginx-proxy" network
            # web-ui
            server 172.18.0.4:80;
}
server {
    server_name example.com;
    listen 80 ;
    access_log /var/log/Nginx/access.log vhost;
    # Do not HTTPS redirect Let'sEncrypt Acme challenge
    location /.well-kNown/acme-challenge/ {
        auth_basic off;
        allow all;
        root /usr/share/Nginx/html;
        try_files $uri =404;
        break;
    }
    location / {
        return 301 https://$host$request_uri;
    }
}
server {
    server_name example.com;
    listen 443 ssl http2 ;
    access_log /var/log/Nginx/access.log vhost;
    ssl_session_timeout 5m;
    ssl_session_cache shared:SSL:50m;
    ssl_session_tickets off;
    ssl_certificate /etc/Nginx/certs/example.com.crt;
    ssl_certificate_key /etc/Nginx/certs/example.com.key;
    ssl_dhparam /etc/Nginx/certs/example.com.dhparam.pem;
    ssl_stapling on;
    ssl_stapling_verify on;
    ssl_trusted_certificate /etc/Nginx/certs/example.com.chain.pem;
    add_header Strict-Transport-Security "max-age=31536000" always;
    include /etc/Nginx/vhost.d/example.com;
    location / {
        proxy_pass http://example.com;
        include /etc/Nginx/vhost.d/example.com_location;
    }
}

这也是Nginx-proxy个容器日志：

dockergen.1 | 2020/09/19 15:35:28 Generated '/etc/Nginx/conf.d/default.conf' from 8 containers
dockergen.1 | 2020/09/19 15:35:28 Watching docker events
dockergen.1 | 2020/09/19 15:35:28 Contents of /etc/Nginx/conf.d/default.conf did not change. Skipping notification 'Nginx -s reload'
.
.
.

我不知道该如何克服。如果您能帮助我，那就太好了。

解决方法

暂无找到可以解决该程序问题的有效方法，小编努力寻找整理中！

如果你已经找到好的解决方法，欢迎将解决方案带上本链接一起发送给小编。

小编邮箱:dio#foxmail.com (将#修改为@）

dockerjwilder-nginx-proxyproxypass