使用SSL与Gunicorn / Django / Nginx应用程序时出现混合内容错误

Question

我正在尝试为Superdesk的实例配置HTTPS，它使用Gunicorn和Nginx进行路由。我安装了证书并且（我认为）在服务器上工作。然而，将浏览器指向应用程序会在Firefox上“阻止加载混合活动内容”http://localhost/api，并且“ws：// localhost / ws”的WebSocket连接失败：Chrome上的连接建立错误：net :: ERR_CONNECTION_REFUSED“。这个应用程序的文档几乎不存在，我现在花了无数个小时试图让它工作。我在GitHub上向开发者提交了一个issue，但我的回答并不是很幸运。这是我的Nginx配置：

server {
    listen 80;
    listen 443 ssl;

    server_name my_server_name;
    ssl on;
    ssl_certificate /path/to/my/cert.pem;
    ssl_certificate_key /path/to/my/key/key.pem;

    location /ws {
        proxy_pass http://localhost:5100;
        proxy_http_version 1.1;
        proxy_buffering off;
        proxy_read_timeout 3600;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
     }  
    location /api {
        proxy_pass http://localhost:5000;
        proxy_set_header Host localhost;
        expires epoch;

        sub_filter_once off;
        sub_filter_types application/json;
        sub_filter 'http://localhost' 'http://$host';
    }  
    location /contentapi {
        proxy_pass http://localhost:5400;
        proxy_set_header Host localhost;
        expires epoch;
    }  
    location /.well-known {
        root /var/tmp;
    }
    location / {
        root /opt/superdesk/client/dist;

        # TODO: use "config.js:server" for user installations
        sub_filter_once off;
        sub_filter_types application/javascript;
        sub_filter 'http://localhost' 'http://$host';
        sub_filter 'ws://localhost/ws' 'ws://$host/ws';
    }
    location /mail {
        alias /var/log/superdesk/mail/;
        default_type text/plain;
        autoindex on;
        autoindex_exact_size off;
    }
}

这是我第一次使用nginx / gunicorn / django app而且我完全迷失了。有人能指出我正确的方向吗？

Answer 1

对于任何试图设置Superdesk并遇到相同问题的人，我终于找到了正确的配置。

首先，这是我必须处理HTTPS请求并将HTTP请求重定向到HTTPS的Nginx配置：

server {
    listen                      443 ssl http2;
    listen                      [::]:443 ssl http2;
    server_name                 my.domain.com;

    ssl on;
    ssl_certificate             /path/to/my/cert.pem;
    ssl_certificate_key         /path/to/my/key.pem;
    ssl_protocols               TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;

    location /ws {
    proxy_pass http://localhost:5100;
    proxy_http_version 1.1;
    proxy_buffering off;
    proxy_read_timeout 3600;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
}

location /api {
    proxy_pass http://localhost:5000;
    proxy_set_header Host my.domain.com;
    expires epoch;

    sub_filter_once off;
    sub_filter_types application/json;
    sub_filter 'http://localhost' 'https://$host';
}

location /contentapi {
    proxy_pass http://localhost:5400;
    proxy_set_header Host my.domain.com;
    expires epoch;
}

location /.well-known {
    root /var/tmp;
}
location / {
    root /opt/superdesk/client/dist;

    # TODO: use "config.js:server" for user installations
    sub_filter_once off;
    sub_filter_types application/javascript;
    sub_filter 'http://localhost' 'https://$host';
    sub_filter 'ws://localhost/ws' 'wss://$host/ws';
}
location /mail {
    alias /var/log/superdesk/mail/;
    default_type text/plain;
    autoindex on;
    autoindex_exact_size off;
}

}

server {
    listen                      80;
    listen                      [::]:80;
    server_name                 my.domain.com;
    return                      301 https://$host$request_uri;
}

我在配置中遗漏了什么：

proxy_set_header字段必须设置为proxy_set_header Host <my_domain name>，而在sub_filter字段中，它只是必须设置为使用HTTPS的第二个参数

特定于Superdesk的东西必须配置：

在/opt/superdesk/activate.sh中，将HOST_SSL设置为HOST_SSL=${HOST_SSL:-s}。这将确保通过邮件发送的链接（如密码休息电子邮件）以HTTPS形式发送。

回想起来似乎很简单但是很难弄清楚Nginx知识有限......