Network guide

Give your IT team the app and API hostnames below. The kiosk needs outbound connections; it does not accept inbound connections or receive push alerts.

On this page

Before you start

Ask your IT administrator to make network changes. Have this environment's hostnames, the affected location and the error message ready. Proxy and certificate policies depend on your device management.

Kiosk Wi-Fi

Use working DNS and outbound HTTPS on TCP port 443. Avoid captive portals that ask for a network sign-in after the kiosk is mounted. The network must trust the site's TLS certificates; coordinate any inspection certificates with your device administrator.

App updates

Native kiosks also need u.expo.dev and assets.eascdn.net for app updates. If those hosts are blocked, the installed kiosk may continue working but will not receive those updates. Allow the device's App Store or Play services through your normal device-management policy.

Staff on restricted Wi-Fi

In addition to the app and API, sign-in needs securetoken.googleapis.com and identitytoolkit.googleapis.com. Microsoft sign-in uses login.microsoftonline.com; Google sign-in uses accounts.google.com and oauth2.googleapis.com. Native alert registration uses exp.host. Staff devices also need their operating system's push service or the browser's push endpoint.

Troubleshoot in order

Check power and Wi-Fi, then open the app from the same network and run the connection check. Try a different approved network to isolate a firewall issue. Ask IT to check DNS, captive portals and blocked HTTPS. Give your administrator the error code and affected location; do not send visitor details.

Production hostnames

app.ovatello.com · api.ovatello.com

Related help