# Unable to login to localhost:9200

**URL:** <https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [March 23, 2022, 7:48am UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416 "2022-03-23T07:48:54Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![csreddy.ennam](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@csreddy.ennam](https://discuss.elastic.co/u/csreddy.ennam)\
**Post date:** [March 23, 2022, 7:48am UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/1 "2022-03-23T07:48:54Z")

</div>

we were using Elasticsearch from more than 2 years, now we are unable to open localhost:9200 (latest version: Using Elasticsearch 8.1.0 )

---

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [March 23, 2022, 7:50am UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/2 "2022-03-23T07:50:56Z")

</div>

Hi there! You would need to share a lot more information than that for anyone to be able to help you in a meaningful way. What did you change recently ? Did you upgrade an existing cluster or installed one anew ? What does "unable to open" mean exactly ? What is the error you are getting ? Is there anything in the logs?

---

<div class="post-metadata">

**Author:** ![csreddy.ennam](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@csreddy.ennam](https://discuss.elastic.co/u/csreddy.ennam)\
**Post date:** [March 23, 2022, 7:53am UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/3 "2022-03-23T07:53:06Z")

</div>

we have installed latest Elasticsearch and made it as windows service, after that when we try to open in browser [http://localhost:32570](http://localhost:32570) (we modified default port) unable to open the web page in older versions we were able to open this.

---

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [March 23, 2022, 8:00am UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/4 "2022-03-23T08:00:12Z")

</div>

Please follow our documentation in [Install Elasticsearch with .zip on Windows | Elasticsearch Guide [8.1] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/zip-windows.html#windows-service)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 27, 2022, 11:59pm UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/5 "2022-03-27T23:59:31Z")

</div>

3 posts were split to a new topic: [Connection refused on put mapping](https://discuss.elastic.co/t/connection-refused-on-put-mapping/300790)

---

<div class="post-metadata">

**Author:** ![csreddy.ennam](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@csreddy.ennam](https://discuss.elastic.co/u/csreddy.ennam)\
**Post date:** [March 23, 2022, 11:20am UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/8 "2022-03-23T11:20:57Z")

</div>

when i try to open in browser ([http://localhost:32570](http://localhost:32570)) (port updated), getting an popup window requesting for username and password, provided validation credentials still unable to proceed.  
Getting following error:{"error":{"root\_cause":[{"type":"security\_exception","reason":"missing authentication credentials for REST request [/]","header":{"WWW-Authenticate":["Basic realm="security" charset="UTF-8"","ApiKey"]}}],"type":"security\_exception","reason":"missing authentication credentials for REST request [/]","header":{"WWW-Authenticate":["Basic realm="security" charset="UTF-8"","ApiKey"]}},"status":401}

Is that any configuration need to do, in the prior release we don't see this issue.

---

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [March 23, 2022, 1:51pm UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/9 "2022-03-23T13:51:05Z")

</div>

I shared a link to our docs , please read it

---

<div class="post-metadata">

**Author:** ![csreddy.ennam](https://avatars.discourse-cdn.com/v4/letter/c/6f9a4e/32.png) [@csreddy.ennam](https://discuss.elastic.co/u/csreddy.ennam)\
**Post date:** [March 28, 2022, 4:27pm UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/10 "2022-03-28T16:27:45Z")

</div>

Thanks

---

<div class="post-metadata">

**Author:** ![bb\_datta](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bb_datta/32/107969_2.png) [@bb\_datta](https://discuss.elastic.co/u/bb_datta)\
**Post date:** [July 6, 2022, 7:08am UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/11 "2022-07-06T07:08:09Z")

</div>

Thank you very much, this was simple and it helps 😃

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 4, 2022, 8:34am UTC](https://discuss.elastic.co/t/unable-to-login-to-localhost-9200/300416/12 "2022-11-04T08:34:47Z")

</div>


