# Problem access web to kibana and elasticsearch

**URL:** <https://discuss.elastic.co/t/problem-access-web-to-kibana-and-elasticsearch/122104>\
**Category:** Kibana\
**Created:** [March 1, 2018, 2:59pm UTC](https://discuss.elastic.co/t/problem-access-web-to-kibana-and-elasticsearch/122104 "2018-03-01T14:59:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amandine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amandine/32/28305_2.png) [@Amandine](https://discuss.elastic.co/u/Amandine)\
**Post date:** [March 1, 2018, 2:59pm UTC](https://discuss.elastic.co/t/problem-access-web-to-kibana-and-elasticsearch/122104/1 "2018-03-01T14:59:29Z")

</div>

Hello, I want Kibana and Elasticsearch to be accessible via a domain name (example: [example.com](http://example.com)) on the browser. -\> [http://example.com:9200](http://example.com:9200) or [http://example.com:5601](http://example.com:5601). The domain name exists and there is a public IP. There is NAT on the 9200 and 5601 port.

I modified the configuration files of Elasticsearch, Kibana and Logstash. It works with a curl [http://example.com:9200](http://example.com:9200) or curl [http://example.com:5601](http://example.com:5601) but not via the browser.

I don't want to access it with the IP because I want to secure the site with a certificate lets'encrypt.

Can someone help me ?!

---

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [March 1, 2018, 7:33pm UTC](https://discuss.elastic.co/t/problem-access-web-to-kibana-and-elasticsearch/122104/2 "2018-03-01T19:33:44Z")

</div>

Is your host machine aware of what to resolve [example.com](http://example.com) to? Usually this is an entry in /etc/hosts. In the interim you can test by binding kibana to your public IP (or 0.0.0.0) in kibana.yml.

---

<div class="post-metadata">

**Author:** ![KiHyun\_Kim](https://avatars.discourse-cdn.com/v4/letter/k/f17d59/32.png) [@KiHyun\_Kim](https://discuss.elastic.co/u/KiHyun_Kim)\
**Post date:** [March 2, 2018, 4:48am UTC](https://discuss.elastic.co/t/problem-access-web-to-kibana-and-elasticsearch/122104/3 "2018-03-02T04:48:59Z")

</div>

I think you can use proxy.

---

<div class="post-metadata">

**Author:** ![Amandine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/amandine/32/28305_2.png) [@Amandine](https://discuss.elastic.co/u/Amandine)\
**Post date:** [March 2, 2018, 8:23am UTC](https://discuss.elastic.co/t/problem-access-web-to-kibana-and-elasticsearch/122104/4 "2018-03-02T08:23:30Z")

</div>

My host machine don't resolve [example.com](http://example.com). My problem is a little resolve by an other person.  
I have no proxy.  
Thank you for your answers.

Today, my problem is the Kibana's status is red.  
ui sttings -\> Elastic plugin is red  
plugin:elasticsearch@5.6.5 -\> Request Timeout after 3000ms

If you have ideas...

But I have an other problem. I don't touch configuration files and I have an error 504 Gateway Time-Out.

---

<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:** [March 30, 2018, 8:34am UTC](https://discuss.elastic.co/t/problem-access-web-to-kibana-and-elasticsearch/122104/5 "2018-03-30T08:34:54Z")

</div>

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