Nginx websockets+SSL不起作用(NET::ERR_CERT_COMMON_NAME_INVALID）

Question

upstream websocket {
    server xx.xx.xx.xx:8080;
}

server {
    listen 80;
    listen [::]:80;
    server_name domain.com *.domain.com;
    return 301 https://$server_name$request_uri;
}

server {
    listen 443 ssl default_server;
    listen [::]:443 ssl default_server;
    ssl on;
    ssl_certificate /etc/letsencrypt/live/domain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/domain.com/privkey.pem;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 5m;

    root /var/www/html;

    index index.php index.html index.htm index.nginx-debian.html;

    server_name domain.com *.domain.com;

    location / {
        try_files $uri $uri/ =404;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
        fastcgi_pass unix:/run/php/php7.0-fpm.sock;
    }

    location ~ /\.ht {
        deny all;
    }

    location /ws {
            proxy_pass http://websocket;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_set_header Host $host;
    }

}

（索引）：2到“wss://xx.xx.xx.xx.xx/ws:8080”的WebSocket连接失败：连接建立错误:NET::err_cert_common_name_invalid

我想这与证书(SSL)有关，但我真的不知道如何解决这个问题！

提前感谢！

<script>
    var conn = new WebSocket('wss://xx.xx.xx.xx/ws');
    conn.onopen = function(e) {
    console.log("Connection established!");
};
</script>

当我将xx.xx.xx.xx更改为domain.com时，我会得到一个握手错误代码504。

顺便说一句，我正在通过php（php server.php）使用ratchet运行一个websocket服务器，下面的示例如下：http://socketo.me/docs/hello-world

Answer 1

为上游Nginx配置SSL

先决条件

1. NGINX Plus R6及更高版本或最新的NGINX开源，使用--with-stream和with-stream_ssl_module配置参数编译
2. 代理TCP服务器或TCP服务器的上游组
3. SSL证书和私钥

stream {
        upstream websocket {
             server backend1.example.com:8080;

    }

    server {
        listen                8080 ssl;
        proxy_pass            websocket;

        ssl_certificate       /etc/ssl/certs/server.crt;
        ssl_certificate_key   /etc/ssl/certs/server.key;
        ssl_protocols         SSLv3 TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers           HIGH:!aNULL:!MD5;
        ssl_session_cache     shared:SSL:20m;
        ssl_session_timeout   4h;
        ssl_handshake_timeout 30s;
    …
     }
}