Nginx反向代理Odoo导出长耗时报表报upstream prematurely closed错误求助

场景说明 #

场景1：运行正常 #

我在Debian 10系统服务器上部署了Odoo，同服务器部署Nginx作为反向代理，所有功能运行正常。

对应Nginx配置：

location / {
    proxy_redirect off;
    proxy_pass http://127.0.0.1:8069;
}

场景2：出现故障 #

我使用另一台Debian 10服务器单独部署Nginx，配置和场景1完全一致，仅修改了上游服务的IP地址。

对应Nginx配置：

location / {
    proxy_redirect off;
    proxy_pass http://PUBLIC_IP_FROM_SERVER_OF_SCENARIO_1:8069;
}

部署后Odoo的登录、导航、创建记录、筛选、分组等常规功能均正常，但导出需要10秒及以上生成时间的报表时，就会报错upstream prematurely closed connection while reading upstream。

已尝试的解决方案 #

我查阅了大量论坛内容，单独测试了所有常见的Nginx配置调整方案，均未解决问题，测试过的配置如下：

proxy_request_buffering off;
proxy_buffering off;

proxy_busy_buffers_size 2048k;
proxy_temp_file_write_size 2048k;

proxy_buffer_size 1024k;
proxy_buffers 16 1024k;

完整Nginx配置 #

server {
 listen 443 ssl;

 server_name dbname.domain.com;

 proxy_read_timeout 1440s;
 proxy_connect_timeout 75s;
 proxy_send_timeout 75s;
 client_max_body_size 100M;

 # Add Headers for odoo proxy mode
 proxy_set_header Host $host;
 proxy_set_header X-Forwarded-Host $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;

 # SSL parameters - update with your cert details
 ssl on;
 ssl_certificate /etc/letsencrypt/live/domain.com/fullchain.pem; # managed by Certbot
 ssl_certificate_key /etc/letsencrypt/live/domain.com/privkey.pem; # managed by Certbot

 ssl_session_timeout 30m;
 ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
 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';
 ssl_prefer_server_ciphers on;

 # Redirect requests to odoo backend server
 location /longpolling {
     proxy_pass http://PUBLIC_IP_FROM_SERVER_OF_SCENARIO_1:8072;
 }

 location / {
   proxy_redirect off;
   proxy_pass http://PUBLIC_IP_FROM_SERVER_OF_SCENARIO_1:8069;
 }
 gzip_types text/css text/less text/plain text/xml application/xml application/json 
 application/javascript;
 gzip on;
}

补充说明 #

测试环境使用HTTP协议，生产环境使用加密VPN，两种环境下均出现相同问题。

内容的提问来源于stack exchange，提问作者Eric Hernandez