帶有埠轉發的Nginx反向代理不起作用-有解無憂

我無法訪問本地托管的網站。這個想法是托管在 docker 容器中并位于 Nginx 代理后面的站點應該可以從 Internet 訪問。

我有一個帶有 NoIP 的主機名，我們稱之為stuff.ddns.net.
我已經為 NoIP DNS 服務器設定了 IP 更新（即，stuff.ddns.net始終指向我的路由器）。
我的路由器將埠轉發到本地網路（Linux 機器）上的靜態 IP 80。443
我在前面提到的 Linux 機器上的 Docker 容器中托管了一個 Apache Airflow Web 服務器，并且我已經設定了AIRFLOW__WEBSERVER__BASE_URL: 'https://stuff.ddns.net/airflow'.

當我嘗試stuff.ddns.net/airflow在我的網路瀏覽器中訪問時，我得到Safari can't open the page "stuff.ddns.net/airflow" because Safari can't connect to the server "stuff.ddns.net".

這是我的 nginx.conf：

# top-level http config for websocket headers
# If Upgrade is defined, Connection = upgrade
# If Upgrade is empty, Connection = close
events { 
    worker_connections 1024;
}

http {
    map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
    }

    upstream airflow {
        server localhost:8080;
    }

    server {
        listen [::]:80;
        server_name stuff.ddns.net;
        return 302 https://$host$request_uri;
    }

    server {
        listen [::]:443 ssl;

        server_name stuff.ddns.net;

        ssl_certificate /run/secrets/stuff_ddns_net_pem_chain;
        ssl_certificate_key /run/secrets/stuff_ddns_net_key;

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_prefer_server_ciphers on;
        ssl_dhparam /run/secrets/dhparam.pem;
        ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA';

        location /airflow/ {
            proxy_pass http://airflow;
            proxy_set_header Host $http_host;
            proxy_redirect off;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
        }
    }
}

想法？

編輯：一個截斷的（即，其他氣流組件被忽略）docker-compose.yml，以完全清楚地設定：

version: '3.7'

x-airflow-common:
  &airflow-common
  image: ${AIRFLOW_IMAGE_NAME:-apache/airflow:2.4.0}
  # build: .
  environment:
    &airflow-common-env
    AIRFLOW__CORE__EXECUTOR: CeleryExecutor
    AIRFLOW__CORE__SQL_ALCHEMY_CONN_CMD: 'cat /run/secrets/sql_alchemy_conn'
    AIRFLOW__CELERY__RESULT_BACKEND_CMD: 'cat /run/secrets/result_backend'
    AIRFLOW__CELERY__BROKER_URL: redis://:@redis:6379/0
    AIRFLOW__CORE__FERNET_KEY: ''
    AIRFLOW__CORE__DAGS_ARE_PAUSED_AT_CREATION: 'true'
    AIRFLOW__CORE__LOAD_EXAMPLES: 'false'
    AIRFLOW__API__AUTH_BACKENDS: 'airflow.api.auth.backend.basic_auth'
    AIRFLOW__WEBSERVER__BASE_URL: 'https://stuff.ddns.net/airflow'
    AIRFLOW__WEBSERVER__ENABLE_PROXY_FIX: 'True'
    _PIP_ADDITIONAL_REQUIREMENTS: ${_PIP_ADDITIONAL_REQUIREMENTS:-}
  volumes:
    - ./storage/airflow/dags:/opt/airflow/dags
    - ./storage/airflow/logs:/opt/airflow/logs
    - ./storage/airflow/plugins:/opt/airflow/plugins
  user: "${AIRFLOW_UID:-1000}:0"
  secrets:
    - sql_alchemy_conn
    - result_backend
    - machine_pass
  depends_on:
    &airflow-common-depends-on
    redis:
      condition: service_healthy
    postgres:
      condition: service_healthy

x-stuff-common:
  &stuff-common
  restart: unless-stopped
  networks:
    - ${DOCKER_NETWORK:-stuff}

services:
  nginx:
    <<: *stuff-common
    container_name: stuff-nginx
    image: nginxproxy/nginx-proxy:alpine
    hostname: nginx
    ports:
      - ${PORT_NGINX:-80}:80
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro
      - ./config/nginx.conf:/etc/nginx/nginx.conf:ro
    secrets:
      - stuff_ddns_net_pem_chain
      - stuff_ddns_net_key
      - dhparam.pem

  airflow-webserver:
    <<: *stuff-common
    <<: *airflow-common
    container_name: stuff-airflow-webserver
    command: webserver
    ports:
      - ${PORT_UI_AIRFLOW:-8080}:8080
    healthcheck:
      test: ["CMD", "curl", "--fail", "http://localhost:${PORT_UI_AIRFLOW:-8080}/airflow/health"]
      interval: 10s
      timeout: 10s
      retries: 5
    depends_on:
      <<: *airflow-common-depends-on
      airflow-init:
        condition: service_completed_successfully

networks:
  stuff:
    name: ${DOCKER_NETWORK:-stuff}

secrets:
  ... <truncated>

uj5u.com熱心網友回復：

這里的解決方案是三重的：

Docker 容器使用與所有其他容器相同的橋接網路。
在 nginx.confupstream宣告中，替換為 Docker 主機localhost的LAN IP 地址（這對我有用，因為我使用的是靜態分配的地址）。
listen <PORT>;在 nginx.conf中的指令上方添加listen [::]:<PORT>;（我不確定這是做什么的，但沒有這個一切都會中斷）。

這是 Nginx.conf 的頂部現在的樣子：

    upstream airflow {
        server 192.168.50.165:8080;
    }

    server {
        listen 80;
        listen [::]:80;
        server_name stuff.ddns.net;
        return 302 https://$host$request_uri;
    }

    server {
        listen 443 ssl;
        listen [::]:443 ssl;
        server_name stuff.ddns.net;

    .....

轉載請註明出處，本文鏈接：https://www.uj5u.com/gongcheng/525913.html

標籤：码头工人nginx空气流动

上一篇：nginx：[警告]沖突的服務器名稱“”在0.0.0.0:80，忽略

下一篇：可以將proxy_pass設定為從query_string或標頭引數NGINX代理派生的變數嗎？