Question

我在Flask网络应用程序中建立websocket时遇到了麻烦。

在客户端，我正在发出一个＆＃34; ping＆＃34; websocket事件每秒都发送到服务器。在浏览器控制台中，我每秒都会看到以下错误

POST https://example.com/socket.io/?EIO=3&transport=polling&t=LOkVYzQ&sid=88b5202cf38f40879ddfc6ce36322233 400 (BAD REQUEST)

GET https://example.com/socket.io/?EIO=3&transport=polling&t=LOkVZLN&sid=5a355bbccb6f4f05bd46379066876955 400 (BAD REQUEST)

WebSocket connection to 'wss://example.com/socket.io/?EIO=3&transport=websocket&sid=5a355bbccb6f4f05bd46379066876955' failed: WebSocket is closed before the connection is established.

我有以下nginx.conf

server {
    listen 80;
    server_name example.com www.example.com;
    return 301 https://$server_name$request_uri;
}

upstream app_server {

    # for UNIX domain socket setups
    server unix:/pathtowebapp/gunicorn.sock fail_timeout=0;

}

server {

    listen 443 ssl;

    server_name example.com www.example.com;

    keepalive_timeout 5;

    ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem;

    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers on;
    ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';

    charset     utf-8;
    client_max_body_size 30M;

    location / {
        try_files $uri @proxy_to_app;
    }

    location /socket.io {
      proxy_pass http://app_server;
      proxy_redirect off;

      proxy_set_header Host $host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Upgrade websocket;
      proxy_set_header Connection "upgrade";
      proxy_read_timeout 86400;
      proxy_buffering off;
      proxy_headers_hash_max_size 1024;

    }


    location /static {
        alias /pathtowebapp/webapp/static;
    }

    location @proxy_to_app {
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

        # enable this if and only if you use HTTPS
        proxy_set_header X-Forwarded-Proto https;

        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_set_header Host $http_host;

        # we don't want nginx trying to do something clever with
        # redirects, we set the Host: header above already.
        proxy_redirect off;
        #proxy_buffering off;
        proxy_pass http://app_server;

    }

}

我一直在寻找在gunicorn前使用nginx使用https的websocket的例子。

虽然websocket连接不成功，但我的网页已加载。

使用以下javascript建立客户端websocket：

var socket = io.connect('https://' + document.domain + ':' + location.port + namespace);

这是我的gunicorn.conf

import multiprocessing

bind = 'unix:/pathtowebapp/gunicorn.sock'
workers = multiprocessing.cpu_count() * 2 + 1
worker_class = 'eventlet'

[编辑] 如果我按照Flask-IO documentation中的方式配置nginx，只需运行(env)$ python deploy_app.py即可。但我的印象是，这不像我之前提到的设置那样生产理想

Answer 1

问题是你在gunicorn上运行多个工人。这不是当前支持的配置，因为gunicorn中的负载均衡器非常有限，不支持粘性会话。文档参考：https://flask-socketio.readthedocs.io/en/latest/#gunicorn-web-server。

相反，运行几个gunicorn实例，每个实例有一个worker，然后使用ip_hash方法设置nginx进行负载平衡，以便会话粘滞。

此外，如果您不知道，如果您运行多个服务器，您还需要运行一个消息队列，以便进程可以协调。这也在上面的文档链接中介绍。

由nginx代表的websockets通过https代表gunic给400（不良请求）

1 个答案: