# Problem using SERVER\_PUBLICBASEURL with docker-compose **URL:** \ **Category:** Kibana\ **Tags:** docker\ **Created:** [October 5, 2022, 12:27pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874 "2022-10-05T12:27:19Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![mammodde](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@mammodde](https://discuss.elastic.co/u/mammodde)\ **Post date:** [October 5, 2022, 12:27pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874/1 "2022-10-05T12:27:19Z")
Hi, I am currently trying to set the field `SERVER_PUBLICSBASEURL` on my docker-compose.yml, but it seems that nothing is changing. I can only access to kibana through the ip but not through the hostname I wrote. the docker-compose is on a separeted server, but on the same network. Do you have any idea of how this should work? ```auto kibana: depends_on: es01: condition: service_healthy es02: condition: service_healthy es03: condition: service_healthy image: docker.elastic.co/kibana/kibana:${STACK_VERSION} volumes: - certs:/usr/share/kibana/config/certs - kibanadata:/usr/share/kibana/data ports: - ${KIBANA_PORT}:5601 environment: - SERVERNAME=kibana - ELASTICSEARCH_HOSTS=https://es01:9200 - ELASTICSEARCH_USERNAME=kibana_system - ELASTICSEARCH_PASSWORD=${KIBANA_PASSWORD} - ELASTICSEARCH_SSL_CERTIFICATEAUTHORITIES=config/certs/ca/ca.crt - SERVER_PUBLICBASEURL= http://${HOSTNAME}:5601 mem_limit: ${MEM_LIMIT} healthcheck: test: [ "CMD-SHELL", "curl -s -I http://localhost:5601 | grep -q 'HTTP/1.1 302 Found'", ] interval: 10s timeout: 10s retries: 120 ``` ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 5, 2022, 1:45pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874/2 "2022-10-05T13:45:46Z")
`SERVER_PUBLICBASEURL= http://${HOSTNAME}:5601` looks like you have a space after the `=` And perhaps you want `SERVERNAME`? `SERVER_PUBLICBASEURL=http://${SERVERNAME}:5601` ---
**Author:** ![mammodde](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@mammodde](https://discuss.elastic.co/u/mammodde)\ **Post date:** [October 5, 2022, 2:19pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874/3 "2022-10-05T14:19:28Z")
basically what I want is to be able to search for the kibana page from chrome typing `http://hostname:5601`- Am I doing it right? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 5, 2022, 2:42pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874/4 "2022-10-05T14:42:19Z")
I do not have to add anything extra ... You do not needs base `SERVER_PUBLICBASEURL` unless you are trying to change the base path you are not. Here is my ultra simple (yes I am sure you will want more) but it works already ```auto --- version: '3' services: elasticsearch: container_name: es01 image: docker.elastic.co/elasticsearch/elasticsearch:${TAG} # 8.x environment: ['CLI_JAVA_OPTS=-Xms1g -Xmx1g','bootstrap.memory_lock=true','discovery.type=single-node','xpack.security.enabled=false', 'xpack.security.enrollment.enabled=false'] ports: - 9200:9200 networks: - elastic ulimits: memlock: soft: -1 hard: -1 nofile: soft: 65536 hard: 65536 kibana: image: docker.elastic.co/kibana/kibana:${TAG} container_name: kib01 environment: XPACK_APM_SERVICEMAPENABLED: "true" XPACK_ENCRYPTEDSAVEDOBJECTS_ENCRYPTIONKEY: d1a66dfd-c4d3-4a0a-8290-2abcb83ab3aa LOGGING_ROOT_LEVEL: error ports: - 5601:5601 networks: - elastic networks: elastic: ``` ```auto $ hostname hyperion ``` ![Screen Shot 2022-10-05 at 7.35.42 AM](https://us1.discourse-cdn.com/elastic/original/3X/3/4/34381e345fb9f042139e430f99f7663081ccfc06.png) What shows when you run `hostname` on your system? Perhaps try the above and see if it works... ---
**Author:** ![mammodde](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@mammodde](https://discuss.elastic.co/u/mammodde)\ **Post date:** [October 5, 2022, 2:45pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874/5 "2022-10-05T14:45:03Z")
where did you set hyperion hostname? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 5, 2022, 2:46pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874/6 "2022-10-05T14:46:24Z")
> [@mammodde](#): > > where did you set hyperion hostname? I did not... that is my point... Try my docker compose real quick see if it works. `TAG=8.4.2 docker-compose -f es-kb-compose.yml` ---
**Author:** ![mammodde](https://avatars.discourse-cdn.com/v4/letter/m/f08c70/32.png) [@mammodde](https://discuss.elastic.co/u/mammodde)\ **Post date:** [October 5, 2022, 2:58pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874/7 "2022-10-05T14:58:28Z")
it still says that the page is not accessible ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [October 5, 2022, 3:06pm UTC](https://discuss.elastic.co/t/problem-using-server-publicbaseurl-with-docker-compose/315874/8 "2022-10-05T15:06:38Z")
> [@mammodde](#): > > it still says that the page is not accessible but works with `localhost`? when you run `hostname` what do you get? When you run what do you get... `$ nslookup hyperion` \