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.

Sign up for GitHub

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

Jump to bottom

HTTP is hard coded for config file access. #1586

Closed
raffpaquin opened this issue Oct 8, 2014 · 1 comment
Closed

HTTP is hard coded for config file access. #1586

raffpaquin opened this issue Oct 8, 2014 · 1 comment
Assignees
@rashidkpc
Labels
bug Fixes for quality problems that affect the customer experience
Milestone
4.0.0-BETA2

Comments

@raffpaquin
Copy link

When I'm running Kibana 4 behind a Nginx proxy with SSL activated, Kibana is working but not able to connect to ElasticSearch since the HTTP procotol is hard coded.

https://github.com/elasticsearch/kibana/blame/master/src/kibana/index.js#L24
@rashidkpc rashidkpc added the bug Fixes for quality problems that affect the customer experience label Oct 8, 2014
@rashidkpc rashidkpc added this to the 4.0.0-BETA2 milestone Oct 8, 2014
@rashidkpc rashidkpc changed the title Kibana 4 behind Nginx Proxy with SSL - HTTP protocol hardcoded HTTP is hardcoded for config file access. Oct 8, 2014
@rashidkpc rashidkpc changed the title HTTP is hardcoded for config file access. HTTP is hard coded for config file access. Oct 8, 2014
@rashidkpc
Copy link
Contributor

Good point, this should probably be a command line switch or something of that nature.

@spalger spalger self-assigned this Oct 8, 2014
@rashidkpc rashidkpc assigned rashidkpc and unassigned spalger Oct 15, 2014
spalger pushed a commit that referenced this issue Oct 15, 2014
@spenceralger
Merge pull request #1680 from rashidkpc/fix/elasticsearch-endpoint-pr…
28ddc1f 
…otocol

Use same protocol for elasticsearch as everything else. Closes #1586
@rashidkpc rashidkpc mentioned this issue Oct 21, 2014
Closed
@jlachowski jlachowski mentioned this issue Oct 22, 2014
Closed
@larrycameron80 larrycameron80 mentioned this issue Feb 1, 2024
Open
@santosomar santosomar mentioned this issue Feb 2, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rashidkpc rashidkpc

Labels
bug Fixes for quality problems that affect the customer experience
Projects
None yet
Milestone
4.0.0-BETA2
Development

No branches or pull requests
3 participants
@raffpaquin @rashidkpc @spalger