# Kibana loads default elastic page instead of setup **URL:** \ **Category:** Kibana\ **Created:** [February 29, 2024, 8:58am UTC](https://discuss.elastic.co/t/kibana-loads-default-elastic-page-instead-of-setup/354421 "2024-02-29T08:58:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Palak\_Chopra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palak_chopra/32/125700_2.png) [@Palak\_Chopra](https://discuss.elastic.co/u/Palak_Chopra)\ **Post date:** [February 29, 2024, 8:58am UTC](https://discuss.elastic.co/t/kibana-loads-default-elastic-page-instead-of-setup/354421/1 "2024-02-29T08:58:29Z")
I am using filebeat with elk on an ubuntu server VM. When I visit the server's ip from the host machine this is what I get: ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/d/fdcf449057ac2e58086592bd9dfa82abd6402ccc.png) How do I go to the kibana setup/login page? ifconfig of Ubuntu server VM: ```auto enp0s3: flags=4419 mtu 1500 inet 10.0.2.5 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::a00:27ff:fe31:cdb0 prefixlen 64 scopeid 0x20 ether 08:00:27:31:cd:b0 txqueuelen 1000 (Ethernet) RX packets 33 bytes 7158 (7.1 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 230 bytes 19317 (19.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp0s8: flags=4163 mtu 1500 inet 192.168.56.107 netmask 255.255.255.0 broadcast 192.168.56.255 inet6 fe80::a00:27ff:fea1:a7df prefixlen 64 scopeid 0x20 ether 08:00:27:a1:a7:df txqueuelen 1000 (Ethernet) RX packets 3536 bytes 336259 (336.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 4337 bytes 2968278 (2.9 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 5456 bytes 2930579 (2.9 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 5456 bytes 2930579 (2.9 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` Kibana.yml: ```auto # 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 na> # The default is 'localhost', which usually means remote machines will not be able to > # 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 base> # 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. # This setting was effectively always `false` before Kibana 6.3 and will # default to `true` starting in Kibana 7.0. #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: "http://192.168.56.107:5601" # 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" # The URLs of the Elasticsearch instances to use for all your queries. elasticsearch.hosts: ["http://192.168.56.107:9200"] # Kibana uses an index in Elasticsearch to store saved searches, visualizations and # dashboards. Kibana creates a new index if the index doesn't already exist. #kibana.index: ".kibana" # The default application to load. #kibana.defaultAppId: "home" # If your Elasticsearch is protected with basic authentication, these settings provide # the username and password that the Kibana server uses to perform maintenance on the > # index at startup. Your Kibana users still need to authenticate with Elasticsearch, w> # is proxied through the Kibana server. #elasticsearch.username: "kibana_system" #elasticsearch.password: "pass" # Kibana can also authenticate to Elasticsearch via "service account tokens". # If may use this token instead of a username/password. # elasticsearch.serviceAccountToken: "my_token" # Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectiv> # These settings enable SSL for outgoing requests from the Kibana server to the browse> #server.ssl.enabled: false #server.ssl.certificate: /path/to/your/server.crt #server.ssl.key: /path/to/your/server.key # Optional settings that provide the paths to the PEM-format SSL certificate and key f> # These files are used to verify the identity of Kibana to Elasticsearch and are requi> # xpack.security.http.ssl.client_authentication in Elasticsearch is set to required. #elasticsearch.ssl.certificate: /path/to/your/client.crt #elasticsearch.ssl.key: /path/to/your/client.key # Optional setting that enables you to specify a path to the PEM file for the certific> # authority for your Elasticsearch instance. #elasticsearch.ssl.certificateAuthorities: ["/path/to/your/CA.pem"] # To disregard the validity of SSL certificates, change this setting's value to 'none'. #elasticsearch.ssl.verificationMode: full # Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the > # the elasticsearch.requestTimeout setting. #elasticsearch.pingTimeout: 1500 # Time in milliseconds to wait for responses from the back end or Elasticsearch. This > # must be a positive integer. #elasticsearch.requestTimeout: 30000 # List of Kibana client-side headers to send to Elasticsearch. To send *no* client-side # headers, set this value to [] (an empty list). #elasticsearch.requestHeadersWhitelist: [authorization] # Header names and values that are sent to Elasticsearch. Any custom headers cannot be> # by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist conf> #elasticsearch.customHeaders: {} # Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 t> #elasticsearch.shardTimeout: 30000 # Logs queries sent to Elasticsearch. Requires logging.verbose set to true. #elasticsearch.logQueries: false # Specifies the path where Kibana creates the process ID file. #pid.file: /run/kibana/kibana.pid # Enables you to specify a file where Kibana stores log output. #logging.dest: stdout # Set the value of this setting to true to suppress all logging output. #logging.silent: false # Set the interval in milliseconds to sample system and process performance # metrics. Minimum is 100ms. Defaults to 5000. #ops.interval: 5000 # Specifies locale to be used for all localizable strings, dates and number formats. # Supported languages are the following: English - en , by default , Chinese - zh-CN . #i18n.locale: "en" ``` Elastic.yml: ```auto # # NOTE: Elasticsearch comes with reasonable defaults for most settings. # Before you set out to tweak and tune the configuration, make sure you # understand what are you trying to accomplish and the consequences. # # The primary way of configuring a node is via this file. This template lists # the most important settings you may want to configure for a production cluster. # # Please consult the documentation for further information on configuration options: # https://www.elastic.co/guide/en/elasticsearch/reference/index.html # # ---------------------------------- Cluster ----------------------------------- # # Use a descriptive name for your cluster: # #cluster.name: nids # # ------------------------------------ Node ------------------------------------ # # Use a descriptive name for the node: # #node.name: node-1 # # Add custom attributes to the node: # #node.attr.rack: r1 # # ----------------------------------- Paths ------------------------------------ # # Path to directory where to store the data (separate multiple locations by comma): # path.data: /var/lib/elasticsearch # # Path to log files: # path.logs: /var/log/elasticsearch # # ----------------------------------- Memory ----------------------------------- # # Lock the memory on startup: # #bootstrap.memory_lock: true # # Make sure that the heap size is set to about half the memory available # on the system and that the owner of the process is allowed to use this # limit. # # Elasticsearch performs poorly when the system is swapping the memory. # # ---------------------------------- Network ----------------------------------- # # By default Elasticsearch is only accessible on localhost. Set a different # address here to expose this node on the network: # network.host: 192.168.56.107 # # By default Elasticsearch listens for HTTP traffic on the first free port it # finds starting at 9200. Set a specific HTTP port here: # #http.port: 9200 # # For more information, consult the network module documentation. # # --------------------------------- Discovery ---------------------------------- # # Pass an initial list of hosts to perform discovery when this node is started: # The default list of hosts is ["127.0.0.1", "[::1]"] # discovery.seed_hosts: ["192.168.56.107"] # # Bootstrap the cluster using an initial set of master-eligible nodes: # #cluster.initial_master_nodes: ["node-1", "node-2"] # # For more information, consult the discovery and cluster formation module documentati> # # ---------------------------------- Various ----------------------------------- # # Require explicit names when deleting indices: # #action.destructive_requires_name: true # # ---------------------------------- Security ---------------------------------- # # ***WARNING*** # # Elasticsearch security features are not enabled by default. # These features are free, but require configuration changes to enable them. # This means that users don’t have to provide credentials and can get full access # to the cluster. Network connections are also not encrypted. # # To protect your data, we strongly encourage you to enable the Elasticsearch security> # Refer to the following documentation for instructions. # # https://www.elastic.co/guide/en/elasticsearch/reference/7.16/configuring-stack-secur> ``` PS - my VM is in NAT and host-only network mode ---
**Author:** ![ahmed\_charafouddine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ahmed_charafouddine/32/45129_2.png) [@ahmed\_charafouddine](https://discuss.elastic.co/u/ahmed_charafouddine)\ **Post date:** [February 29, 2024, 9:05am UTC](https://discuss.elastic.co/t/kibana-loads-default-elastic-page-instead-of-setup/354421/2 "2024-02-29T09:05:15Z")
> [@Palak\_Chopra](#): > > How do I go to the kibana setup/login page? Hello @Palak_Chopra As it says in the pop-up on the right at the bottom, you need to activate security on elasticsearch. Here is a link that may help you : [https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-stack-security.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-stack-security.html) ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [February 29, 2024, 9:27am UTC](https://discuss.elastic.co/t/kibana-loads-default-elastic-page-instead-of-setup/354421/3 "2024-02-29T09:27:47Z")
Hi @Palak_Chopra Welcome to the community. Apologies, I'm a bit confused. What Kibana setup page are you talking about? What are you trying to accomplish? @ahmed_charafouddine is correct. You do not have security enabled so there is no login screen.... ---
**Author:** ![Palak\_Chopra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palak_chopra/32/125700_2.png) [@Palak\_Chopra](https://discuss.elastic.co/u/Palak_Chopra)\ **Post date:** [March 1, 2024, 9:11am UTC](https://discuss.elastic.co/t/kibana-loads-default-elastic-page-instead-of-setup/354421/4 "2024-03-01T09:11:46Z")
Thank you! I totally skipped over this during installation. ---
**Author:** ![Palak\_Chopra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/palak_chopra/32/125700_2.png) [@Palak\_Chopra](https://discuss.elastic.co/u/Palak_Chopra)\ **Post date:** [March 1, 2024, 9:12am UTC](https://discuss.elastic.co/t/kibana-loads-default-elastic-page-instead-of-setup/354421/5 "2024-03-01T09:12:53Z")
I was getting a default elastic page instead of the setup one that comes when you first access kibana. @ahmed_charafouddine 's answer helped! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 29, 2024, 9:13am UTC](https://discuss.elastic.co/t/kibana-loads-default-elastic-page-instead-of-setup/354421/6 "2024-03-29T09:13:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.