# Map Issue in Kibana 6.0.0
**URL:** https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360
**Category:** Kibana
**Created:** [December 5, 2017, 1:21pm UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360 "2017-12-05T13:21:35Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@adwaitjoshi](https://discuss.elastic.co/u/adwaitjoshi)
#### Post date: [December 5, 2017, 1:21pm UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/1 "2017-12-05T13:21:35Z")
Hey Guys,
I just installed Kibana 6.0.0 on a server and having a problem loading Maps. It errors out with the error "could not receive manifest from tile service". I am assuming this is because Kibana cannot load the maps. Its possible because the server is in a datacenter behind some firewalls. I have DNS configured on the machine so generally outgoing connections are not an issue. But not all incoming connections work. Does anyone know how to solve this?
Regards,
Adwait
---
### Author:  [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [December 5, 2017, 6:50pm UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/2 "2017-12-05T18:50:02Z")
Hi @adwaitjoshi,
Kibana by default uses the [Elastic Maps Service](https://www.elastic.co/elastic-maps-service) to load the tiles and other assets from. So it either requires access to the service's servers (e.g. `tiles.elastic.co`) or needs to be configured with a locally hosted map server instead. Some users who don't need maps also choose to blackhole the tile service's DNS to localhost or similar.
---
### Author:  [@adwaitjoshi](https://discuss.elastic.co/u/adwaitjoshi)
#### Post date: [December 6, 2017, 12:21am UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/3 "2017-12-06T00:21:30Z")
Where would this configuration be stored and what should I be testing to make sure that the communication actually works. All outgoing connections are allowed but no incoming connections are. So if this is a request that receives a response, it should come back fine. But I would have to test the ports and urls.
---
### Author:  [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [December 6, 2017, 10:51am UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/4 "2017-12-06T10:51:30Z")
You can configure it in your `kibana.yml` with the setting `tilemap.url`. See [the docs](https://www.elastic.co/guide/en/kibana/current/settings.html) for a list of all settings.
The urls used by default by the tile map should start with `https://tiles.maps.elastic.co` and `https://catalogue.maps.elastic.co`.
---
### Author:  [@adwaitjoshi](https://discuss.elastic.co/u/adwaitjoshi)
#### Post date: [December 6, 2017, 1:52pm UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/5 "2017-12-06T13:52:31Z")
Reading through the setting it says Kibana read this from an external metadata service. Do you know what that URL is? I want to make sure I can hit it. Also if I do change the url to something would it be changed to whats below? the [tiles.elastic.co/v2](http://tiles.elastic.co/v2)...?
> The URL to the tileservice that Kibana uses to display map tiles in tilemap visualizations. By default, Kibana reads this url from an external metadata service, but users can still override this parameter to use their own Tile Map Service. For example: "[https://tiles.elastic.co/v2/default/{z}/{x}/{y}.png?elastic\_tile\_service\_tos=agree&my\_app\_name=kibana](https://tiles.elastic.co/v2/default/%7Bz%7D/%7Bx%7D/%7By%7D.png?elastic_tile_service_tos=agree&my_app_name=kibana)"
---
### Author:  [@adwaitjoshi](https://discuss.elastic.co/u/adwaitjoshi)
#### Post date: [December 7, 2017, 2:37pm UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/6 "2017-12-07T14:37:23Z")
Hello,
Just checking in again to see. I can successfully ping both [tiles.elastic.co](http://tiles.elastic.co) and [tiles.maps.elastic.co](http://tiles.maps.elastic.co) maps still wont load with the error
region map could not receive manifest from tile service status -1
What else can I try?
Adwait
---
### Author:  [@weltenwort](https://discuss.elastic.co/u/weltenwort)
#### Post date: [December 7, 2017, 5:51pm UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/7 "2017-12-07T17:51:10Z")
The metadata service should be the `https://catalogue.maps.elastic.co` url I mentioned. You can try to use the browser devtools to check which external requests Kibana makes when displaying a map visualization.
---
### Author:  [@adwaitjoshi](https://discuss.elastic.co/u/adwaitjoshi)
#### Post date: [December 7, 2017, 6:42pm UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/8 "2017-12-07T18:42:07Z")
That showed the underlying issue. The server was making the request OK. But my local machine was blocking it. I solved it!!! Thank you so much for your time and help.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 4, 2018, 6:46pm UTC](https://discuss.elastic.co/t/map-issue-in-kibana-6-0-0/110360/9 "2018-01-04T18:46:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.