# Error running Elastic Maps behind proxy **URL:** \ **Category:** Kibana\ **Tags:** docker, maps\ **Created:** [December 28, 2023, 1:27pm UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082 "2023-12-28T13:27:39Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![m.hanna](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@m.hanna](https://discuss.elastic.co/u/m.hanna)\ **Post date:** [December 28, 2023, 1:27pm UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/1 "2023-12-28T13:27:39Z")
I am trying to run an EMS server on a disconnected network behind an Nginx reverse-proxy in a docker swarm. I am able to start EMS up and it looks to connect to elasticsearch without the `basePath` setting. As soon as I add `BASEPATH` to the environment EMS fails to start. I tried to change the logging level to debug to see why it doesn't start, but I am not getting anything too obvious. Here is the EMS stanza from my docker-compose.yml: ```auto ems: image: ems:8.11.1 hostname: ems environment: # - BASEPATH=/map - ELASTICSEARCH_HOST=https://elasticsearch:9200 - ELASTICSEARCH_USERNAME=ems - ELASTICSEARCH_PASSWORD=XXXXXXXXXXXXXXX - ELASTICSEARCH_SSL_CERTIFICATE=/usr/src/app/server/config/certs/elasticsearch/elasticsearch.crt - ELASTICSEARCH_SSL_KEY=/usr/src/app/server/config/certs/elasticsearch/elasticsearch.key - ELASTICSEARCH_SSL_CERTIFICATEAUTHORITIES=/usr/src/app/server/config/certs/ca/ca/crt volumes: - './config/ems/certs/:/usr/src/app/server/config/certs/' ports: - 8080:8080 networks: ['net'] ``` With `BASEPATH` commented out, I can successfully connect to EMS from the elasticsearch container: ```auto # docker exec -it elasticsearch curl -k http://ems:8080/status {"version":"8.11.1","overall":{"level":0,"state":"available","title":"All services are available"},"services":{"License":{"level":0,"state":"available","title":"Success", ... ``` When I uncomment `BASEPATH` and restart EMS, it never enters a running state and elasticsearch cannot resolve the ems hostname. The only change I see in the logs is that the `/status` endpoint can no longer be resolved and gives me a status code of 404 instead of 200. Here is the reverse-proxy snippet for completeness: ```auto location: /map { set $upstream http://ems:8080; proxy_pass $upstream; proxy_redirect off; proxy_set_header HOST $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $scheme; proxy_set_header X-Forwarded-Host $host/map; proxy_pass_request_headers on; proxy_set_header Authorization $http_authorization; proxy_pass_header Authorization; } ``` ---
**Author:** ![m.hanna](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@m.hanna](https://discuss.elastic.co/u/m.hanna)\ **Post date:** [December 28, 2023, 4:14pm UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/2 "2023-12-28T16:14:42Z")
I seem to have gotten it somewhat working. I removed the `BASEPATH` environment and modified the reverse proxy. My current proxy settings are: ```auto location: /map/ { proxy_pass http://ems:8080/; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "Upgrade"; proxy_set_header Host $host; } ``` This allows kibana to resolve the EMS server with `map.emsUrl: https:///map` set. But this has a downside in that I cannot use variables in the `proxy_pass` setting. If the EMS server is down, then my reverse proxy will not start because it will try to verify that [https://ems:8080](https://ems:8080) is accessible, so none of the other services will be reachable. Also, I cannot see any of the layers from the EMS UI. I am not convinced that is related to this issue; I might need to play with the reverse proxy settings some more. Also, I wonder why `basePath` didn't seem to work as intended. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [December 29, 2023, 10:28am UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/3 "2023-12-29T10:28:03Z")
hi @m.hanna thanks for reporting the issue, we'll take a look a this next week and get back to you with any findings. Thanks also for sharing your attempts as well, everything helps. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [December 29, 2023, 10:37am UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/4 "2023-12-29T10:37:42Z")
Can't check deeper now, but I did a quick test, and the `basePath` setting is working on my local environment (8.11) both as being passed as an environment variable and in the configuration file. Maybe it is better to contact your Elastic support representative to get a discussion where logs or other private details are better handled? Best regards. ---
**Author:** ![m.hanna](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@m.hanna](https://discuss.elastic.co/u/m.hanna)\ **Post date:** [January 3, 2024, 2:52pm UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/5 "2024-01-03T14:52:40Z")
Thanks for looking into it. It looks to me that the main issue with setting `basePath` is the that `/status` endpoint can no longer be resolved (I get a 404 instead of the expected 200). So then the healthcheck in the docker container fails. For running EMS with a regular docker compose, this just means that EMS will show as `unhealthy`, but will still start. In a docker swarm, however, EMS fails to start at all when the container is unhealthy. I will play around with adding my own healthcheck in the compose file and see if that resolves the issue. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [January 3, 2024, 3:44pm UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/6 "2024-01-03T15:44:26Z")
> [@m.hanna](#): > > In a docker swarm, however, EMS fails to start at all when the container is unhealthy. I will play around with adding my own healthcheck in the compose file and see if that resolves the issue. This is unfortunate ☹ We'll take a look to see if there's a fix we can add to ensure the healthcheck honors the basePath setting. Please, keep us informed if you can override it. ---
**Author:** ![m.hanna](https://avatars.discourse-cdn.com/v4/letter/m/b9bd4f/32.png) [@m.hanna](https://discuss.elastic.co/u/m.hanna)\ **Post date:** [January 3, 2024, 4:37pm UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/7 "2024-01-03T16:37:25Z")
Definitely looks like the heathcheck settings in the container. As a quick test, I added `BASEPATH=/map` back to the environment, changed the reverse proxy back to the original settings (first post), and then added ```auto healthcheck: disable: true ``` to my compose file and EMS started up fine. Not only does Kibana see the map server using the correct URL, but the EMS UI now also works as expected. ---
**Author:** ![jsanz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsanz/32/53734_2.png) [@jsanz](https://discuss.elastic.co/u/jsanz)\ **Post date:** [January 3, 2024, 4:52pm UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/8 "2024-01-03T16:52:38Z")
Glad that worked 🎉 We'll fix this issue and report back here when we know in which version exactly this is released. Feel free to ping us here anytime. Best ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 31, 2024, 4:53pm UTC](https://discuss.elastic.co/t/error-running-elastic-maps-behind-proxy/350082/9 "2024-01-31T16:53:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.