#1566 closed defect (worksforme)

Websockets not working for proxy_pass

Reported by: sanket.1985@… Owned by:
Priority: major Milestone:
Component: nginx-module Version: 1.13.x
Keywords: Cc:
uname -a: Linux pmdocker 4.13.0-43-generic #48-Ubuntu SMP Wed May 16 12:18:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.13.12

Description

I am trying to put Nginx in front of Zeppelin. For the same, have done configuration of Zeppelin for Nginx based on their documentation. While am trying to follow the steps, it seems that Websockets are not working with Zeppelin.

Reference guide followed is at: https://zeppelin.apache.org/docs/0.7.3/security/authentication.html

Configuration of default.conf file for Nginx is as below:

        location /zeppelin/ {
            proxy_pass http://104.211.216.218/;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header Host $http_host;
            proxy_set_header X-NginX-Proxy true;
            proxy_redirect off;
        }

        location /zeppelin/ws {
            proxy_pass http://104.211.216.218/ws;
            proxy_http_version 1.1;
            proxy_set_header Upgrade websocket;
            proxy_set_header Connection upgrade;
        }

Change History (2)

comment:1 Changed 18 months ago by mdounin

If you think this is a bug in nginx, please provide details on why do you think it is indeed bug in nginx, and not a bug in Zeppelin and/or misconfiguration in your setup. If you need help with configuring nginx, consider using support options available.

comment:2 Changed 17 months ago by mdounin

  • Resolution set to worksforme
  • Status changed from new to closed

Feedback timeout.

Note: See TracTickets for help on using tickets.