# Kibana not accessible in browser after allowing port in firewall-cmd

**URL:** <https://discuss.elastic.co/t/kibana-not-accessible-in-browser-after-allowing-port-in-firewall-cmd/316526>\
**Category:** Kibana\
**Created:** [October 13, 2022, 11:03am UTC](https://discuss.elastic.co/t/kibana-not-accessible-in-browser-after-allowing-port-in-firewall-cmd/316526 "2022-10-13T11:03:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mikhatanu](https://avatars.discourse-cdn.com/v4/letter/m/ba8739/32.png) [@mikhatanu](https://discuss.elastic.co/u/mikhatanu)\
**Post date:** [October 13, 2022, 11:03am UTC](https://discuss.elastic.co/t/kibana-not-accessible-in-browser-after-allowing-port-in-firewall-cmd/316526/1 "2022-10-13T11:03:37Z")

</div>

Hello, i have installed kibana in remote host from ssh. I tried curl from the host and it succeed. I tried to access it from browser, but it said ERR\_CONNECTION\_TIMED\_OUT.

here is my firewalld

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/a/2a4d381cbedf2eb51320e2a095921c90e4ec8da1.png)

```auto
# firewall-cmd --list-ports
5601/tcp 8080/tcp

```

my server setting in kibana.yml

```auto
server.host: "10.151.92.111"
server.port: 5601

```

curl from ssh in remote host:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/e/de1e49ccd523d9d112e2fafdf513899c660f76e0.png)  
TL;DR: connected /success

here is my netstat -tulpn

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/c/2c427bb98fec62a5b1d648712046df38431e7390.png)  
TL;DR: port open is 5601 on tcp, not accessible. port 8080 on tcp6 is accessible

browser result:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/c/6c9fcc7bbdf4d3792966e767f592b20a6501a254.png)  
Image transcript:

```auto
This site can't be reached.
10.151.92.111 took too long to respond.
Try:
* Checking the connection
* Checking the proxy and the firewall
* Running windows network diagnostics
ERR_CONNECTION_TIMED_OUT

Reload Details

```

I have another service that runs at port 8080 and i can access it from my browser

---

<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:** [October 13, 2022, 10:46pm UTC](https://discuss.elastic.co/t/kibana-not-accessible-in-browser-after-allowing-port-in-firewall-cmd/316526/2 "2022-10-13T22:46:18Z")

</div>

Please don't post pictures of text, logs or code. They are difficult to read, impossible to search and replicate (if it's code), and some people may not be even able to see them 🙂

---

<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 10, 2022, 9:37pm UTC](https://discuss.elastic.co/t/kibana-not-accessible-in-browser-after-allowing-port-in-firewall-cmd/316526/3 "2022-11-10T21:37:21Z")

</div>



---

<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:** [December 8, 2022, 6:21pm UTC](https://discuss.elastic.co/t/kibana-not-accessible-in-browser-after-allowing-port-in-firewall-cmd/316526/4 "2022-12-08T18:21:55Z")

</div>



---

<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:** [January 5, 2023, 6:22pm UTC](https://discuss.elastic.co/t/kibana-not-accessible-in-browser-after-allowing-port-in-firewall-cmd/316526/5 "2023-01-05T18:22:48Z")

</div>

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