Unable to connect filebeat with kibana to load dashboard

Elastic Stack Beats
1

Hi there,
I'm running kibana behind apache2 proxy
kibana is running in localhost port 5601
and my apache2 IP & port as 46.246.x.x:yyyy

when I ran ./filebeat setup -e command in order to connect filebeat on client server to kibana on host server
I'm getting this result

Index setup finished.
Loading dashboards (Kibana must be running and reachable)
Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to http://46.246.x.x:yyyy/api/status fails: fail to execute the HTTP GET request: Get "http://46.246.x.x:yyyy/api/status": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers). Response:

my filebeat.yml as below

setup.kibana:
   host: "46.246.x.x:yyyy" 
   username: "username"
   password: "password"

my kibana.yml

# =================== System: Kibana Server ===================
# Kibana is served by a back end server. This setting specifies the port to use.
#server.port: 5601

# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
#server.host: "0.0.0.0"

# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""

# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# Defaults to `false`.
#server.rewriteBasePath: false

# Specifies the public URL at which Kibana is available for end users. If
# `server.basePath` is configured this URL should end with the same basePath.
#server.publicBaseUrl: ""

# The maximum payload size in bytes for incoming server requests.
#server.maxPayload: 1048576

# The Kibana server's name. This is used for display purposes.
#server.name: "your-hostname"
2

Default protocol is http, might be you need https. Read this

3

could you tell me why would I use https if I can access kibana from browser using http://46.246.x.x:yyyy
I didn't use https protocol in kibana.yml nor in apache2

4

HTTPS is not mandatory, just recommended.
Your filebeat host must see Kibana over port yyyy. Check with telnet or curl.
Does your kibana user, have rights to trigger APIs? Test with
curl -u username http://46.246.x.x:yyyy/api/status

5

I tried to curl with kibana user on my local machine and on on filebeat host

on my local machine I could obtain results
but on my filebeat host I got

curl: (28) Failed to connect to 46.246.x.x port yyyy: Connection timed out
6

The TCP connection is not opened from the filebeat server to Kibana. Firewall issue.

7

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