After configuring the reverse proxy, events are dispatched but no response occurs.

[kjxbyz]

After configuring the reverse proxy, the hello2 event is dispatched, but there is no response.

server {
    listen 80;
    server_name dev.chenyifaer.com;

    return 301 https://dev.chenyifaer.com$request_uri;
}

server {
    listen 443 ssl http2;
    server_name dev.chenyifaer.com;
    charset     utf-8;

    ssl_certificate     /certs/dev.chenyifaer.com.pem;
    ssl_certificate_key /certs/dev.chenyifaer.com.key;
    ssl_session_timeout  5m;
    ssl_verify_client off;
    ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
    ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE:ECDH:AES:HIGH:!NULL:!aNULL:!MD5:!ADH:!RC4:!DH:!DHE;
    ssl_prefer_server_ciphers  on;

    add_header Access-Control-Allow-Origin *;

    location ^~ /homing-pigeon/ws {
        proxy_pass         https://dev.external.homing-pigeon.chenyifaer.com/ws;
        proxy_set_header   Host                 dev.external.homing-pigeon.chenyifaer.com;
        proxy_set_header   X-Real-IP            $remote_addr;
        proxy_set_header   X-Forwarded-For      $proxy_add_x_forwarded_for;
        proxy_redirect off;
        proxy_buffering off;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_cache_bypass $http_upgrade;
    }

    location ^~ /socket.io/ {
        set $cors_origin "";
        if ($http_origin ~* "^http://127.0.0.1$") {
            set $cors_origin $http_origin;
        }
        if ($http_origin ~* "^http://localhost$") {
            set $cors_origin $http_origin;
        }
        if ($http_origin ~* "^https://dev.chenyifaer.com$") {
            set $cors_origin $http_origin;
        }
        if ($http_origin ~* "^https://www.chenyifaer.com$") {
            set $cors_origin $http_origin;
        }
        add_header Access-Control-Allow-Origin $cors_origin;
        add_header Access-Control-Allow-Methods 'GET, POST, PATCH, PUT, DELETE';
        add_header Access-Control-Allow-Headers '*';
        add_header Access-Control-Allow-Credentials 'true';

        proxy_pass         https://dev.external.homing-pigeon.chenyifaer.com/socket.io/;
        proxy_set_header   Host                 dev.external.homing-pigeon.chenyifaer.com;
        proxy_set_header   X-Real-IP            $remote_addr;
        proxy_set_header   X-Forwarded-For      $proxy_add_x_forwarded_for;
        proxy_set_header   X-Forwarded-Proto    $scheme;
        proxy_set_header   X-Forwarded-Host     dev.chenyifaer.com;
        proxy_set_header   X-Forwarded-Port     $server_port;
        proxy_set_header   X-NginX-Proxy        true;
        proxy_redirect off;

        proxy_buffers 8 32k;
        proxy_buffer_size 64k;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_cache_bypass $http_upgrade;
        proxy_ssl_server_name on;
    }

}

[darrachequesne]

Hi! Could you please explain what you are trying to achieve? Why do you have two distinct locations in your nginx configuration? Is /homing-pigeon/ws pointing towards your Socket.IO server?

References:

• https://socket.io/docs/v4/reverse-proxy/#nginx
• https://socket.io/docs/v4/troubleshooting-connection-issues/

[kjxbyz]

local development environment:

When accessing the following two URLs, the results returned are actually different. Do not you know why?

curl "http://127.0.0.1:3001/ws/?EIO=4&transport=polling"

curl "http://localhost:3001/ws/?EIO=4&transport=polling"

[darrachequesne]

I think you are mixing the "namespace" and the "path" concepts here.

The "path" indicates the path of the HTTP request, by default it's /socket.io/.

If you want to catch requests on http://.../ws/, you will need to set the path to /ws/.

Reference: https://socket.io/docs/v4/server-options/#path

The "namespace", on the other hand, is the name of the Socket.IO namespace, which is not found in the request path, but in the Socket.IO packets.

Reference: https://socket.io/docs/v4/namespaces/

[kjxbyz]

If you remove the namespace, use the default configuration, and set path to /ws/, then an error will be reported when accessing http://127.0.0.1:3001/ws/ in postman. You must access http://127.0.0.1:3001 and set Handshake path to /ws for normal access.

[kjxbyz]

What makes people confused is that when the socket event is triggered in postman, there is no response. However, I used the socket_io_client library in flutter and found that the response can be received normally.

[darrachequesne]

@kjxbyz Thanks for the update 👍 we should definitely add a how-to guide with Postman.