【问题标题】:How to connect websocket after set up with NGINX and Supervisor?设置好 NGINX 和 Supervisor 后如何连接 websocket?
【发布时间】:2020-07-09 18:58:26
【问题描述】:

我在我的 wsgi 应用程序旁边创建了一个 Django 频道。如果我运行,一切正常:

daphne -b 0.0.0.0 -p 8001 myapp.asgi:application 

我可以连接到 websocekt,但是在使用 nginx 创建主管后,我无法连接,而且我没有看到任何可以解决问题的有用日志。

当我检查主管状态时,它没有错误:

asgi:asgi0                       RUNNING   pid 23981, uptime 0:10:22
asgi:asgi1                       RUNNING   pid 23980, uptime 0:10:22
asgi:asgi2                       RUNNING   pid 23983, uptime 0:10:22
asgi:asgi3                       RUNNING   pid 23982, uptime 0:10:22

套接字最初是 localhost:8001,我也允许 UFW 使用该端口,但它不起作用,所以我更改为我的服务器 IP。

主管

[fcgi-program:asgi]
# TCP socket used by Nginx backend upstream
socket=tcp://139.162.172.87:8001

# Directory where your site's project files are located
directory=/home/markkiraly/crumb_backend

# Each process needs to have a separate socket file, so we use process_num
# Make sure to update "mysite.asgi" to match your project name
command=/home/markkiraly/crumb_backend/venv/bin/daphne --fd 0 --access-log - --proxy-headers crumb_backend.asgi:application
# Number of processes to startup, roughly the number of CPUs you have
numprocs=4

# Give each process a unique name so they can be told apart
process_name=asgi%(process_num)d

# Automatically start and recover processes
autostart=true
autorestart=true

# Choose where you want your log to go
stdout_logfile=/var/log/asgi.log
redirect_stderr=true

NGINX 配置

upstream channels-backend {
    server 139.162.172.87:8001;
}

server {
    listen 80;
    server_name crumbliterature.com www.crumbliterature.com;
    location /static/ {
        root /home/markkiraly/crumb_backend/;
    }

    location /media/ {
        root /home/markkiraly/crumb_backend/;
    }

     location / {
        include proxy_params;
        proxy_pass http://unix:/run/gunicorn.sock;
    }

     location /ws/ {
        try_files $uri @proxy_to_app;
    }

    location @proxy_to_app {
        proxy_pass http://channels-backend;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        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_set_header X-Forwarded-Host $server_name;
    }

}

我尝试了所有可能的方式:

ws://139.162.172.87/ws/chat/1/
ws://139.162.172.87:8001/ws/chat/1/
ws://crumbliterature.com/ws/chat/1/
ws://crumbliterature.com:8001/ws/chat/1/

【问题讨论】:

    标签: django sockets websocket django-channels channels


    【解决方案1】:

    1)

    如果 NGINX 和 Django Channel 位于一台机器上,那么你可以替换

    upstream channels-backend {
        server 139.162.172.87:8001;
    }
    

    upstream channels-backend {
        server localhost:8001;
    }
    

    2)

    我不了解 Django Channels,但如果默认或选定的端口被另一个应用程序阻止,某些应用程序可以尝试不同的端口。可能是您的应用程序可以工作但使用另一个端口或卡住但不通知它。尝试检查哪个应用程序在 8001 上监听(如果有监听)

    【讨论】:

      猜你喜欢
      • 2012-05-29
      • 2012-07-30
      • 1970-01-01
      • 1970-01-01
      • 2018-10-12
      • 2016-10-17
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多