Re: Difficult paths for Zeppelin and Nginx integration

[Sanket Shah]

Thanks Sam and Fabien for sharing the snippets. Fabien's solution didn't 
worked, but Sam's solution got me success.


location /zeppelin/ {
proxy_pass http://10.0.1.1:8080/;
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://10.0.1.1:8080/ws;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
proxy_http_version 1.1;
proxy_set_header Upgrade websocket;
proxy_set_header Connection upgrade;
proxy_read_timeout 5s;
proxy_connect_timeout 5s;
proxy_redirect off;
}



One more thing worth while noting is - if I pass public IP address of Zeppelin, 
it fails; but if private IP is passed, it works. This is specifically observed 
on Azure VM and AWS EC2 instances.


Sanket Tarun Shah - Enterprise Architect
+91 98793 56075 |  sanket.s...@outlook.com
(LinkedIn)

From: Sam Nicholson 
Sent: 05 June 2018 04:53 AM
To: users@zeppelin.apache.org
Subject: Re: Difficult paths for Zeppelin and Nginx integration


Here's the zeppelin from my currently, working, config
I have changed my DNS domains to "internal" and "external"
Other than that, it's really verbatim.

server {
listen 443 ssl http2;
server_name  zeppelin.external;
ssl_certificate /etc/certs/fullchain.cer;
ssl_certificate_key /etc/certs/cert.key;
location / {
proxy_pass   http://zeppelin.internal:6800;
proxy_set_header Host$host;
proxy_set_header X-Real-IP   $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
}
location /ws {
proxy_pass   http://zeppelin.internal:6800;
proxy_set_header Host$host;
proxy_set_header X-Real-IP   $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
proxy_http_version 1.1;
proxy_set_header Upgrade websocket;
proxy_set_header Connection upgrade;
proxy_read_timeout 86400;
}
}


On Mon, Jun 4, 2018 at 12:58 PM, Sanket Shah 
mailto:sanket.s...@outlook.com>> wrote:
Am trying to put Nginx in front of Zeppelin. Regular requests are passing 
through, but Websockets are not working. Followed this based on guide of 
Zeppelin - https://zeppelin.apache.org/docs/0.7.3/security/authentication.html. 
Seems having a real tough luck to get this going as scratching head and pulling 
hairs 😞
Apache Zeppelin 0.7.3 Documentation: Authentication for 
NGINX
There are multiple ways to enable authentication in Apache Zeppelin. This page 
describes HTTP basic auth using NGINX.
zeppelin.apache.org



Below is excerpt of my configuration:

location /zeppelin/ {
proxy_pass http://104.211.216.218:8080/;
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:8080/ws;
proxy_http_version 1.1;
proxy_set_header Upgrade websocket;
proxy_set_header Connection upgrade;
proxy_read_timeout 86400;
}




Sanket Tarun Shah - Enterprise Architect
+91 98793 56075 |  sanket.s...@outlook.com
(LinkedIn)

Re: Difficult paths for Zeppelin and Nginx integration

[Sam Nicholson]

Here's the zeppelin from my currently, working, config
I have changed my DNS domains to "internal" and "external"
Other than that, it's really verbatim.

server {
listen 443 ssl http2;
server_name  zeppelin.external;
ssl_certificate /etc/certs/fullchain.cer;
ssl_certificate_key /etc/certs/cert.key;
location / {
proxy_pass   http://zeppelin.internal:6800;
proxy_set_header Host$host;
proxy_set_header X-Real-IP   $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
}
location /ws {
proxy_pass   http://zeppelin.internal:6800;
proxy_set_header Host$host;
proxy_set_header X-Real-IP   $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;
proxy_http_version 1.1;
proxy_set_header Upgrade websocket;
proxy_set_header Connection upgrade;
proxy_read_timeout 86400;
}
}


On Mon, Jun 4, 2018 at 12:58 PM, Sanket Shah 
wrote:

