When navigating to the Home or Physical Data Center views in VCF Operations, the map fails to render. You may observe the following symptoms:
curl) to tile.openstreetmap.org or tile.jawg.io via a proxy appear successful (HTTP 200), but the map still does not load in the browser.VCF Operations 9.x
The map functionality in VCF Operations relies on several specific subdomains to retrieve map tiles. Even if primary domains are whitelisted, the map will fail to render if the browser cannot reach individual tile servers (subdomains a, b, c, or d) through the network proxy or firewall.
Additionally, because the map is rendered by the browser, the machine or jump server used to access the VCF Operations UI must have direct or proxy-based access to these subdomains.
Ensure that the machine or jump server used to browse the VCF Operations UI has access to all required map tile endpoints on port 443.
Ensure the following Fully Qualified Domain Names (FQDNs) are whitelisted in your firewall or proxy:
a.tile.jawg.iob.tile.jawg.ioc.tile.jawg.iod.tile.jawg.iotile.openstreetmap.orgTo confirm the subdomains are accessible from your browsing machine:
https://a.tile.jawg.io). If successful, you should see a map tile image or a service response rather than a connection error.curl to test connectivity to specific subdomains via your proxy: