Further when I check configuration from UI, it does not show webserver port
setting there. So I think the issue is that the zeppelin-site.xml is not
applied somehow. I have already restarted Zeppelin, but does not help.

Regards,
Chandra
On Jun 30, 2016 12:07 PM, "Chandra Maloo" <maloochan...@gmail.com> wrote:

> I have configured zeppelin.server.port to 443 and zeppelin.websocket.port
> to 80
> It starts successfully, when I run as super user, but shows disconnected
> on UI.
> Do you know what could be the reason?
> On Jun 30, 2016 11:59 AM, "Abhisar Mohapatra" <
> abhisar.mohapa...@inmobi.com> wrote:
>
>> Yes ,I think you can do that.Anyways you have an option to configure the
>> port you want your zeppelin instance to run on.Point is the IP shouldn't be
>> a private IP and should be accessible from outside.Or if VPN
>> connection,then yes.
>>
>> Thanks,
>> Abhisar
>>
>> On Thu, Jun 30, 2016 at 8:22 AM, Chandra Maloo <maloochan...@gmail.com>
>> wrote:
>>
>>> Hello,
>>> I am working in an organization where firewall allows only HTTP and
>>> HTTPS traffic. I have Zeppelin installed in a machine within firewall.
>>> Can I configure Zeppelin to work with only 80 and 443 ports so that I
>>> can access it from outside the organization with its public IP?
>>>
>>> Regards,
>>> Chandra
>>>
>>
>>
>> _____________________________________________________________
>> The information contained in this communication is intended solely for
>> the use of the individual or entity to whom it is addressed and others
>> authorized to receive it. It may contain confidential or legally privileged
>> information. If you are not the intended recipient you are hereby notified
>> that any disclosure, copying, distribution or taking any action in reliance
>> on the contents of this information is strictly prohibited and may be
>> unlawful. If you have received this communication in error, please notify
>> us immediately by responding to this email and then delete it from your
>> system. The firm is neither liable for the proper and complete transmission
>> of the information contained in this communication nor for any delay in its
>> receipt.
>
>

Reply via email to