# Issue with server.publicBaseUrl

**URL:** <https://discuss.elastic.co/t/issue-with-server-publicbaseurl/285796>\
**Category:** Kibana\
**Created:** [October 4, 2021, 9:06am UTC](https://discuss.elastic.co/t/issue-with-server-publicbaseurl/285796 "2021-10-04T09:06:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![PhilD](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@PhilD](https://discuss.elastic.co/u/PhilD)\
**Post date:** [October 4, 2021, 9:06am UTC](https://discuss.elastic.co/t/issue-with-server-publicbaseurl/285796/1 "2021-10-04T09:06:27Z")

</div>

Hello,

I've deployed Kibana 7.14, behind a NGINX proxy, but keep getting a toast notification that server.publicBaseUrl has not been set; yet it has been in kibana.yml. Is there a way to dump the running configuration to ensure it has indeed been set? or is there something I need to do differently from an NGINX perspective please.

Thanks.

---

<div class="post-metadata">

**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\
**Post date:** [October 5, 2021, 12:32pm UTC](https://discuss.elastic.co/t/issue-with-server-publicbaseurl/285796/2 "2021-10-05T12:32:12Z")

</div>

> Is there a way to dump the running configuration to ensure it has indeed been set?

Unfortunately, no. It's not currently possible due to security reasons since the config file might contain sensitive settings.  
Have you run Kibana with `server.publicBaseUrl` set in ` kibana.yml` ? Or you adjusted the config while Kibana was running and sent the `SIGHUP` signal?

---

<div class="post-metadata">

**Author:** ![PhilD](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@PhilD](https://discuss.elastic.co/u/PhilD)\
**Post date:** [October 5, 2021, 12:35pm UTC](https://discuss.elastic.co/t/issue-with-server-publicbaseurl/285796/3 "2021-10-05T12:35:06Z")

</div>

Hi @Mikhail_Shustov .. I am using the Kibana docker image and have checked that it has been set correctly in kibana.yml. The container has been restarted multiple times. Thanks.

---

<div class="post-metadata">

**Author:** ![Mikhail\_Shustov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikhail_shustov/32/49186_2.png) [@Mikhail\_Shustov](https://discuss.elastic.co/u/Mikhail_Shustov)\
**Post date:** [October 5, 2021, 12:44pm UTC](https://discuss.elastic.co/t/issue-with-server-publicbaseurl/285796/4 "2021-10-05T12:44:02Z")

</div>

> [@PhilD](#):
>
> server.publicBaseUrl

Could you try to set `server.publicBaseUrl` value via an ENV var? It should be `SERVER_PUBLICBASEURL: ...` according to

> **[Install Kibana with Docker | Kibana Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/kibana/current/docker.html#environment-variable-config)**

---

<div class="post-metadata">

**Author:** ![PhilD](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@PhilD](https://discuss.elastic.co/u/PhilD)\
**Post date:** [October 5, 2021, 12:51pm UTC](https://discuss.elastic.co/t/issue-with-server-publicbaseurl/285796/5 "2021-10-05T12:51:11Z")

</div>

Thank you, that appears to have resolved the issue 🙂 though doesn't explain why it's not being picked up from kibana.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:** [November 2, 2021, 12:51pm UTC](https://discuss.elastic.co/t/issue-with-server-publicbaseurl/285796/6 "2021-11-02T12:51:37Z")

</div>

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