> Am trying to put Nginx in front of Zeppelin. Regular requests are passing
> through, but Websockets are not working. Followed this based on guide of
> Zeppelin - https://zeppelin.apache.org/docs/0.7.3/security/
> authentication.html. Seems having a real tough luck to get this going as
> scratching head and pulling hairs 😞
> Apache Zeppelin 0.7.3 Documentation: Authentication for NGINX
> 
> There are multiple ways to enable authentication in Apache Zeppelin. This
> page describes HTTP basic auth using NGINX.
> zeppelin.apache.org
>
> Below is excerpt of my configuration:
>
> location /zeppelin/ {
> proxy_pass http://104.211.216.218:8080/;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:8080/ws;proxy_http_version 1.1;
> proxy_set_header Upgrade websocket;
> proxy_set_header Connection upgrade;
> proxy_read_timeout 86400;
> }
>
>
>
>
> *Sanket Tarun Shah - **Enterprise Architect*
> +91 98793 56075 |  sanket.s...@outlook.com 
> (LinkedIn )
>

Re: Brain dead question on my part...

[Michael Segel]

Thanks Jeff,

That explains why it didn’t work… :-)



On Jun 4, 2018, at 6:08 PM, Jeff Zhang 
mailto:zjf...@gmail.com>> wrote:


