Network Requirements

Share this page with your IT department before installation, when adding Basecamps, or when troubleshooting connectivity. It lists what the Basecamp needs from your network, and separately what staff and visitors need.

Basecamp (sync station)

The Basecamp initiates all connections itself. Nothing needs to reach it from outside.

Destination	Port	Purpose
api.guide-id.com	TCP 443 (HTTPS)	Configuration, content download, log upload, status and updates
syncboxdebug.guideid.com	TCP 443 (TLS)	Remote diagnostics — used only when Guide-ID support enables it for your device. Note the spelling: this host is not covered by *.guide-id.com
connectivitycheck.gstatic.com	TCP 443, TCP 80	Optional — internet and captive-portal check
NTP servers (Debian pool)	UDP 123	Optional — time synchronization

api.guide-id.com is the only destination the Basecamp needs for normal operation. We recommend allowing the two optional destinations, but the Basecamp keeps working without them:

• connectivitycheck.gstatic.com is only contacted when Guide-ID cannot be reached. It lets the Connection LED tell a blocked or unreachable Guide-ID (steady orange) apart from a broken internet connection (red), and it detects login pages. If you block it, a blocked Guide-ID shows as red with five flashes, just like an internet outage, which makes troubleshooting harder.
• NTP keeps the clock exact. Without it, the Basecamp sets its clock from Guide-ID’s responses.

Requirements:

• DHCP (IPv4) with a gateway and DNS server — static IP addresses are not supported
• No inbound ports and no port forwarding; remote diagnostics use a tunnel opened by the Basecamp itself
• Captive portals (browser login pages) are not supported
• Ethernet (RJ-45) is preferred. Wi-Fi is 2.4 GHz only (802.11 b/g/n), secured with a passphrase (WPA2 or WPA3 Personal). WPA-Enterprise (802.1X) is not supported; a Wi-Fi Basecamp is configured through its own hotspot — see Installing Your Basecamp
• Proxy: supported through automatic discovery (WPAD via DHCP option 252 or a wpad DNS entry) or a PAC file; the proxy must allow HTTP CONNECT to port 443. Manual proxy settings are configured by Guide-ID support. Authenticating proxies: basic authentication only.
• MAC filtering: the Basecamp’s Ethernet and Wi-Fi MAC addresses are shown in the Platform when you add the Basecamp (step Details → Network Info)

Staff (Platform in the browser)

Destination	Purpose
platform.guide-id.com	The Platform — tours, hardware, insights
account.guide-id.com	Login

Standard HTTPS (TCP 443) from your office network is sufficient.

Visitors (web app on their own phones)

Destination	Purpose
app.guide-id.com	The visitor web app (PWA)

If you offer the web app on your guest Wi-Fi, allow this domain for visitors as well.

Tip

The simplest firewall rule that covers everything above except the two non-Guide-ID hosts is: allow outbound HTTPS to *.guide-id.com. Add syncboxdebug.guideid.com explicitly, and preferably connectivitycheck.gstatic.com and NTP as well.

Related articles

• Installing Your Basecamp — physical Basecamp setup
• Basecamp Network Issues — troubleshoot connectivity problems