Thin + Nginx + Websockets配置| Rails

我有一個Ruby on Rails 3.2應用程序，帶有websocket-rails gem，運行在nginx反向代理後面的瘦webserver中。Thin + Nginx + Websockets配置| Rails

除了nginx反向代理，一切正常。通過去除nginx反向代理，websocket通信工作得很好。（包括開發和生產）。使用nginx作爲websockets的反向代理是問題開始的地方。

Nginx 版本1.3.13以上應該能夠支持websocket代理。基於該文檔here和here我創建了以下nginx的配置：

map $http_upgrade $connection_upgrade { 
    default upgrade; 
    ''  close; 
} 

upstream ravecy { 
    server localhost:3000; 
    server localhost:3001; 
} 

server { 
    listen 80; 
    server_name test.ravecy.com; 

    root /var/www/ravecy.com/public; 

    location/{ 
    try_files $uri @ravecy; 
    } 

    location @ravecy { 
    proxy_pass http://ravecy; 
    proxy_http_version 1.1; 
    proxy_set_header Upgrade $http_upgrade; 
    proxy_set_header Connection $connection_upgrade; 
    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_redirect off; 
    } 
}

但不幸的是，這是行不通的。我完全不知道爲什麼，但在我看來，nginx的不處理我的WebSocket連接嘗試的WebSocket連接，但常規HTTP連接，從日誌中看到：

==> production.log <== 
Started GET "/chat" for 82.170.121.62 at 2013-04-10 12:20:12 +0200 
Processing by ApplicationController#chat as HTML 
    Rendered application/chat.html.erb within layouts/frontend (0.2ms) 
    Rendered layouts/frontend/_navbar.html.erb (6.3ms) 
    Rendered layouts/shared/_alert.html.erb (0.0ms) 
    Rendered layouts/frontend/_facebook_sdk.html.erb (0.0ms) 
Completed 200 OK in 9ms (Views: 8.4ms | ActiveRecord: 0.4ms) 
Started GET "/websocket" for 82.170.121.62 at 2013-04-10 12:20:12 +0200 

==> websocket_rails.log <== 
I [2013-04-10 12:20:12.744] [ConnectionManager] Connection opened: #<Connnection::47398780> 

I [2013-04-10 12:20:12.745] [Dispatcher] Started Event: client_connected 
I [2013-04-10 12:20:12.745] [Dispatcher] Name: client_connected 
I [2013-04-10 12:20:12.745] [Dispatcher] Data: {"connection_id"=>47398780} 
I [2013-04-10 12:20:12.745] [Dispatcher] Connection: #<Connnection::47398780> 

I [2013-04-10 12:20:12.747] [Dispatcher] Event client_connected Finished in 0.001960819 seconds 


==> /var/log/nginx/access.log <== 
82.170.121.62 - - [10/Apr/2013:12:20:12 +0200] "GET /chat HTTP/1.1" 200 854 "http://test.ravecy.com/posts" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17" 
82.170.121.62 - - [10/Apr/2013:12:20:12 +0200] "GET /assets/frontend-6ad91089203a6026624ce015c2800492.css HTTP/1.1" 304 0 "http://test.ravecy.com/chat" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17" 
82.170.121.62 - - [10/Apr/2013:12:20:12 +0200] "GET /assets/frontend-98fa493fc9f482c0d44b31bda5a89135.js HTTP/1.1" 304 0 "http://test.ravecy.com/chat" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/536.26.17 (KHTML, like Gecko) Version/6.0.2 Safari/536.26.17" 

==> websocket_rails.log <== 
I [2013-04-10 12:20:12.832] [ConnectionManager] Connection closed: #<Connnection::47398780> 

I [2013-04-10 12:20:12.832] [Dispatcher] Started Event: client_disconnected 
I [2013-04-10 12:20:12.832] [Dispatcher] Name: client_disconnected 
I [2013-04-10 12:20:12.832] [Dispatcher] Data: nil 
I [2013-04-10 12:20:12.832] [Dispatcher] Connection: #<Connnection::47398780> 

I [2013-04-10 12:20:12.833] [Dispatcher] Event client_disconnected Finished in 0.000293462 seconds 


