NGINX-SSL握手中关闭连接，而SSL与上游握手

Question

堆栈:React，NGINX 1.14.0，GUnicorn，Django 2.2.8，Python 3.6.9

错误:

• 在浏览器：当React调用Django API（当然在请求头中有origin)时，大约30秒后在浏览器控制台出现CORS错误。
  在浏览器控制台：CORS策略阻止从源“https：//mydomain”访问“https://mydomain:8000/somethy/”处的XMLHttpRequest：请求的资源上没有“access-control-allog-origin”标头。
  此外，HTTP状态代码为502坏网关。
• 在NGINX：当SSL握手时SSL握手中的对等关闭连接，客户端:something，服务器:mydomain，请求：“Get/something/HTTP/1.1”，上游：“https://unix://home/Ubuntu/django_path/gunicorn.sock://Somethy/”，主机：“mydomain:8000”，引用者：“https://mydomain/something”。客户端在等待请求时超时（110：连接超时），客户端:something，服务器:0.0.0.0:443
• 在GUnicorn处:[关键]工作人员超时
• 在Django：我编写了要查看的日志，但日志没有打印出来。

Conf：

• Nginx:

server {
    listen 80;
    server_name mydomain;

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

server {
    listen 443 ssl;
    server_name mydomain;

    error_log /var/log/nginx/error.log debug;

    ssl_certificate /etc/letsencrypt/live/mydomain/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/mydomain/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    location / {
        root /home/ubuntu/react_path/build;
        index index.html index.htm;
        try_files $uri $uri/ /index.html;
    }
}

server {
    listen 8000 ssl;
    server_name mydomain;

    ssl_certificate /etc/letsencrypt/live/mydomain/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/mydomain/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    charset utf-8;

    location / {
        include proxy_params;
        proxy_pass https://unix:/home/ubuntu/django_path/gunicorn.sock;
    }

    location /static/ {
        alias /home/ubuntu/django_path/static/;
    }

    location /media/ {
        alias /home/ubuntu/django_path/media/;
    }
}

• Gunicorn:

[Unit]
Description=gunicorn daemon
After=network.target

[Service]
User=ubuntu
Group=www-data
WorkingDirectory=/home/ubuntu/django_path
ExecStart=/home/ubuntu/VENV/bin/gunicorn --workers 3 --bind unix:/home/ubuntu/django_path/gunicorn.sock api.wsgi:application

[Install]
WantedBy=multi-user.target

• Django:

CORS_ALLOWED_ORIGINS = [
    'https://mydomain',
]

有一些问题，但我认为CORS错误是因为交通无法到达Django，甚至Gunicorn。

所以也许我改变NGINX conf。你怎么看？我怎么能修好？

Answer 1

继续下去后，我找到了解决办法。

https://serverfault.com/questions/746297/how-to-run-gunicorn-upport-with-an-nginx-ssl-configuration
非常有帮助。

下面是Nginx的conf。

upstream gunicorn {
    server 127.0.0.1:8080;
}

server {
    listen 80;
    server_name mydomain;

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

server {
    listen 443 ssl;
    server_name mydomain;

    ...
}

server {
    listen 8000 ssl;
    server_name mydomain;

    ...

    location / {
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $host;
        proxy_pass http://gunicorn;
    }
    ...
}

下面是Gunicorn的conf。

...
ExecStart=/home/ubuntu/VENV/bin/gunicorn --workers 3 --bind 127.0.0.1:8080:/home/ubuntu/django_path/gunicorn.sock api.wsgi:application
...