Actioncable Nginx和Puma WebSocket握手:意外的响应

时间:2016-09-02 12:54:28

标签: ruby-on-rails ruby nginx puma actioncable

我正在尝试使用rails 5,Nginx和Puma配置服务器。应用程序运行正常,但Actioncable正在提供

.gitlab-ci.yml

以下是我的nginx设置,

WebSocket connection to 'ws://server_name.com/cable' failed:
Error during WebSocket handshake: Unexpected response code: 200

在production.rb的rails中,我进行了如下设置。

upstream app {
  server unix:/tmp/app.sock fail_timeout=0;
}

server {
    listen       80;
    server_name  server_name.com;
    try_files $uri/index.html $uri @app;
    client_max_body_size 100M;
    location @app {
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header Host $http_host;
      proxy_redirect off;
      proxy_pass http://app;
      client_max_body_size 10M;
    }

    location /cable {
       proxy_pass http://app/;
       proxy_http_version 1.1;
       proxy_set_header Upgrade $http_upgrade;
       proxy_set_header Connection "Upgrade";
    }

    location ~ ^/(assets|uploads)/ {
        root assets_path;
        gzip_static on;
        expires max;
        add_header Cache-Control public;
        add_header ETag "";
        break;
    }
    error_page   500 502 503 504  /500.html;
 }

任何帮助将不胜感激。

2 个答案:

答案 0 :(得分:2)

尝试添加:

config.action_cable.allowed_request_origins = ['*']
config.action_cable.disable_request_forgery_protection = true

到您的config/environments/production.rb文件

它适用于我,你也可以检查this link。 这个question

答案 1 :(得分:1)

尝试使用,

location /cable {
    proxy_pass http://app; # not http://app/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
}

如果你没有ssl,还要确保你的production.rb中有config.action_cable.allowed_request_origins = [/http:\/\/*/, /https:\/\/*/]