# Nothing on 5601 **URL:** \ **Category:** Kibana\ **Created:** [January 9, 2018, 3:45pm UTC](https://discuss.elastic.co/t/nothing-on-5601/114729 "2018-01-09T15:45:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![DarkVodka34](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/darkvodka34/32/26247_2.png) [@DarkVodka34](https://discuss.elastic.co/u/DarkVodka34)\ **Post date:** [January 9, 2018, 3:45pm UTC](https://discuss.elastic.co/t/nothing-on-5601/114729/1 "2018-01-09T15:45:30Z")
Very new to linux running ubuntu server and have been following this tut > **[Elasticstack (ELK), Suricata and pfSense Firewall – Part 2: Elasticstack...](https://extelligenceblog.it/2017/07/14/elastic-stack-suricata-idps-and-pfsense-firewall-part-2-elasticstack-installation-and-config/)** > > Introduction This is the second article in a series documenting the implementation of reporting using Elastic Stack of log data from the Suricata IDPS running on the Open Source pfSense firewall. T… I get nothing on [http://10.0.0.249:5601](http://10.0.0.249:5601) curl [http://localhost:5601](http://localhost:5601) Gives darkvodka34@WebServer:~ netstat -anp | grep 5601 Gives (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) tcp 0 0 127.0.0.1:5601 0.0.0.0:\* LISTEN - tcp 0 0 127.0.0.1:47698 127.0.0.1:5601 TIME\_WAIT - sudo service kibana status Gives ● kibana.service - Kibana Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: e Active: active (running) since Tue 2018-01-09 15:38:45 GMT; 6min ago Main PID: 3067 (node) Tasks: 10 Memory: 70.8M CPU: 4.015s CGroup: /system.slice/kibana.service └─3067 /usr/share/kibana/bin/../node/bin/node --no-warnings /usr/shar Jan 09 15:38:47 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"log","@timestamp":"2018-01- Jan 09 15:38:47 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"log","@timestamp":"2018-01- Jan 09 15:38:47 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"log","@timestamp":"2018-01- Jan 09 15:38:47 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"log","@timestamp":"2018-01- Jan 09 15:38:47 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"log","@timestamp":"2018-01- Jan 09 15:38:47 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"log","@timestamp":"2018-01- Jan 09 15:38:47 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"log","@timestamp":"2018-01- Jan 09 15:39:37 [WebServer.com](http://WebServer.com) systemd[1]: Started Kibana. Jan 09 15:40:15 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"response","@timestamp":"201 Jan 09 15:43:58 [WebServer.com](http://WebServer.com) kibana[3067]: {"type":"response","@timestamp":"201 [2]+ Stopped sudo service kibana status I have no clue as this worked fine the last time I followed this tut Thanks ---
**Author:** ![thomasneirynck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thomasneirynck/32/23313_2.png) [@thomasneirynck](https://discuss.elastic.co/u/thomasneirynck)\ **Post date:** [January 9, 2018, 10:05pm UTC](https://discuss.elastic.co/t/nothing-on-5601/114729/2 "2018-01-09T22:05:58Z")
hi @DarkVodka34, It's a little hard to make up. So Kibana works on localhost but not accessing by IP? I'd check first and make sure you have the `server.host: 0.0.0.0` configured in the kibana.yml ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 6, 2018, 10:05pm UTC](https://discuss.elastic.co/t/nothing-on-5601/114729/3 "2018-02-06T22:05:59Z")
Closed on February 6, 2018, 10:05pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.