# Can't connect remotely to Kibana from Windows machine **URL:** \ **Category:** Kibana\ **Created:** [February 21, 2019, 8:49pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486 "2019-02-21T20:49:59Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![HWCMP](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@HWCMP](https://discuss.elastic.co/u/HWCMP)\ **Post date:** [February 21, 2019, 8:49pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/1 "2019-02-21T20:49:59Z")
I have kibana installed on ubuntu server and can't navigate to it remotely. I'm on the same private network as the server. I've edited the kibana.yml file to the following: # Kibana is served by a back end server. This setting specifies the port to use. server.port: 5601 # Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values. # The default is 'localhost', which usually means remote machines will not be able to connect. # To allow connections from remote users, set this parameter to a non-loopback address. server.host: "0.0.0.0" I've opened the port 5601 and even disabled UFW with no luck. Any suggestions on what else I should look for. I'm new to this so help would be greatly appreciated. Thanks. ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [February 21, 2019, 10:27pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/2 "2019-02-21T22:27:05Z")
Are you able to connect to the server from a browser running locally? Or able to use curl to get a Kibana HTTP response locally? ---
**Author:** ![HWCMP](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@HWCMP](https://discuss.elastic.co/u/HWCMP)\ **Post date:** [February 22, 2019, 12:47pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/3 "2019-02-22T12:47:22Z")
No I can't. I get this using curl HTTP/1.1 503 Service Unavailable retry-after: 30 content-type: text/html; charset=utf-8 cache-control: no-cache content-length: 30 Date: Fri, 22 Feb 2019 12:46:10 GMT Connection: keep-alive ---
**Author:** ![HWCMP](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@HWCMP](https://discuss.elastic.co/u/HWCMP)\ **Post date:** [February 22, 2019, 1:06pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/4 "2019-02-22T13:06:21Z")
Tim. Now I get this when I try and access remotely in chrome. Looks like I’m getting close. Kibana server is not ready yet ---
**Author:** ![HWCMP](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@HWCMP](https://discuss.elastic.co/u/HWCMP)\ **Post date:** [February 22, 2019, 9:30pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/5 "2019-02-22T21:30:51Z")
Hi Tim. Any thoughts as to why I keep getting this "Kibana server is not ready yet"? Thanks! ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [February 25, 2019, 1:40pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/6 "2019-02-25T13:40:30Z")
Hi, apologies for the lapse. Is Elasticsearch up and running when you start Kibana? Do the logs show anything about the connection to Elasticsearch? I don't see what version you are running, but perhaps it's an issue of Kibana getting stuck trying to upgrade from an older version? [https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0](https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0) ---
**Author:** ![HWCMP](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@HWCMP](https://discuss.elastic.co/u/HWCMP)\ **Post date:** [February 25, 2019, 2:02pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/7 "2019-02-25T14:02:13Z")
Good morning Tim. Elastic search is running. Not sure about the logs. I'm totally new to elasticsearch. If you could point me in the direction to access the log and what to look for I can send to you. I reinstalled elasticsearch this morning and not I'm getting HTTP/!.1 200 OK whereas before it wasn't. HTTP/1.1 200 OK kbn-name: kibana kbn-xpack-sig: 0267e2644851baacc7a0f79fab6407f9 cache-control: no-cache content-type: text/html; charset=utf-8 content-length: 68761 vary: accept-encoding accept-ranges: bytes connection: close Date: Mon, 25 Feb 2019 13:58:54 GMT ---
**Author:** ![HWCMP](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@HWCMP](https://discuss.elastic.co/u/HWCMP)\ **Post date:** [February 25, 2019, 2:14pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/8 "2019-02-25T14:14:09Z")
is the log you're referring to? status = error # log action execution errors for easier debugging logger.action.name = org.elasticsearch.action logger.action.level = debug appender.console.type = Console appender.console.name = console appender.console.layout.type = PatternLayout appender.console.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node\_name]%marker %m%n appender.rolling.type = RollingFile appender.rolling.name = rolling appender.rolling.fileName = {sys:es.logs.base\_path}{sys:file.separator}{sys:es.logs.cluster\_name}.log appender.rolling.layout.type = PatternLayout appender.rolling.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node\_name]%marker %.-10000m%n appender.rolling.filePattern = {sys:es.logs.base\_path}{sys:file.separator}{sys:es.logs.cluster\_name}-%d{yyyy-MM-dd}-%i.log.gz appender.rolling.policies.type = Policies appender.rolling.policies.time.type = TimeBasedTriggeringPolicy appender.rolling.policies.time.interval = 1 appender.rolling.policies.time.modulate = true appender.rolling.policies.size.type = SizeBasedTriggeringPolicy appender.rolling.policies.size.size = 128MB appender.rolling.strategy.type = DefaultRolloverStrategy appender.rolling.strategy.fileIndex = nomax appender.rolling.strategy.action.type = Delete appender.rolling.strategy.action.basepath = {sys:es.logs.base\_path} appender.rolling.strategy.action.condition.type = IfFileName appender.rolling.strategy.action.condition.glob = {sys:es.logs.cluster\_name}-\* appender.rolling.strategy.action.condition.nested\_condition.type = IfAccumulatedFileSize appender.rolling.strategy.action.condition.nested\_condition.exceeds = 2GB rootLogger.level = info rootLogger.appenderRef.console.ref = console rootLogger.appenderRef.rolling.ref = rolling appender.deprecation\_rolling.type = RollingFile appender.deprecation\_rolling.name = deprecation\_rolling ---
**Author:** ![HWCMP](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@HWCMP](https://discuss.elastic.co/u/HWCMP)\ **Post date:** [February 25, 2019, 2:17pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/9 "2019-02-25T14:17:01Z")
elasticsearch version 6.6.1 ---
**Author:** ![HWCMP](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@HWCMP](https://discuss.elastic.co/u/HWCMP)\ **Post date:** [February 25, 2019, 2:50pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/10 "2019-02-25T14:50:58Z")
Tim. It's working. I used a different machine to access and it works fine. Something weird going on with the other machine not allowing me to access. Firewall is disabled. I'm good for now. Thanks! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 25, 2019, 2:51pm UTC](https://discuss.elastic.co/t/cant-connect-remotely-to-kibana-from-windows-machine/169486/11 "2019-03-25T14:51:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.