# Cannot access kibana **URL:** \ **Category:** Kibana\ **Created:** [January 11, 2019, 4:57pm UTC](https://discuss.elastic.co/t/cannot-access-kibana/163936 "2019-01-11T16:57:51Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Richard\_Phillips\_Roy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richard_phillips_roy/32/46989_2.png) [@Richard\_Phillips\_Roy](https://discuss.elastic.co/u/Richard_Phillips_Roy)\ **Post date:** [January 11, 2019, 4:57pm UTC](https://discuss.elastic.co/t/cannot-access-kibana/163936/1 "2019-01-11T16:57:51Z")
I'm using Bitnami ELK stack on Windows, and I'm unable to access kibana elastic search is running, but when I open "[http://127.0.0.1:5601/elk/app/kibana](http://127.0.0.1:5601/elk/app/kibana)" i'm getting this {"statusCode":404,"error":"Not Found","message":"Not Found"} please help I'm a beginner these are my logs: C:\Bitnami\elk-6.5.4-1\kibana\bin\>kibana log [16:53:34.810] [warning][config][deprecation] You should set server.basePath along with server.rewriteBasePath. Starting in 7.0, Kibana will expect that all requests start with server.basePath rather than expecting you to rewrite the requests in your reverse proxy. Set server.rewriteBasePath to false to preserve the current behavior and silence this warning. log [16:53:34.826] [warning][pid] pid file already exists at C:\Bitnami\elk-6.5.4-1/kibana/tmp/kibana.pid log [16:53:35.397] [info][status][plugin:kibana@6.5.4] Status changed from uninitialized to green - Ready log [16:53:35.428] [info][status][plugin:elasticsearch@6.5.4] Status changed from uninitialized to yellow - Waiting for Elasticsearch log [16:53:35.521] [info][status][plugin:timelion@6.5.4] Status changed from uninitialized to green - Ready log [16:53:35.537] [info][status][plugin:console@6.5.4] Status changed from uninitialized to green - Ready log [16:53:35.537] [info][status][plugin:metrics@6.5.4] Status changed from uninitialized to green - Ready log [16:53:35.553] [info][status][plugin:elasticsearch@6.5.4] Status changed from yellow to green - Ready log [16:53:35.568] [info][listening] Server running at [http://127.0.0.1:5601](http://127.0.0.1:5601) ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [January 25, 2019, 5:26pm UTC](https://discuss.elastic.co/t/cannot-access-kibana/163936/2 "2019-01-25T17:26:49Z")
How is the health of your cluster ? The cluster health API allows to get a very simple status on the health of the cluster. For example, on a quiet single node cluster with a single index with 5 shards and one replica, this: `GET _cluster/health` Do ES logs indicate anything ? Are you using a proxy. Thanks Rashmi ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 22, 2019, 5:26pm UTC](https://discuss.elastic.co/t/cannot-access-kibana/163936/3 "2019-02-22T17:26:51Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.