==> /var/log/nginx/access.log <== 
82.170.121.62 - - [10/Apr/2013:12:20:12 +0200] "GET /websocket HTTP/1.1" 200 398 "-" "-"

注意，連接被關閉在100ms內，即使它應該保持活着。

此外CONFIGS： nginx.conf：

user www-data; 
worker_processes 4; 
pid /run/nginx.pid; 

events { 
    worker_connections 768; 
} 

http { 
    sendfile on; 
    tcp_nopush on; 
    tcp_nodelay on; 
    keepalive_timeout 65; 
    types_hash_max_size 2048; 

    include /etc/nginx/mime.types; 
    default_type application/octet-stream; 

    access_log /var/log/nginx/access.log; 
    error_log /var/log/nginx/error.log; 

    gzip on; 
    gzip_disable "msie6"; 

    include /etc/nginx/conf.d/*.conf; 
    include /etc/nginx/sites-enabled/*; 
}

薄配置：

--- 
chdir: /var/www/ravecy.com 
environment: production 
address: 127.0.0.1 
port: 3000 
timeout: 30 
log: log/thin.log 
pid: tmp/pids/thin.pid 
max_conns: 1024 
max_persistent_conns: 100 
require: [] 
wait: 30 
servers: 2 
daemonize: true

nginx的版本： nginx的/ 1.3.15 URL住例如： http://test.ravecy.com/chat

另請注意：在JS控制檯中執行new WebSocket("ws://test.ravecy.com/websocket")時，爲瀏覽器提示「Unexpected response code：200」。

我非常渴望做這個工作，不再知道我應該做什麼。

的Telnet導致NGINX：

的Telnet導致直接到薄：

GET /websocket HTTP/1.1 
Host: test.ravecy.com 
Connection: Upgrade 
Upgrade: WebSocket 

HTTP/1.1 101 Web Socket Protocol Handshake 
Upgrade: WebSocket 
Connection: Upgrade 
WebSocket-Origin: 
WebSocket-Location: ws://test.ravecy.com/websocket 

[["client_connected",{"id":null,"channel":null,"data":{"connection_id":37489460},"success":null,"result":null,"server_token":null}]][["users",{"id":null,"channel":null,"data":[],"success":null,"result":null,"server_token":null}]][["client_connected",{"id":null,"channel":null,"data":{},"success":false,"result":null,"server_token":null}]]

顯然，這是人的東西出了問題。但爲什麼？

來源

2013-04-13 Toby Hinloopen

似乎它的固定在HTTP：//test.ravecy .COM /聊天。原因是什麼？ –

基於telnet結果，我注意到我使用了「升級」的大寫「U」。使用「升級」，而不是「升級」修復了我所有的問題...

來源

2013-04-14 09:54:32

thx！你的意思是在Nginx的配置？你在哪裏改變了'U'？ – unludo

'map $ http_upgrade $ connection_upgrade { 默認升級; ''close; }' –

非常感謝你！你今天節省我的大腦。 omg什麼瘋狂的東西..在我的情況下，正確的位置配置看起來像這樣 'proxy_http_version 1.1;' 'proxy_set_header升級$ http_upgrade;' 'proxy_set_header連接「升級」;' –

是的。該連接用於HTTP在次WS升級語法區分大小寫

所以完整的服務器配置是這樣的：

server { 
listen 80; 
server_name server.com; 

root /var/www/my-app/current/public; 

try_files $uri/index.html $uri @app; 

location @app { 
    proxy_pass http://app; 
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
    proxy_set_header Host $http_host; 
    proxy_redirect off; 
} 

# enables WS support 
location /websocket { 
    proxy_pass http://app; 
    proxy_http_version 1.1; 
    proxy_set_header Upgrade $http_upgrade; 
    proxy_set_header Connection "Upgrade"; 
} 

error_page 500 502 503 504 /500.html; 
client_max_body_size 4G; 
keepalive_timeout 10;

}

來源

2017-02-25 10:40:00 Sachin

Thin + Nginx + Websockets配置| Rails

回答

相關問題