mashgin

Kiosk

Understanding the Kiosk Network Test

Reference guide to the kiosk's built-in Network Test — what each check is verifying and how to read pass/fail results before troubleshooting.

📋 Overview


The Network Test runs from Staff Mode > Manage > Network > Test and checks the kiosk's connectivity to the local network and to Mashgin's servers. Each check verifies a different layer of the connection, so the pattern of passes and failures tells you where the problem is, not just that there is one.

Run this test any time:

  • A Kiosk Offline alert appears
  • Transactions or items aren't syncing
  • You've changed network settings (Static IP, DHCP, VLAN, etc.) and want to confirm the kiosk is still reachable
Reference: Full Network Test results in Staff Mode

🔍 How to Read the Results


Step 1. Run the Test

  1. Open Staff Mode and go to Manage > Network
  1. Open Test
  1. Tap Run Tests and wait for each check to complete

Each check shows a green check with Yes (pass) or a red mark with No (fail).

Step 2. Interpret What Each Check Is Verifying

The checks are grouped into Local Network, Mashgin Services, and Firewall / Ports — running from "closest to the kiosk" outward. A failure usually points to whichever layer is broken, and the first failing check is normally the root cause.

Check
What it verifies
Most common cause of failure
Network link
The Ethernet port is up and the cable is detected
Loose or unplugged cable; failing port
IP valid
The kiosk has a valid IP address
DHCP server not responding; Static IP misconfigured
DHCP lease
The kiosk obtained a DHCP lease
No DHCP server, or an exhausted scope (not used on Static IP)
Config applied
The saved network config is active
A pending or failed change — re-open Ethernet and tap Save
Gateway reachable
The kiosk can reach the local router/gateway
Wrong gateway address; switch or router issue
Link stability
The link is stable with no rx/tx errors
Flaky cable, port, or a duplex mismatch
Check
What it verifies
Most common cause of failure
Mashgin cloud reachable
The kiosk can reach Mashgin's cloud
Firewall blocking Mashgin domains; cloud-side issue
VPN server reachable
The kiosk can reach the VPN server
Firewall or ISP blocking the VPN
Grid reachable
The kiosk can reach the Grid service
Firewall or routing blocking the grid IPs
VPN connected
The secure VPN tunnel is up
"Block QUIC" / UDP rules; VPN handshake blocked
Check
What it verifies
Most common cause of failure
Grid servers reachable
All required grid servers respond (e.g. 5/5)
Some grid IPs blocked at the firewall
UDP egress
Outbound UDP (WireGuard VPN) is allowed
UDP/443 blocked by "block QUIC" rules
💡

The first check that fails is almost always the root cause — the checks after it tend to fail as a consequence. Fix the earliest failure first, then re-run the test.

🔗

The test also lists the Required Endpoints (the grid IPs and Mashgin domains, with their ports) at the bottom. Share these and the Network Architecture Guide with the site's IT team so they can allowlist them.

Step 3. Take Action Based on the Result

  • All Yes ✅ Connectivity is healthy.
    • If an alert is still showing, give it 30–60 seconds to clear, then power cycle if needed.
  • Local Network passes but Mashgin Services or Firewall / Ports fail:
    • The kiosk's local network is fine, but a firewall is likely blocking Mashgin's domains or outbound UDP. This is an upstream networking issue the site's IT team needs to resolve.

💡 Tips


💡

Always re-run the Network Test after each change you make during troubleshooting — it's the fastest signal that the fix worked.

⚠️

An intermittent failure (passes some runs, fails others) usually indicates a flaky cable, port, or upstream switch. Replace the cable as a first move — it's the cheapest fix and the most common culprit.

🔗 Related Articles


🖐️

Need help? Contact support at 📧 help@mashgin.com or call (855) 475-0889

Did this answer your question?
😞
😐
🤩