Decanter / kibana and https.

classic Classic list List threaded Threaded
3 messages Options
SvS
Reply | Threaded
Open this post in threaded view
|

Decanter / kibana and https.

SvS
This post was updated on .
Hi all,

We try to use https instead of http for decanter / kibana. When I use
https://localhost:8182/kibana this gives the error below:
Oops!
Looks like something went wrong. Refreshing may do the trick.

Go back  or clear your session

Fatal Error
Kibana: Unknown error while connecting to Elasticsearch

Error: Unknown error while connecting to Elasticsearch
Error: No Living connections
    at sendReqWithConnection
(https://localhost:8182/kibana/index.js?_b=7562:85302:15)
    at next (https://localhost:8182/kibana/index.js?_b=7562:83802:7)
    at https://localhost:8182/kibana/index.js?_b=7562:52880:21


Detected in karaf version 4.0.9, 4.1.3 and 4.1.4 on Windows.

Used configuration for org.ops4j.pax.web is:
javax.servlet.context.tempdir = ${karaf.home}\\data/pax-web-jsp
org.ops4j.pax.web.config.file = ${karaf.home}/etc/jetty.xml
org.osgi.service.http.port=8181
org.osgi.service.http.enabled=false
org.osgi.service.http.port.secure=8182
org.osgi.service.http.secure.enabled=true
org.ops4j.pax.web.ssl.keystore=./etc/keystores/https_keystore
org.ops4j.pax.web.ssl.password=OBF\:<obfuscated>
org.ops4j.pax.web.ssl.keypassword=OBF\:<obfuscated>
org.ops4j.pax.web.ssl.clientauthwanted=true


When using http it all works fine.

Does anyone have a suggestion or is this a bug?
Regards,
SvS
Reply | Threaded
Open this post in threaded view
|

Re: Decanter / kibana and https.

jbonofre
Hi,

Thanks for the report. Let me take a look.

I think that problem is on the connection to the elasticsearch instance (using
8200 by default).

Did you try to pass the elasticsearch location on the kibana URL ?

I created the following Jira to work on this one:

https://issues.apache.org/jira/browse/KARAF-5552

Regards
JB

On 12/21/2017 12:07 PM, SvS wrote:

> Hi all,
>
> We try to use https instead of http for decanter / kibana. When I use
> https://localhost:8182/kibana this gives the error below:
> /Oops!
> Looks like something went wrong. Refreshing may do the trick.
>
> Go back  or clear your session
>
> Fatal Error
> Kibana: Unknown error while connecting to Elasticsearch
>
> Error: Unknown error while connecting to Elasticsearch
> Error: No Living connections
>      at sendReqWithConnection
> (https://localhost:8444/kibana/index.js?_b=7562:85302:15)
>      at next (https://localhost:8444/kibana/index.js?_b=7562:83802:7)
>      at https://localhost:8444/kibana/index.js?_b=7562:52880:21/
>
> Detected in karaf version 4.0.9, 4.1.3 and 4.1.4 on Windows.
>
> Used configuration for org.ops4j.pax.web is:
> /javax.servlet.context.tempdir = ${karaf.home}\\data/pax-web-jsp
> org.ops4j.pax.web.config.file = ${karaf.home}/etc/jetty.xml
> org.osgi.service.http.port=8181
> org.osgi.service.http.enabled=false
> org.osgi.service.http.port.secure=8182
> org.osgi.service.http.secure.enabled=true
> org.ops4j.pax.web.ssl.keystore=./etc/keystores/https_keystore
> org.ops4j.pax.web.ssl.password=OBF\:<obfuscated>
> org.ops4j.pax.web.ssl.keypassword=OBF\:<obfuscated>
> org.ops4j.pax.web.ssl.clientauthwanted=true/
>
> When using http it all works fine.
>
> Does anyone have a suggestion or is this a bug?
>
>
>
> -----
> Regards,
> SvS
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
SvS
Reply | Threaded
Open this post in threaded view
|

Re: Decanter / kibana and https.

SvS
This post was updated on .
Hi JB,

Thanks for your quick response!

Did you mean something like: http://localhost:9200 ?

Response on request: http://localhost:9200/ is:
{
  "name" : "decanter",
  "cluster_name" : "elasticsearch",
  "version" : {
    "number" : "2.2.0",
    "build_hash" : "NA",
    "build_timestamp" : "NA",
    "build_snapshot" : false,
    "lucene_version" : "5.4.1"
  },
  "tagline" : "You Know, for Search"
}


Response on request: https://localhost:9200/ is:
ERR_CONNECTION_CLOSED

I think you are right...?
Regards,
SvS