Hello, In a Kubernetes cluster, I have an Nginx server acting like a reverse proxy / TLS termination solution that proxypass requests to a backend Tomcat application that has some functionalities powered by Web Sockets (SockJS / Stomp). Unfortunately, the Web Sockets handshake never completes successfully.
On the Client side, in my browser, I can see the following messages in the console: ``` Opening Web Socket... websockets-0.1.min.js:116 Whoops! Lost connection to https://myhost/stomp ``` Followed by a HTTP 504 Gateway Timeout websockets-0.1.min.js:72 WebSocket connection to 'wss://myhost/stomp/673/ugvpxc1lwmfjnung/websocket' failed: Error during WebSocket handshake: Unexpected response code: 504 -- On the tomcat side I have the following entry in the access log: 0:0:0:0:0:0:0:1,2017-06-01 16:53:36.915 +0000,4,GET,HTTP/1.1,"/stomp/673/ugvpxc1lwmfjnung/websocket",101,-,O,-,blablablabla,-,-,"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36",-,,-,-,-,-,-,- Whereas, on the nginx access log I have the corresponding: 10.2.89.0 - - [01/Jun/2017:16:54:41 +0000] "GET /stomp/673/ugvpxc1lwmfjnung/websocket HTTP/1.1" 499 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36" "24.5.136.13" Now, according to what I've researched, the 499 code is presented when the client closes the connection, but I can't figure out why it would take so long for the response to return to the client. According to the timestamps from these two entries, these two events are separated by ~1 minute. What's going on here? Here a snippet from my nginx.conf, any assistance at this point is deeply appreciated: server { listen 9965 default_server ssl; listen [::]:9965 default_server ssl; resolver 127.0.0.1; server_name _; ssl_certificate /etc/ssl/certs/certificate.pem; ssl_certificate_key /etc/ssl/certs/key.pem; ssl_dhparam /etc/ssl/certs/dhparam.pem; client_max_body_size 2000M; location / { proxy_read_timeout 900; proxy_pass_header Server; proxy_http_version 1.1; proxy_set_header Host $host; #proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Upgrade 'websocket'; proxy_set_header Connection "upgrade"; proxy_pass http://localhost:15010; } -- Any ideas to troubleshoot this further? Kindest regards, -- Marcelo Posted at Nginx Forum: https://forum.nginx.org/read.php?2,274580,274580#msg-274580 _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
