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;
}
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>:
> 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
>
>
>
>
>
