# \[Couldnt able to access Kibana from browser\] hosting ELK on a remote Linux Machine **URL:** \ **Category:** Kibana\ **Created:** [May 7, 2020, 6:22am UTC](https://discuss.elastic.co/t/couldnt-able-to-access-kibana-from-browser-hosting-elk-on-a-remote-linux-machine/231461 "2020-05-07T06:22:42Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![manish1](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@manish1](https://discuss.elastic.co/u/manish1)\ **Post date:** [May 7, 2020, 6:22am UTC](https://discuss.elastic.co/t/couldnt-able-to-access-kibana-from-browser-hosting-elk-on-a-remote-linux-machine/231461/1 "2020-05-07T06:22:42Z")
I have installed ELK on a remote Linux machine but couldn't able to access the kibana from the browser. I know by default kibana is accessible on localhost. Changes I did on kibana.yml uncommenting and updating these lines: ```auto server.port: 5601 server.host: "server IP address" elasticsearch.hosts: ["http://server IP address:9200"] logging.dest: /var/log/kibana/kibana.log ``` Started the service after the changes `sudo -i service kibana start` in the browser, I typed URL: [HTTP://server](HTTP://server) ip address:5601 still, it's unreachable `This site can’t be reached` I tried debugging it by going through a few posts: commands: `sudo ss -tln | grep 5601` it gave me no output `sudo lsof -i -P -n | grep LISTEN` 5601 was not listed Please help where I am doing wrong. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [May 8, 2020, 11:45am UTC](https://discuss.elastic.co/t/couldnt-able-to-access-kibana-from-browser-hosting-elk-on-a-remote-linux-machine/231461/2 "2020-05-08T11:45:57Z")
hi @manish1 welcome to Elastic community! By your comments, it looks like kibana is not running. What do you have in your logs? ---
**Author:** ![manish1](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@manish1](https://discuss.elastic.co/u/manish1)\ **Post date:** [May 8, 2020, 12:02pm UTC](https://discuss.elastic.co/t/couldnt-able-to-access-kibana-from-browser-hosting-elk-on-a-remote-linux-machine/231461/3 "2020-05-08T12:02:22Z")
I belive its running based on the output of this command `sudo -i service kibana status` ```auto ● kibana.service - Kibana Loaded: loaded (/etc/systemd/system/kibana.service; disabled; vendor preset: enabled) Active: active (running) since Fri 2020-05-08 17:30:15 IST; 2s ago Main PID: 122883 (node) Tasks: 7 (limit: 4675) CGroup: /system.slice/kibana.service └─122883 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml May 08 17:30:15 tripnomics systemd[1]: Started Kibana. ``` Even the log is also not getting printed into the given location. I think none of the changes done in the kibana.yml are reflecting back. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [May 8, 2020, 1:36pm UTC](https://discuss.elastic.co/t/couldnt-able-to-access-kibana-from-browser-hosting-elk-on-a-remote-linux-machine/231461/4 "2020-05-08T13:36:13Z")
according to [the docs](https://www.elastic.co/guide/en/kibana/7.6/start-stop.html#_running_kibana_with_systemd) with systemd your logs should appear with this command ``` journalctl -u kibana.service ``` can you try that one? I've installed a `7.6.2` from packages on a Debian server and I could see the logs exactly with that command. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 5, 2020, 1:36pm UTC](https://discuss.elastic.co/t/couldnt-able-to-access-kibana-from-browser-hosting-elk-on-a-remote-linux-machine/231461/5 "2020-06-05T13:36:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.