Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trend Panel doesn't work with https connection #395

Closed
ehsan007 opened this issue Aug 21, 2013 · 7 comments
Closed

Trend Panel doesn't work with https connection #395

ehsan007 opened this issue Aug 21, 2013 · 7 comments

Comments

@ehsan007
Copy link

When using Kibana with a secure connection to elasticsearch via an apache server :

elasticsearch : "https://xxx.xxx.xxx.xxx:443" (in config.js)

All panels work great but "Trend" panel which is stuck and showing Loading icon forever. I hope somebody fix this or find a workaround for it soon. Thanks

@rashidkpc
Copy link
Contributor

I'm not able to replicate this, can you attach your proxy configuration? The trend panel does not use any unique methods for talking to ES that would cause it to distinguish protocol.

@ehsan007
Copy link
Author

Thanks for your email. Here is the apache config , I am using apache 2.4.2 .

<VirtualHost :80>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.
) https://%{HTTP_HOST}%{REQUEST_URI}

<VirtualHost *:443>

SSLEngine On
SSLCertificateFile /etc/cert.crt
SSLCertificateKeyFile /etc/cert.key

ProxyPreserveHost On
ProxyRequests Off

DocumentRoot /var/www

loglevel debug
ErrorLog /var/log/apache2/error_log
CustomLog /var/log/apache2/access_log combined

Require all Denied

<LocationMatch "^(/kibana-int/dashboard/|/kibana-int/temp).*$">
ProxyPassMatch http://xxx.xxx.xxx.xxx:9200

<LocationMatch "^(/test./_aliases|/test./_search)$">
AuthFormProvider file
AuthUserFile /etc/users
AuthName test
AuthFormLoginRequiredLocation /login/index.html
AuthType form
Session on
SessionCookieName session path=/
require valid-user

ProxyPassMatch http://xxx.xxx.xxx.xxx:9200
#ProxyPassReverse http://xxx.xxx.xxx.xxx:9200

<Location /testdashboard>

Options -Multiviews
AuthFormProvider file
AuthUserFile /etc/users
AuthName test
AuthFormLoginRequiredLocation /login/index.html
AuthType form
Session on
SessionCookieName session path=/
require valid-user

<Location /dologin.html>
SetHandler form-login-handler
AuthFormLoginRequiredLocation /login/index.html
AuthFormLoginSuccessLocation /testdashboard
AuthFormPassword password
AuthFormUsername username
AuthFormProvider file
AuthUserFile /etc/users
AuthType form
AuthName test
Session On
SessionCookieName session path=/

<Location /dologout.html>
SetHandler form-logout-handler
#AuthFormLoginRequiredLocation /index.html
AuthFormLogoutLocation /login/index.html
AuthName test
Session On
SessionCookieName session path=/

Thanks

On Wed, Aug 21, 2013 at 3:26 PM, Rashid Khan [email protected]:

I'm not able to replicate this, can you attach your proxy configuration?
The trend panel does not use any unique methods for talking to ES that
would cause it to distinguish protocol.


Reply to this email directly or view it on GitHubhttps://github.com//issues/395#issuecomment-23038762
.

@rashidkpc
Copy link
Contributor

<LocationMatch "^(/test.*/_aliases|/test.*/_search)$">
should be

<LocationMatch "^(/test.*/_aliases|/test.*/_search|/test.*/_mapping)$">

Though that has nothing todo with the trends panel, it can impact the table.

@ehsan007
Copy link
Author

I fixed this

<LocationMatch "^(/test./_aliases|/test./_search|/test.*/_mapping)$">

but Trend still doesn't work. Everything else is working on my dashboard but Trend Panel. I appreciate any comment.

Thanks.

@rashidkpc
Copy link
Contributor

And the trend panel works fine without HTTPS? Can you check your configuration both with and without https?

@ehsan007
Copy link
Author

I just checked it without using HTTPS and it still doesn't work. But It does work when I directly put ES server IP address in the Config.js file.

harper-carroll pushed a commit to harper-carroll/kibana that referenced this issue Jul 11, 2016
spalger pushed a commit that referenced this issue Jun 25, 2019
@JialuZhang
Copy link

@ehsan007

In your posted configuration,

<VirtualHost :80>
RewriteEngine On
RewriteCond %{HTTPS} off
...

This configuration should be paired with
otherwise this is a silent misconfiguration.

The correct configuration would be

<VirtualHost :80>
RewriteEngine On
RewriteCond %{HTTPS} off
...
</VirtualHost>

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@rashidkpc @ehsan007 @JialuZhang and others