If the Nx Maps application cannot connect or receive a response behind a restrictive firewall, you must add specific domains and ports to your firewall's outbound allow list.
Nx Maps uses distributed, dynamically allocated servers instead of a fixed set of IP addresses. Because of this dynamic routing, you must allow traffic by domain name and port rather than by static IP addresses.
| NOTE: Because Nx Maps relies on the Nx Cloud to function, please review the recommended configurations in THIS article. To ensure uninterrupted service, verify that all FQDNs listed there are added to your firewall's passlist. |
Required ports
Nx Maps traffic relies on the following ports for secure and standard web communication:
Port 443 (HTTPS): The primary port. All requests to load maps, tiles, styles, or perform geolocation go through secure HTTPS traffic.
Port 80 (HTTP): Used primarily for initial redirects, though almost all operational traffic is forced to HTTPS.
Allowed domains
To simplify configuration, most corporate firewalls allow you to use wildcards. If your firewall supports wildcards, add the following two rules for outbound traffic on port 443:
*.nxvms.com*.mapbox.com
Explicit domain list
If your firewall does not support wildcard matching, you must explicitly allow the following individual domains:
Standard domains
maps.nxvms.commapbox.comapi.mapbox.com
Additional subdomains and tile servers
mapbox.comapi.tiles.mapbox.coma.tiles.mapbox.comb.tiles.mapbox.comc.tiles.mapbox.comd.tiles.mapbox.comevents.mapbox.com
Comments
0 comments
Article is closed for comments.