用于 Playframework Websockets 的 VHosts Nginx 配置

Posted 2023-02-16

【中文标题】用于 Playframework Websockets 的 VHosts Nginx 配置

【英文标题】：VHosts Nginx Config for Playframework Websockets

【发布时间】：2012-02-21 05:36:45

【问题描述】：

下面的配置似乎有效，但现在失败了。我按照article 下载并安装了 tcp_proxy_module。

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;


events 
    worker_connections  1024;



http 
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;

    #server 

    #


    # another virtual host using mix of IP-, name-, and port-based configuration

    server 
        listen       80;
       #listen       locahost:8080;
        server_name  localhost.in;

        location / 
            proxy_pass http://127.0.0.1:9000;
        proxy_set_header        Host            $host;
         
    

更新：

Nginx 错误日志：

2012/02/21 10:56:59 [error] 14745#0: *278 upstream timed out (60: Operation timed out) while reading upstream, client: 127.0.0.1, server: localhost.in, request: "GET /websocket/room/socket?roomNo=1&user=sameerFF HTTP/1.1", upstream: "http://127.0.0.1:9000/websocket/room/socket?roomNo=1&user=sameerFF", host: "test.localhost.in"
2012/02/21 10:56:59 [error] 14745#0: *257 upstream timed out (60: Operation timed out) while reading upstream, client: 127.0.0.1, server: localhost.in, request: "GET /websocket/room/socket?roomNo=1&user=sameerChrome HTTP/1.1", upstream: "http://127.0.0.1:9000/websocket/room/socket?roomNo=1&user=sameerChrome", host: "test.localhost.in"
2012/02/21 10:59:40 [error] 15366#0: *10 upstream timed out (60: Operation timed out) while reading upstream, client: 127.0.0.1, server: localhost.in, request: "GET /websocket/room/socket?roomNo=1&user=sameerFF HTTP/1.1", upstream: "http://127.0.0.1:9000/websocket/room/socket?roomNo=1&user=sameerFF", host: "test.localhost.in"

更新 2：

使用此配置，我在启动 nginx 时遇到绑定异常。如果我删除 tcp 设置，nginx 就会正常运行。对于常规的 http 请求和 WebSocket 请求，我需要端口 80 重定向到 9000

#user  nobody;
worker_processes  1;

error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;


events 
    worker_connections  1024;


tcp 
     upstream websockets 
      ## Play! location
       server 127.0.0.1:9000;
        

    server 
        listen 80;
        server_name localhost.in;

        tcp_nodelay on;
        proxy_pass websockets;
   



http 
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  logs/access.log  main;

    sendfile        on;
    #tcp_nopush     on;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;

    # another virtual host using mix of IP-, name-, and port-based configuration

    server 
        listen       80;
#listen       locahost:8080;
        server_name  localhost.in;

        location / 
            proxy_pass http://127.0.0.1:9000;
        proxy_set_header        Host            $host;
    
    

【问题讨论】：

它是怎么失败的？是否有来自 nginx 或日志文件的错误消息（在您重新启用错误日志之后，当然:)）？只是 Websockets 部分不起作用吗？

我为聊天示例添加了错误日志条目，它们看起来像 TimeOutExceptions。

【参考方案1】：

看起来只是 websockets 不工作。请再次阅读article you linked。您没有修改您的 nginx 配置。

根据那篇文章，您的示例配置可能如下所示（不过我还没有测试过）：

tcp 
    upstream websockets 
        ## Play! location
        server 127.0.0.1:9000;
       

    server 
        listen 80;
        server_name localhost.in;

        tcp_nodelay on;
        proxy_pass websockets;
    

【讨论】：

尝试了您的解决方案，但在开始时遇到绑定异常（请参阅我对问题的编辑）。非常感谢您的帮助！

当然你得到一个绑定异常，你试图绑定到端口 80 两次。尝试不使用整个 http... 部分。 tcp... 部分应该自动将所有内容（传统的 HTTP 请求和 Websocket 内容）路由到播放服务器。