Skip to main content
FieldPal runs on Azure infrastructure that scales automatically, so its services do not sit behind fixed IP addresses. Firewall rules must be configured by DNS hostname, not IP address. IP-based allowlisting will break without warning when Azure reassigns the underlying addresses.
Do not allowlist FieldPal traffic by IP address or IP range. Azure autoscaling means these addresses change without notice, and IP-based rules will stop working unpredictably.
This guide lists the hostnames your network needs to reach for:
  • The FieldPal mobile app (Android), used by field workers
  • The FieldPal dashboard, accessed via browser by admins and managers

​
Required hostnames

All FieldPal traffic uses outbound HTTPS on port 443. No inbound rules are required, the app and dashboard only initiate connections outward.

​
Configuring your firewall

  1. Identify your firewall’s DNS-based (FQDN) filtering capability. Most enterprise firewalls (e.g. those supporting application or web filtering) support this; simple IP-only firewalls may not, and may need a proxy in front of them.
  2. Add each hostname in the table above to an allowlist for outbound HTTPS (port 443).
  3. If your firewall requires wildcard support to be enabled explicitly, confirm *.fieldpal.ai resolves correctly through it.
  4. Test from a device on the network by opening the dashboard URL and, on a mobile device already enrolled, checking a field worker can log in and sync a report.
If your organisation uses a web/content filtering proxy in addition to a firewall, hostnames may also need adding there. DNS-based firewall rules alone will not help if a separate proxy blocks the same traffic.

​
Verifying access

If the app or dashboard cannot connect after your firewall change:
  • Confirm DNS resolution for each hostname works from an affected device (nslookup dashboard.fieldpal.ai).
  • Confirm the firewall log shows the connection being allowed, not silently dropped.
  • Check for a separate proxy or endpoint security tool (e.g. an EDR agent) that may be blocking the connection independently of the firewall.
If access is still blocked after these checks, contact your FieldPal account contact with the hostname, timestamp, and firewall/proxy log entry so it can be investigated.