Could not able to access ELK 6.8.0 on Browser

Elastic Stack Elasticsearch
1

Hi,

We have installed ELK 6.8.0 using debian and not enabled security.But we could not able to access cluster using web browser and observed by default .security index.Even the elasticsearch services running and curl commands are successful but could not able to access on browser on host.Is firewall blocking on host not sure as we could able to access previous version elastic services from host.

Regards,
Vivek

2

Hi Vivek,

Please take the time to give us a little more detail.

But we could not able to access cluster using web browser

What exactly are you typing in your browser and what is the error message you see?

and observed by default .security index

Can you please explain what you mean with this ?

.Even the elasticsearch services running

Can you share the output ?

curl commands are successful

Can you share the curl commands you tried and were successful ?

Is firewall blocking on host not sure as we could able to access previous version elastic services from host.

If you have a firewall on your host/server this might disallowing the connection but we can't know this. You have to check yourself or talk to your IT department.

3

Hi,

if we try to access using ipaddress:9200 on browser we getting connection refused error.

In the indices list we have observed .security index by default.

if we test using command sudo systemctl status elasticsearch.service it is active

curl -XGET 'http://ipaddress:9200' we are getting successful response

The connection is successful with previous ELK versions.

Regards,
Vivek

4

Do you run the curl command from the same machine where the browser is installed ? Or from the machine where the Elasticsearch node is installed ?

5

curl command from where elasticsearch is installed

6

Then the problem is that your machine ( where your browser is installed ) can't reach the machine where Elasticsearch is installed.
What is this IP address that you are using ? Is it routable ? is it local ?

This is not an Elasticsearch issue though, you need to talk to your network engineers / IT department.

7

I have given proper permission to path.data and enabled ports on firewall...Issue fixed ..Thank you...

8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.