# Access Kibana 7.8 outside of LAN **URL:** \ **Category:** Kibana\ **Created:** [July 23, 2020, 2:07pm UTC](https://discuss.elastic.co/t/access-kibana-7-8-outside-of-lan/242352 "2020-07-23T14:07:33Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![prophoto](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@prophoto](https://discuss.elastic.co/u/prophoto)\ **Post date:** [July 23, 2020, 2:07pm UTC](https://discuss.elastic.co/t/access-kibana-7-8-outside-of-lan/242352/1 "2020-07-23T14:07:33Z")
My web servers running CentOS 7 are on AWS. I am running Elasticsearch and Kibana on a local VM also running CentOS 7 and what logs shipped there. Logs are flowing fine to Elasticsearch from the remote web servers. Unfortunately for the life of me I cannot get the remote servers to see Kibana. When I run a curl [http://myip:5601/api/status](http://myip:5601/api/status) or [http://mydomain.com:5601/api/status](http://mydomain.com:5601/api/status) I get a failure. When it do it from another machine in my LAN it works fine. I have server.host set to 0.0.0.0. Port forwards are set correctly, same as Elasticsearch which is working. Help! What am I missing? ---
**Author:** ![cheiligers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheiligers/32/73114_2.png) [@cheiligers](https://discuss.elastic.co/u/cheiligers)\ **Post date:** [July 29, 2020, 7:49pm UTC](https://discuss.elastic.co/t/access-kibana-7-8-outside-of-lan/242352/2 "2020-07-29T19:49:16Z")
@prophoto, what do you mean by your `remote servers` not seeing Kibana? Can your Elasticsearch instance not see Kibana or does Kibana not see your Elasticsearch instance? If it's the latter, try restarting Kibana and make sure that your `server.host` is set in the `kibana.yml` file. ---
**Author:** ![prophoto](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@prophoto](https://discuss.elastic.co/u/prophoto)\ **Post date:** [July 29, 2020, 10:39pm UTC](https://discuss.elastic.co/t/access-kibana-7-8-outside-of-lan/242352/3 "2020-07-29T22:39:15Z")
Kibana and ES are on the same local server in my Office LAN so they communicate fine. I have multiple web servers running CentOS 7 on AWS that Run Filebeat/Metricbeat and store data in the local ES instance just fine. But for some reason those web servers do not see Kibana instance. ---
**Author:** ![cheiligers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheiligers/32/73114_2.png) [@cheiligers](https://discuss.elastic.co/u/cheiligers)\ **Post date:** [July 29, 2020, 10:43pm UTC](https://discuss.elastic.co/t/access-kibana-7-8-outside-of-lan/242352/4 "2020-07-29T22:43:59Z")
I must confess, I don't know why you would need the web servers to see Kibana. Kibana only needs access to the data in Elasticsearch, which is where Filebeat and Metricbeat are sending the data. ---
**Author:** ![prophoto](https://avatars.discourse-cdn.com/v4/letter/p/f6c823/32.png) [@prophoto](https://discuss.elastic.co/u/prophoto)\ **Post date:** [July 29, 2020, 10:45pm UTC](https://discuss.elastic.co/t/access-kibana-7-8-outside-of-lan/242352/5 "2020-07-29T22:45:50Z")
Initially it was to setup Dashboards for Metricbeat/Filebeat. Since then I used the locally running Metricbeat/Filebeat to add the dashboards. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 26, 2020, 10:45pm UTC](https://discuss.elastic.co/t/access-kibana-7-8-outside-of-lan/242352/6 "2020-08-26T22:45:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.