Jira работает с ошибками через обратный прокси Nginx - PullRequest
Новая
       13

Jira работает с ошибками через обратный прокси Nginx

0 голосов
/ 29 ноября 2018

Я пытаюсь запустить свой контейнер Jira, который проксируется Nginx с SSL.Docker и Nginx работают на одном хосте.Это работает, но очень медленно, и я вижу много ошибок 502 в моем браузере после 20 секунд ожидания запроса: 

Failed to load resource: the server responded with a status of 502 (Bad Gateway)
https://jira.domain.com/s/bd8634ced76dd5b58692efac9ae778a3-CDN/-fn7o3/712004/6411e0087192541a09d88223fb51a6a0/7.12.3/_/download/batch/com.atlassian.jira.jira-postsetup-announcements-plugin:post-setup-announcements/com.atlassian.jira.jira-postsetup-announcements-plugin:post-setup-announcements.css
Failed to load resource: the server responded with a status of 502 (Bad Gateway)
https://jira.domain.com/s/18b9a28a421d39b16f73e99fdde14965-CDN/-fn7o3/712004/6411e0087192541a09d88223fb51a6a0/7.12.3/_/download/batch/com.atlassian.jira.jira-postsetup-announcements-plugin:post-setup-announcements/com.atlassian.jira.jira-postsetup-announcements-plugin:post-setup-announcements.js?locale=en-US

Эта ошибка в Nginx: 

2018/11/29 16:57:35 [error] 26220#26220: *959 upstream prematurely closed connection while reading response header from upstream, client: 95.79.57.201, server: jira.domain.com, request: "GET /s/bd8634ced76dd5b58692efac9ae778a3-CDN/-fn7o3/712004/6411e0087192541a09d88223fb51a6a0/7.12.3/_/download/batch/com.atlassian.jira.jira-postsetup-announcements-plugin:post-setup-announcements/com.atlassian.jira.jira-postsetup-announcements-plugin:post-setup-announcements.css HTTP/1.1", upstream: "http://172.19.0.45:8090/s/bd8634ced76dd5b58692efac9ae778a3-CDN/-fn7o3/712004/6411e0087192541a09d88223fb51a6a0/7.12.3/_/download/batch/com.atlassian.jira.jira-postsetup-announcements-plugin:post-setup-announcements/com.atlassian.jira.jira-postsetup-announcements-plugin:post-setup-announcements.css", host: "jira.domain.com"

My Jira server.xml Connectorраздел: 

<Connector port="8090"
 connectionTimeout="20000"
 redirectPort="8443"
 relaxedPathChars="[]|"
 relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
 maxThreads="48"
 minSpareThreads="10"
 enableLookups="false"
 acceptCount="10"
 debug="0"
 URIEncoding="UTF-8"
 protocol="org.apache.coyote.http11.Http11NioProtocol"
 proxyName="jira.domain.com"
 proxyPort="443"
 secure="false"
 scheme="https"/>

И Nginx vhost config: 

upstream jira {
  server 172.19.0.45:8090;
}
server {
  listen       80;
  server_name  jira.domain.com;
  charset      utf-8;

  access_log  /var/log/nginx/jira.access.log main;
  error_log   /var/log/nginx/jira.error.log;
  log_subrequest on;

  location /robots.txt {
    alias /var/www/robots.txt;
  }

  return 301 https://$host$request_uri;
}

server {
  listen      443 ssl;
  server_name jira.domain.com;
  charset     utf-8;

  include  /etc/nginx/ssl/ssl.conf;

  access_log  /var/log/nginx/jira.ssl.access.log main;
  error_log   /var/log/nginx/jira.ssl.error.log;
  log_subrequest on;

  client_max_body_size 15M;

  location / {

    proxy_http_version 1.1;
    proxy_pass   http://jira;

    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;
    client_max_body_size 10M;
  }
  include rules/deny_dotted.conf;
}

Кто-нибудь знает, что можно добавить в конфигурацию Nginx или Jira для исправления этих ошибок?Спасибо.

...