As the error says spark 2.2.1 is not supported in 0.7.2, and property 
(zeppelin.spark.enableSupportedVersionCheck) is only available in 0.8.0 
(https://issues.apache.org/jira/browse/ZEPPELIN-2324)
so please try 0.8.0 RC4  
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.8.0-rc4/
There's still one issue of publishing paragraph in 0.8.0 RC4, I will start a 
new RC, but it should work fine if don't need to publish paragraph.

Michael Segel 
mailto:msegel_had...@hotmail.com>>于2018年6月4日周一 
下午11:05写道：
Hi,

I’m trying to use Zeppelin to connect to a MapR Cluster…

Yes, I know that MapR has their own supported release but I also want to use 
the same set up to also run stand alone too…

My issue is that I’m running Zeppelin 0.7.2 and when I try to connect to spark, 
I get the following error….

 Spark 2.2.1-mapr-1803 is not supported

Ok… so its been a while, I’m trying to see what would cause this and if there 
was an easy fix… (other than going w MapR’s release and running it in a 
container.)


Thx

-Mike

Re: Brain dead question on my part...

[Jeff Zhang]

As the error says spark 2.2.1 is not supported in 0.7.2, and property (
zeppelin.spark.enableSupportedVersionCheck) is only available in 0.8.0 (
https://issues.apache.org/jira/browse/ZEPPELIN-2324)
so please try 0.8.0 RC4
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.8.0-rc4/
There's still one issue of publishing paragraph in 0.8.0 RC4, I will start
a new RC, but it should work fine if don't need to publish paragraph.

Michael Segel 于2018年6月4日周一 下午11:05写道：

> Hi,
>
> I’m trying to use Zeppelin to connect to a MapR Cluster…
>
> Yes, I know that MapR has their own supported release but I also want to
> use the same set up to also run stand alone too…
>
> My issue is that I’m running Zeppelin 0.7.2 and when I try to connect to
> spark, I get the following error….
>
>  Spark 2.2.1-mapr-1803 is not supported
>
> Ok… so its been a while, I’m trying to see what would cause this and if
> there was an easy fix… (other than going w MapR’s release and running it in
> a container.)
>
>
> Thx
>
> -Mike
>
>

Re: Difficult paths for Zeppelin and Nginx integration

[Fabien Morcamp]

Sanket,

Its works for me, and I'm based on this documentation:
https://zeppelin.apache.org/docs/0.7.3/security/authentication.html

Like that:

> location /ws {
> proxy_passhttp://my_internal_ip:8080/ws;
> proxy_read_timeout86400;
> proxy_connect_timeout 5s;
> proxy_redirectoff;
> proxy_set_header  Upgrade websocket;
> proxy_set_header  Connection upgrade;
>   }
> location / {
> proxy_passhttp://my_internal_ip:8080;
> proxy_read_timeout5s;
> proxy_connect_timeout 5s;
> proxy_redirectoff;

 }



On Mon, Jun 4, 2018 at 12:58 PM, Sanket Shah 
wrote:

> Am trying to put Nginx in front of Zeppelin. Regular requests are passing
> through, but Websockets are not working. Followed this based on guide of
> Zeppelin - https://zeppelin.apache.org/docs/0.7.3/security/
> authentication.html
> .
> Seems having a real tough luck to get this going as scratching head and
> pulling hairs 😞
> Apache Zeppelin 0.7.3 Documentation: Authentication for NGINX
> 
> There are multiple ways to enable authentication in Apache Zeppelin. This
> page describes HTTP basic auth using NGINX.
> zeppelin.apache.org
>
> Below is excerpt of my configuration:
>
> location /zeppelin/ {
> proxy_pass http://104.211.216.218:8080/;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:8080/ws;proxy_http_version 1.1;
> proxy_set_header Upgrade websocket;
> proxy_set_header Connection upgrade;
> proxy_read_timeout 86400;
> }
>
>
>
>
> *Sanket Tarun Shah - **Enterprise Architect*
> +91 98793 56075 |  sanket.s...@outlook.com
> 
> (LinkedIn
> 
> )
>

Re: Brain dead question on my part...

[Michael Segel]

Hey Trevor!

Yeah still doesn’t work.

I’ll figure it out… or just go w Mapr’s stuff in containers as the path of 
least resistance.

-Mike


On Jun 4, 2018, at 11:58 AM, Trevor Grant 
mailto:trevor.d.gr...@gmail.com>> wrote:

Yes- restart Zeppelin and make sure no instances are running.

On Mon, Jun 4, 2018 at 11:48 AM, Michael Segel 
mailto:msegel_had...@hotmail.com>> wrote:
This is a simple test that I was using to see if I could run anything…
No errors or anything just the error message…





On Jun 4, 2018, at 11:41 AM, Ruslan Dautkhanov 
mailto:dautkha...@gmail.com>> wrote:

Can you send a screenshot with the error and complete exception stack?




--
Ruslan Dautkhanov

On Mon, Jun 4, 2018 at 10:40 AM, Michael Segel 
mailto:msegel_had...@hotmail.com>> wrote:
Hmmm. Still not working.
Added it to the interpreter setting and restarted the interpreter.

The issue is that I need to use the MapR version of spark since I’m running 
this on the cluster.

Should I restart Zeppelin itself?

On Jun 4, 2018, at 11:32 AM, Ruslan Dautkhanov 
mailto:dautkha...@gmail.com>> wrote:

zeppelin.spark.enableSupportedVersionCheck

Difficult paths for Zeppelin and Nginx integration

[Sanket Shah]

Am trying to put Nginx in front of Zeppelin. Regular requests are passing 
through, but Websockets are not working. Followed this based on guide of 
Zeppelin - https://zeppelin.apache.org/docs/0.7.3/security/authentication.html. 
Seems having a real tough luck to get this going as scratching head and pulling 
hairs 😞
Apache Zeppelin 0.7.3 Documentation: Authentication for 
NGINX
There are multiple ways to enable authentication in Apache Zeppelin. This page 
describes HTTP basic auth using NGINX.
zeppelin.apache.org



Below is excerpt of my configuration:

location /zeppelin/ {
proxy_pass http://104.211.216.218:8080/;
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:8080/ws;
proxy_http_version 1.1;
proxy_set_header Upgrade websocket;
proxy_set_header Connection upgrade;
proxy_read_timeout 86400;
}




Sanket Tarun Shah - Enterprise Architect
+91 98793 56075 |  sanket.s...@outlook.com
(LinkedIn)

Re: Brain dead question on my part...

[Trevor Grant]

Yes- restart Zeppelin and make sure no instances are running.

On Mon, Jun 4, 2018 at 11:48 AM, Michael Segel 
wrote:

> This is a simple test that I was using to see if I could run anything…
> No errors or anything just the error message…
>
>
>
>
> On Jun 4, 2018, at 11:41 AM, Ruslan Dautkhanov 
> wrote:
>
> Can you send a screenshot with the error and complete exception stack?
>
>
>
>
> --
> Ruslan Dautkhanov
>
> On Mon, Jun 4, 2018 at 10:40 AM, Michael Segel 
> wrote:
>
>> Hmmm. Still not working.
>> Added it to the interpreter setting and restarted the interpreter.
>>
>> The issue is that I need to use the MapR version of spark since I’m
>> running this on the cluster.
>>
>> Should I restart Zeppelin itself?
>>
>> On Jun 4, 2018, at 11:32 AM, Ruslan Dautkhanov 
>> wrote:
>>
>> zeppelin.spark.enableSupportedVersionCheck
>>
>>
>>
>
>

Re: Brain dead question on my part...

[Michael Segel]

This is a simple test that I was using to see if I could run anything…
No errors or anything just the error message…

[cid:1A256034-A6E3-4386-806C-3A166EEBD376]



On Jun 4, 2018, at 11:41 AM, Ruslan Dautkhanov 
mailto:dautkha...@gmail.com>> wrote:

Can you send a screenshot with the error and complete exception stack?




--
Ruslan Dautkhanov

On Mon, Jun 4, 2018 at 10:40 AM, Michael Segel 
mailto:msegel_had...@hotmail.com>> wrote:
Hmmm. Still not working.
Added it to the interpreter setting and restarted the interpreter.

The issue is that I need to use the MapR version of spark since I’m running 
this on the cluster.

Should I restart Zeppelin itself?

On Jun 4, 2018, at 11:32 AM, Ruslan Dautkhanov 
mailto:dautkha...@gmail.com>> wrote:

zeppelin.spark.enableSupportedVersionCheck

Re: Brain dead question on my part...

[Ruslan Dautkhanov]

Can you send a screenshot with the error and complete exception stack?




-- 
Ruslan Dautkhanov

On Mon, Jun 4, 2018 at 10:40 AM, Michael Segel 
wrote:

> Hmmm. Still not working.
> Added it to the interpreter setting and restarted the interpreter.
>
> The issue is that I need to use the MapR version of spark since I’m
> running this on the cluster.
>
> Should I restart Zeppelin itself?
>
> On Jun 4, 2018, at 11:32 AM, Ruslan Dautkhanov 
> wrote:
>
> zeppelin.spark.enableSupportedVersionCheck
>
>
>

Re: Brain dead question on my part...

[Michael Segel]

Hmmm. Still not working.
Added it to the interpreter setting and restarted the interpreter.

The issue is that I need to use the MapR version of spark since I’m running 
this on the cluster.

Should I restart Zeppelin itself?

On Jun 4, 2018, at 11:32 AM, Ruslan Dautkhanov 
mailto:dautkha...@gmail.com>> wrote:

zeppelin.spark.enableSupportedVersionCheck

Re: Brain dead question on my part...

[Ruslan Dautkhanov]

Nope add that as a spark interpreter setting.
0.7.2 should work fine with Spark 2.2 afaik.
You may want to go with Zeppelin 0.8 when you upgrade to Spark 2.3.



-- 
Ruslan Dautkhanov

On Mon, Jun 4, 2018 at 10:29 AM, Michael Segel 
wrote:

> I’m assuming that I want to set this in ./conf/zeppelin-site.xml …
>
> Didn’t have any impact. Still getting the same error.
>
>
> On Jun 4, 2018, at 11:17 AM, Michael Segel 
> wrote:
>
> Hmmm…. did not know that option existed.
> Are there any downsides to doing this?
>
> Thx
>
> -Mike
>
>
> On Jun 4, 2018, at 11:10 AM, Ruslan Dautkhanov 
> wrote:
>
> Should you try to set  zeppelin.spark.enableSupportedVersionCheck to
> false at spark interpreter level ?
>
>
>
> --
> Ruslan Dautkhanov
>
> On Mon, Jun 4, 2018 at 9:05 AM, Michael Segel 
> wrote:
>
>> Hi,
>>
>> I’m trying to use Zeppelin to connect to a MapR Cluster…
>>
>> Yes, I know that MapR has their own supported release but I also want to
>> use the same set up to also run stand alone too…
>>
>> My issue is that I’m running Zeppelin 0.7.2 and when I try to connect to
>> spark, I get the following error….
>>
>>  Spark 2.2.1-mapr-1803 is not supported
>>
>> Ok… so its been a while, I’m trying to see what would cause this and if
>> there was an easy fix… (other than going w MapR’s release and running it in
>> a container.)
>>
>>
>> Thx
>>
>> -Mike
>>
>>
>
>
>

Re: Brain dead question on my part...

[Michael Segel]

I’m assuming that I want to set this in ./conf/zeppelin-site.xml …

Didn’t have any impact. Still getting the same error.


On Jun 4, 2018, at 11:17 AM, Michael Segel 
mailto:msegel_had...@hotmail.com>> wrote:

Hmmm…. did not know that option existed.
Are there any downsides to doing this?

Thx

-Mike


On Jun 4, 2018, at 11:10 AM, Ruslan Dautkhanov 
mailto:dautkha...@gmail.com>> wrote:

Should you try to set  zeppelin.spark.enableSupportedVersionCheck to false at 
spark interpreter level ?



--
Ruslan Dautkhanov

On Mon, Jun 4, 2018 at 9:05 AM, Michael Segel 
mailto:msegel_had...@hotmail.com>> wrote:
Hi,

I’m trying to use Zeppelin to connect to a MapR Cluster…

Yes, I know that MapR has their own supported release but I also want to use 
the same set up to also run stand alone too…

My issue is that I’m running Zeppelin 0.7.2 and when I try to connect to spark, 
I get the following error….

 Spark 2.2.1-mapr-1803 is not supported

Ok… so its been a while, I’m trying to see what would cause this and if there 
was an easy fix… (other than going w MapR’s release and running it in a 
container.)


Thx

-Mike

Re: Brain dead question on my part...

[Michael Segel]

Hmmm…. did not know that option existed.
Are there any downsides to doing this?

Thx

-Mike


On Jun 4, 2018, at 11:10 AM, Ruslan Dautkhanov 
mailto:dautkha...@gmail.com>> wrote:

Should you try to set  zeppelin.spark.enableSupportedVersionCheck to false at 
spark interpreter level ?



--
Ruslan Dautkhanov

On Mon, Jun 4, 2018 at 9:05 AM, Michael Segel 
mailto:msegel_had...@hotmail.com>> wrote:
Hi,

I’m trying to use Zeppelin to connect to a MapR Cluster…

Yes, I know that MapR has their own supported release but I also want to use 
the same set up to also run stand alone too…

My issue is that I’m running Zeppelin 0.7.2 and when I try to connect to spark, 
I get the following error….

 Spark 2.2.1-mapr-1803 is not supported

Ok… so its been a while, I’m trying to see what would cause this and if there 
was an easy fix… (other than going w MapR’s release and running it in a 
container.)


Thx

-Mike

Re: Brain dead question on my part...

[Ruslan Dautkhanov]

Should you try to set  zeppelin.spark.enableSupportedVersionCheck to false
at spark interpreter level ?



-- 
Ruslan Dautkhanov

On Mon, Jun 4, 2018 at 9:05 AM, Michael Segel 
wrote:

> Hi,
>
> I’m trying to use Zeppelin to connect to a MapR Cluster…
>
> Yes, I know that MapR has their own supported release but I also want to
> use the same set up to also run stand alone too…
>
> My issue is that I’m running Zeppelin 0.7.2 and when I try to connect to
> spark, I get the following error….
>
>  Spark 2.2.1-mapr-1803 is not supported
>
> Ok… so its been a while, I’m trying to see what would cause this and if
> there was an easy fix… (other than going w MapR’s release and running it in
> a container.)
>
>
> Thx
>
> -Mike
>
>

Brain dead question on my part...

[Michael Segel]

Hi, 

I’m trying to use Zeppelin to connect to a MapR Cluster… 

Yes, I know that MapR has their own supported release but I also want to use 
the same set up to also run stand alone too… 

My issue is that I’m running Zeppelin 0.7.2 and when I try to connect to spark, 
I get the following error…. 

 Spark 2.2.1-mapr-1803 is not supported

Ok… so its been a while, I’m trying to see what would cause this and if there 
was an easy fix… (other than going w MapR’s release and running it in a 
container.) 


Thx

-Mike