Issue with server.publicBaseUrl

Elastic Stack Kibana
1

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.

2

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?

3

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.

4

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

2 Likes
5

Thank you, that appears to have resolved the issue :slight_smile: though doesn't explain why it's not being picked up from kibana.yml :frowning:

6

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