0

我正在尝试为Superdesk的实例配置 HTTPS，该实例使用 Gunicorn 和 Nginx 进行路由。我安装了证书并且（我认为）在服务器上工作。然而，将浏览器指向应用程序会在 Firefox 和“WebSocket 连接到'ws://localhost/ws' 失败：Chrome 上的连接建立错误：net::ERR_CONNECTION_REFUSED"。这个应用程序的文档几乎不存在，我现在花了无数个小时试图让它工作。我在 GitHub 上向开发人员提交了一个问题，但我没有得到太多的答案。这是我的 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 应用程序，我完全迷失了。有人能指出我正确的方向吗？

4

1 回答 1

0

对于任何尝试设置 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 的了解有限，很难弄清楚......

于 2019-03-06T18:17:49.460 回答