# Access Elasticsearch with public IP

**URL:** <https://discuss.elastic.co/t/access-elasticsearch-with-public-ip/334743>\
**Category:** Elasticsearch\
**Created:** [May 31, 2023, 6:09am UTC](https://discuss.elastic.co/t/access-elasticsearch-with-public-ip/334743 "2023-05-31T06:09:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rakhshunda\_Noorein\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rakhshunda_noorein_j/32/99407_2.png) [@Rakhshunda\_Noorein\_J](https://discuss.elastic.co/u/Rakhshunda_Noorein_J)\
**Post date:** [May 31, 2023, 6:09am UTC](https://discuss.elastic.co/t/access-elasticsearch-with-public-ip/334743/1 "2023-05-31T06:09:21Z")

</div>

Hello,

I have my Elasticsearch running on my windows 10 server. **I want to access it with \< my static public ip address \>:9200**

> I can access my elasticsearch from the server with:
> 
> - `localhost:9200` `<my ipv4 address from ipconfig>:9200`

> I can access my elasticsearch from the other device connected to same network as server:
> 
> - `<my ipv4 address from ipconfig>:9200`

> _ **But i cannot access it with outside of network with:** _
> 
> - _ **`<my static public ip address>:9200`** _

My Elasticsearch.yml file is:

```auto
network.host: 0.0.0.0
# Enable security features
xpack.security.enabled: true

xpack.security.enrollment.enabled: true

# Enable encryption for HTTP API client connections, such as Kibana, Logstash, and Agents
xpack.security.http.ssl:
  enabled: true
  keystore.path: certs/http.p12

# Enable encryption and mutual authentication between cluster nodes
xpack.security.transport.ssl:
  enabled: true
  verification_mode: certificate
  keystore.path: certs/transport.p12
  truststore.path: certs/transport.p12
# Create a new cluster with the current node only
# Additional nodes can still join the cluster later
cluster.initial_master_nodes: ["DESKTOP-PAD6FDG"]

# Allow HTTP API connections from anywhere
# Connections are encrypted and require user authentication
http.host: 0.0.0.0

```

---

<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:** [May 31, 2023, 7:54am UTC](https://discuss.elastic.co/t/access-elasticsearch-with-public-ip/334743/2 "2023-05-31T07:54:17Z")

</div>

Is your public IP also associated with an interface on the Elasticsearch host?

---

<div class="post-metadata">

**Author:** ![Rakhshunda\_Noorein\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rakhshunda_noorein_j/32/99407_2.png) [@Rakhshunda\_Noorein\_J](https://discuss.elastic.co/u/Rakhshunda_Noorein_J)\
**Post date:** [May 31, 2023, 8:48am UTC](https://discuss.elastic.co/t/access-elasticsearch-with-public-ip/334743/3 "2023-05-31T08:48:26Z")

</div>

No...How do I check this??..

---

<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:** [June 28, 2023, 8:49am UTC](https://discuss.elastic.co/t/access-elasticsearch-with-public-ip/334743/4 "2023-06-28T08:49:06Z")

</div>

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