# Was anxious to try Kibana 7.5.2 docker. Doesn't work

**URL:** <https://discuss.elastic.co/t/was-anxious-to-try-kibana-7-5-2-docker-doesnt-work/217475>\
**Category:** Kibana\
**Created:** [February 1, 2020, 12:31am UTC](https://discuss.elastic.co/t/was-anxious-to-try-kibana-7-5-2-docker-doesnt-work/217475 "2020-02-01T00:31:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![initproto](https://avatars.discourse-cdn.com/v4/letter/i/74df32/32.png) [@initproto](https://discuss.elastic.co/u/initproto)\
**Post date:** [February 1, 2020, 12:31am UTC](https://discuss.elastic.co/t/was-anxious-to-try-kibana-7-5-2-docker-doesnt-work/217475/1 "2020-02-01T00:31:00Z")

</div>

Hi,  
I ran elastic 7.5.2 docker and kibana 7.5.2 docker. I go to the kibana url and it says

{  
"statusCode": 400,  
"error": "Bad Request",  
"message": "Invalid cookie header"  
}

A shame. Any idea why it's broken?

$ docker run --link 64bcd8d6469c:elasticsearch -p 5601:5601 [docker.elastic.co/kibana/kibana:7.5.2](http://docker.elastic.co/kibana/kibana:7.5.2)

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [February 2, 2020, 7:36pm UTC](https://discuss.elastic.co/t/was-anxious-to-try-kibana-7-5-2-docker-doesnt-work/217475/2 "2020-02-02T19:36:20Z")

</div>

> [@initproto](#):
>
> "statusCode": 400,  
> "error": "Bad Request",  
> "message": "Invalid cookie header

Try checking your kibana.yml file.  
May be try this : Edit your kibana.yml

Remove comment from bellow lines ,if server.host is bound to localhost - no problems

```auto
server.host: 0.0.0.0
elasticsearch.url: "http://localhost:9200"

```

restart kibana and try to access it. Also, does this happen in an incognito window? Maybe some browser plugin causing issues? Kibana doesn't use cookies.

Hope it helps  
Rashmi

---

<div class="post-metadata">

**Author:** ![NerdSec](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nerdsec/32/22056_2.png) [@NerdSec](https://discuss.elastic.co/u/NerdSec)\
**Post date:** [February 3, 2020, 4:33am UTC](https://discuss.elastic.co/t/was-anxious-to-try-kibana-7-5-2-docker-doesnt-work/217475/3 "2020-02-03T04:33:17Z")

</div>

Hi,

Do you have a specific use case for using the `--link` parameter?

In case you don't want to expose your ES container on all interfaces at `9200`, creating a docker network and then using it to run the two containers would be a better option.

```auto
$ docker network create ES --driver=overlay2 --attachable
$ docker run --network=ES docker.elastic.co/elasticsearch/elasticsearch:7.5.2
$ docker run --network=ES -p 5601:5601 docker.elastic.co/kibana/kibana:7.5.2

```

In case you don't mind exposing ES on all interfaces (only for testing), you can simply skip the network creation and flags while running the two containers. I made no changes to my `yml` files while running these commands for testing, and it worked. Did you edit your `yml`?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 2, 2020, 4:33am UTC](https://discuss.elastic.co/t/was-anxious-to-try-kibana-7-5-2-docker-doesnt-work/217475/4 "2020-03-02T04:33:18Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.