Sung Shim,

I wasn't sure what  http://backend and http://backendWS should refer to so I 
defined both as upstream to localhost:8080

Also when I defined the following:

    proxy_set_header X-Real-IP       $proxy_protocol_addr;
    proxy_set_header X-Forwarded-For $proxy_protocol_addr;


Nginx complained that it doesn't know the variable proxy_protocol_addr so I 
omitted these lines.

So now I have the attached nginx config but it doesn't seem to help – Zeppelin 
is still disconnected

Thanks for your help,

Oren




From: astros...@gmail.com [mailto:astros...@gmail.com] On Behalf Of Hyung Sung 
Shim
Sent: Monday, April 4, 2016 2:03 PM
To: users@zeppelin.incubator.apache.org
Subject: Re: Zeppelin 0.5.6 Disconnected

Hello.
Since 0.5.5, Zeppelin uses single port for REST and websocket.
so Could you try to use same port like follow Nginx configuration?

server {
  listen 80 ;
  server_name _;

  location / {
    proxy_set_header Host            $host;
    proxy_set_header X-Real-IP       $proxy_protocol_addr;
    proxy_set_header X-Forwarded-For $proxy_protocol_addr;

    proxy_pass  http://backend<http://backend/>;
  }

  location /ws {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

    proxy_set_header   X-Real-IP $remote_addr;
    proxy_pass  http://backendWS<http://backendws/>;
  }
}

I am fixing the documentation.
Thanks.


2016-04-04 17:24 GMT+09:00 Oren Shani 
<osh...@iucc.ac.il<mailto:osh...@iucc.ac.il>>:
Hello,

I installed Zeppelin 0.5.6 on Ubuntu server 14.04, behind Nginx. Zeppelin comes 
up but shows "Disconnected" in the top right corner.

I found several references to a similar problem on the web and most of them  
suggest that the problem has to do with access to Zeppelin's winsock port 
(8081).

The thing is that Zeppelin on my server does not listen on 8081 but only on 
8080. Also I ran pcap on both the server side and my PC's side and never saw an 
attempt to access port 8081 .

So could it be something else? Maybe I am missing something in my config files?

You can see my zeppelin-site.xml and the relevant lines from my nginx config 
files attached.

Many thanks,

Oren



# Zeppelin

upstream zeppelin {
    server localhost:8080;
}

upstream zeppelin-wss {
    server localhost:8080;
}

    server {
        listen 48080;

        server_name zep.iucc.ac.il;

        auth_basic "Restricted Access";
        auth_basic_user_file /etc/nginx/htpasswd.users;

        ssl on;
        ssl_session_timeout 5m;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_ciphers 
'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH:EECDH+AESGCM:EDH+AESGCM:ECDHE-RSA-AES128-GCM-SHA256:AES256+EECDH:DHE-RSA-AES128-GCM-SHA256:AES256+EDH:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4';

        ssl_prefer_server_ciphers on;
        ssl_session_cache shared:SSL:10m;

        ssl_certificate /etc/nginx/ssl/elk_iucc_ac_il.crt;
        ssl_certificate_key /etc/nginx/ssl/elk_iucc_ac_il.key;
        ssl_dhparam /etc/nginx/ssl/dhparam.pem;

        location /{
                proxy_pass https://zeppelin;
                proxy_set_header Host            $host;
                proxy_redirect off;
                }

        location /ws {
                proxy_pass https://zeppelin-wss;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
                proxy_set_header   X-Real-IP $remote_addr;
                }
    }

Reply via email to