# Cannot access Kibana on port 5601 **URL:** \ **Category:** Kibana\ **Created:** [March 27, 2019, 12:15pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121 "2019-03-27T12:15:38Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![SubjectXXX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/subjectxxx/32/42930_2.png) [@SubjectXXX](https://discuss.elastic.co/u/SubjectXXX)\ **Post date:** [March 27, 2019, 12:15pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121/1 "2019-03-27T12:15:38Z")
Greetings, I hope this is correct section for this kind of problems. Browser on http(s)://domain.name:5601 returns ERR\_CONNECTION\_RESET. If I do curl [http://127.0.0.1:5601](http://127.0.0.1:5601), I get empty response, nothing, no error. Error log in /var/log/ doesnt exist. Few starting infos: - curl 127.0.0.1:9200: { "name" : "OhblFpx", "cluster\_name" : "elasticsearch", "cluster\_uuid" : "iHsPEAMnQFCut0QgrXZ3qw", "version" : { "number" : "6.7.0", "build\_flavor" : "default", "build\_type" : "deb", "build\_hash" : "8453f77", "build\_date" : "2019-03-21T15:32:29.844721Z", "build\_snapshot" : false, "lucene\_version" : "7.7.0", "minimum\_wire\_compatibility\_version" : "5.6.0", "minimum\_index\_compatibility\_version" : "5.0.0" }, "tagline" : "You Know, for Search" } - netstat -an | grep 5601 tcp 0 0 0.0.0.0:5601 0.0.0.0:\* LISTEN - ps -eaf | grep kibana kibana 6072 1 4 13:00 ? 00:00:31 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header-size=65536 /usr/share/kibana/bin/../src/cli -c /etc/kibana kibana.yml root 6346 2076 0 13:11 pts/0 00:00:00 grep --color=auto kibana - service kibana status ● kibana.service - Kibana Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2019-03-27 13:00:34 CET; 12min ago Main PID: 6072 (node) Tasks: 11 (limit: 4915) CGroup: /system.slice/kibana.service └─6072 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header-size=65536 /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml Mar 27 13:00:45 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:45Z","tags":["status","plugin:remote\_clusters@6.7.0","info"],"pid":6072,"state":"green","message":"Status changed from yellow to green - Ready","prevSta Mar 27 13:00:45 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:45Z","tags":["status","plugin:cross\_cluster\_replication@6.7.0","info"],"pid":6072,"state":"green","message":"Status changed from yellow to green - Ready Mar 27 13:00:45 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:45Z","tags":["info","monitoring-ui","kibana-monitoring"],"pid":6072,"message":"Starting monitoring stats collection"} Mar 27 13:00:45 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:45Z","tags":["status","plugin:security@6.7.0","info"],"pid":6072,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"ye Mar 27 13:00:45 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:45Z","tags":["status","plugin:maps@6.7.0","info"],"pid":6072,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow Mar 27 13:00:45 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:45Z","tags":["license","info","xpack"],"pid":6072,"message":"Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | Mar 27 13:00:46 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:46Z","tags":["reporting","warning"],"pid":6072,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from fai Mar 27 13:00:46 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:46Z","tags":["status","plugin:reporting@6.7.0","info"],"pid":6072,"state":"green","message":"Status changed from uninitialized to green - Ready","prevSt Mar 27 13:00:47 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:47Z","tags":["listening","info"],"pid":6072,"message":"Server running at [http://0:5601](http://0:5601)"} Mar 27 13:00:47 efe-web kibana[6072]: {"type":"log","@timestamp":"2019-03-27T12:00:47Z","tags":["status","plugin:spaces@6.7.0","info"],"pid":6072,"state":"green","message":"Status changed from yellow to green - Ready","prevState - kibana.yml: server.port: 5601 server.host: "0" server.name: "domain.name" elasticsearch.hosts: ["[http://localhost:9200](http://localhost:9200)"] - ufw status Status: inactive - port 80 and 443 works on domain. ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [March 27, 2019, 6:01pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121/2 "2019-03-27T18:01:26Z")
if you execute `curl -I http://127.0.0.1:5601` do you see a response similar to the following ```auto HTTP/1.1 302 Found location: /login?next=%2F kbn-name: kibana kbn-xpack-sig: 1afc90f64c0c4c890d32587e9c446842 content-type: text/html; charset=utf-8 vary: origin cache-control: no-cache content-length: 0 connection: close Date: Wed, 27 Mar 2019 18:01:18 GMT ``` ---
**Author:** ![SubjectXXX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/subjectxxx/32/42930_2.png) [@SubjectXXX](https://discuss.elastic.co/u/SubjectXXX)\ **Post date:** [March 27, 2019, 8:19pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121/3 "2019-03-27T20:19:14Z")
I get this: HTTP/1.1 302 Found location: /app/kibana kbn-name: kibana kbn-xpack-sig: c...7 content-type: text/html; charset=utf-8 cache-control: no-cache content-length: 0 connection: close Date: Wed, 27 Mar 2019 20:18:33 GMT ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [March 27, 2019, 8:28pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121/4 "2019-03-27T20:28:15Z")
Great! Then Kibana is listening on localhost:5601. Can you try doing the same curl request using the ip address of the "public" network interface both on the Kibana server itself, and the computer that you're running the web browser from? ---
**Author:** ![SubjectXXX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/subjectxxx/32/42930_2.png) [@SubjectXXX](https://discuss.elastic.co/u/SubjectXXX)\ **Post date:** [March 27, 2019, 8:44pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121/5 "2019-03-27T20:44:06Z")
I get same result with command ran on server. I guess some FW is messing with outside access tho, I'm not sure which one, since I have it turned off.. ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [March 27, 2019, 9:02pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121/6 "2019-03-27T21:02:35Z")
It's possible that your internal network is configured to prevent the two hosts from communicating at all. ---
**Author:** ![SubjectXXX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/subjectxxx/32/42930_2.png) [@SubjectXXX](https://discuss.elastic.co/u/SubjectXXX)\ **Post date:** [March 27, 2019, 9:08pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121/7 "2019-03-27T21:08:47Z")
Well, thank you for now, will go research my network topology.. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 24, 2019, 9:09pm UTC](https://discuss.elastic.co/t/cannot-access-kibana-on-port-5601/174121/8 "2019-04-24T21:09:01Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.