无法在Docker上的NginX反向代理后面访问Kibana

如何解决无法在Docker上的NginX反向代理后面访问Kibana

我使用NginX，ElasticSearch和Kibana进行了Docker Compose设置，如下所示：

web:
    build:
      context: .
      dockerfile: ./system/docker/development/web.Dockerfile
    depends_on:
      - app
    volumes:
      - './system/ssl:/etc/ssl/certs'
    networks:
      - mynet
    ports:
      - 80:80
      - 443:443

  elasticsearch_1:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.7.0
    container_name: "${COMPOSE_PROJECT_NAME:-service}_elasticsearch_1"
    environment:
      - node.name=elasticsearch_1
      - cluster.name=es-docker-cluster
      - discovery.seed_hosts=elasticsearch_2,elasticsearch_3
      - cluster.initial_master_nodes=elasticsearch_1,elasticsearch_2,elasticsearch_3
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - es_volume_1:/usr/share/elasticsearch/data
    ports:
      - 9200:9200
    networks:
      - mynet

  elasticsearch_2:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.7.0
    container_name: "${COMPOSE_PROJECT_NAME:-service}_elasticsearch_2"
    environment:
      - node.name=elasticsearch_2
      - cluster.name=es-docker-cluster
      - discovery.seed_hosts=elasticsearch_1,elasticsearch_3
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - es_volume_2:/usr/share/elasticsearch/data
    ports:
      - 9201:9201
    networks:
      - mynet

  elasticsearch_3:
    image: docker.elastic.co/elasticsearch/elasticsearch:7.7.0
    container_name: "${COMPOSE_PROJECT_NAME:-service}_elasticsearch_3"
    environment:
      - node.name=elasticsearch_3
      - cluster.name=es-docker-cluster
      - discovery.seed_hosts=elasticsearch_1,elasticsearch_2
      - cluster.initial_master_nodes=elasticsearch_1,elasticsearch_3
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    ulimits:
      memlock:
        soft: -1
        hard: -1
    volumes:
      - es_volume_3:/usr/share/elasticsearch/data
    ports:
      - 9202:9202
    networks:
      - mynet

  kibana:
    image: docker.elastic.co/kibana/kibana:7.7.0
    container_name: "${COMPOSE_PROJECT_NAME:-service}_kibana"
    ports:
      - 5601:5601
    environment:
      ELASTICSEARCH_URL: http://elasticsearch_1:9200
      ELASTICSEARCH_HOSTS: http://elasticsearch_1:9200
    networks:
      - mynet
      
volumes:
  es_volume_1: null
  es_volume_2: null
  es_volume_3: null

networks:
  mynet:
    driver: bridge
    ipam:
      config:
      - subnet: 172.18.0.0/24
        gateway: 172.18.0.1

这是我的NginX配置：

server {
   listen 80;
   listen 443 ssl http2;

   ssl_certificate /ssl/localhost.crt;
   ssl_certificate_key /ssl/localhost.key;

  ...

  location /app/kibana {
     proxy_pass http://kibana:5601;
     proxy_http_version 1.1;
     proxy_set_header Upgrade $http_upgrade;
     proxy_set_header Connection 'upgrade';
     proxy_set_header Host $host;
     proxy_cache_bypass $http_upgrade;
     proxy_set_header X-Real-IP $remote_addr;
     proxy_set_header Connection "Keep-Alive";
     proxy_set_header Proxy-Connection "Keep-Alive";
     proxy_set_header Authorization "";
  }

   location ~ /\. {    
      deny all;  
   }
   
   ...
}

当我尝试使用http://localhost/app/kibana访问Kibana时，我看到一个空白页，并且能够在浏览器控制台中看到错误：

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'self'". Either the 'unsafe-inline' keyword,a hash ('sha256-P5polb1UreUSOe5V/Pv7tc+yeZuJXiOi/3fqhGsU7BE='),or a nonce ('nonce-...') is required to enable inline execution.

kibana:348 GET https://localhost/bundles/app/kibana/bootstrap.js net::ERR_ABORTED 404

manifest.json:1 GET https://localhost/ui/favicons/manifest.json 404

如果我将以下location添加到我的NginX配置中，UI将开始显示，但页面仍然没有响应：

  location ~ (/app|/translations|/node_modules|/built_assets/|/bundles|/es_admin|/plugins|/api|/ui|/elasticsearch|/spaces/enter) {
         proxy_pass          http://kibana:5601;
         proxy_set_header    Host $host;
         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 $scheme;
         proxy_set_header    X-Forwarded-Host $http_host;
         proxy_set_header    Authorization "";
         proxy_hide_header   Authorization;
  }

并且浏览器控制台中还有其他错误：

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-eval' 'self'". Either the 'unsafe-inline' keyword,or a nonce ('nonce-...') is required to enable inline execution.

commons.bundle.js:3 GET https://localhost/internal/security/session 404

Detected an unhandled Promise rejection.
Error

解决方法

现在首选使用简单的容器名称。相反，container_name: "${COMPOSE_PROJECT_NAME:-service}_kibana"使用container_name: "kibana"。您以后可以更改它们，但要记住还要更新该名称的所有引用（例如Nginx配置中的Kibana上游主机或Kibana的ELASTICSEARCH_HOSTS配置）。

唯一需要在实际计算机上打开端口的容器是带有Nginx的Web容器。删除所有其他ports: xxxx:yyyy映射。

对于您的Nginx配置，您只需要一个简单的location指令：

location / {
     proxy_pass http://kibana:5601;
}

将Kibana安装在其他位置时，必须按照here的说明配置Kibana的server.basePath。

location /kibana/ {
     proxy_pass http://kibana:5601;
}

  kibana:
    container_name: kibana
    image: docker.elastic.co/kibana/kibana:7.7.0
    environment:
      SERVER_BASEPATH: /kibana
      SERVER_REWRITEBASEPATH: 'false'
      ELASTICSEARCH_HOSTS: http://elasticsearch_1:9200
    networks:
      - mynet

此NginX配置对我来说适用于Kibana（尽管它为我的其他应用造成了问题）：

location /app/kibana/ {
  proxy_pass http://kibana:5601;
}

location ~ (/app|/api|/internal|/translations|/bundles|/ui|/built_assets/|/elasticsearch|/spaces/enter) {
      proxy_pass          http://kibana:5601;
      proxy_set_header    Host $host;
      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 $scheme;
      proxy_set_header    X-Forwarded-Host $http_host;
      proxy_set_header    Authorization "";
      proxy_hide_header   Authorization;
  }

我发现internal在第二个location中也需要处理。感谢@mikezter帮助消除了第一个问题。

无法在Docker上的NginX反向代理后面访问Kibana

如何解决无法在Docker上的NginX反向代理后面访问Kibana

解决方法

相关推荐