You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -235,7 +235,7 @@ TIP: The available basemaps and boundaries can be explored from the `/maps` endp
235
235
[[elastic-maps-server-kibana]]
236
236
==== Kibana configuration
237
237
238
-
With {hosted-ems} running, add the `map.emsUrl` configuration key in your <<settings, kibana.yml>> file pointing to the root of the service. This setting will point {kib} to request EMS basemaps and boundaries from {hosted-ems}. Typically this will be the URL to the <<ems-host,host and port>> of {hosted-ems}. For example, `map.emsUrl: https://my-ems-server:8080`.
238
+
With {hosted-ems} running, add the `map.emsUrl` configuration key in your <<settings, kibana.yml>> file pointing to the root of the service. This setting will point {kib} to request EMS basemaps and boundaries from {hosted-ems}. Typically this will be the URL to the <<ems-host,host and port>> of {hosted-ems}. For example, `map.emsUrl: <BASE_URL>:8080`.
If you are using a self-managed deployment, access {kib} through the web application on port 5601.
16
16
17
-
. Point your web browser to the machine where you are running {kib} and specify the port number. For example, `localhost:5601` or `http://YOURDOMAIN.com:5601`.
17
+
. Point your web browser to the machine where you are running {kib} and specify the port number. For example, `localhost:5601` or `<HOST_URL>:5601`.
18
18
+
19
19
To remotely connect to {kib}, set <<server-host,server.host>> to a non-loopback address.
0 commit comments