Vizito runs in the cloud. The tablet, the backoffice and the visitor’s own phone all talk to Vizito over HTTPS, so on most networks nothing needs to be configured. This page is for the IT department of a site with a firewall, a web proxy or a locked-down guest network.
Hosts to allow
Everything is outbound, over TCP port 443 (HTTPS). Vizito never opens a connection into your network; the only traffic from Vizito to you is the webhooks you configure yourself, delivered to a public address of your choosing.
| Host | Used by | What for |
|---|---|---|
| backoffice.vizito.be | Your staff’s browsers | The backoffice |
| frontoffice.vizito.be | The tablet | The kiosk app and its live updates (a websocket, wss://, on the same host) |
| api.vizito.be | Your own integrations | The API, webhooks are sent from here |
| m.vizito.be | Visitors’ phones | Contactless sign in and static QR codes |
| p.vizito.be | Visitors’ phones and PCs | Pre-registration and self-registration |
| vizito.nl.object-storage.io | Tablet, backoffice, phones | Your logo, splash images, agreement documents and visitor photos |
| vizito.eu | Tablet and backoffice | The help center and the activation shortcut |
If your firewall filters by category rather than by host, these are business web applications. No other ports are needed: badge printers are reached on your own local network, not through Vizito.
Email from Vizito comes from vizito@vizito.be, or from your own address once you have set it up under “Account settings” > “General” > “Email address FROM”. Ask your mail administrator to allow that sender if host notifications or invitations land in quarantine. See Invitations.
Behind a corporate proxy
- Proxy without TLS inspection: works as it is.
- Proxy with TLS inspection: the tablet has to trust the proxy’s certificate, as it would for any HTTPS site. If the kiosk shows “Your tablet is offline. Check the network settings and try again.” although the tablet browses the web, ask your IT department to exclude the hosts above from inspection.
- Websockets blocked: the kiosk keeps working. It receives changes from the backoffice the moment they are saved through the websocket; without it, the changes arrive the next time the app returns to the welcome screen, and the activation token is picked up by polling. See Device activation.
- Authenticated proxies: the kiosk app cannot prompt for proxy credentials. Put the tablet on a network segment that reaches the hosts above without authentication.
Guest Wi-Fi
A guest network is often the wrong place for a reception tablet:
- Captive portals ask for a click or a login when the session expires. A kiosk cannot answer that, and it goes offline until somebody does. Use a network without a portal, or exempt the tablet’s MAC address.
- Client isolation stops devices on the guest network from seeing each other, so the tablet cannot reach a label printer on the same Wi-Fi. Put the tablet and the printer on the same network without isolation, or connect the printer over Bluetooth. See Brother QL-820NWB setup.
- Bandwidth is not an issue. A sign in is a few kilobytes; only agreement videos and splash images are larger, and they are cached on the tablet.
Visitors who sign in on their own phone use their own connection, so nothing on your network matters for them apart from mobile coverage at the door.
Printers
The tablet prints straight to the printer over the local network or over Bluetooth. Give a network printer a fixed IP address or a DHCP reservation, keep it on the same subnet as the tablet, and do not enable client isolation between them. Nothing about printing goes through Vizito’s servers except the badge image itself, which the tablet fetches from frontoffice.vizito.be.
Checklist for a new site
- Tablet on a Wi-Fi without captive portal, reaching the hosts above on port 443.
- Backoffice PCs reaching backoffice.vizito.be.
- Printer on the same network as the tablet with a fixed address, or paired over Bluetooth.
- Mail from vizito@vizito.be, or your own FROM address, allowed by your spam filter.
- For integrations: your server reaching api.vizito.be, and your webhook endpoint reachable from the internet.
Still stuck? Contact us through the chat in the backoffice or at info@vizito.eu with the network setup and, if possible, the message the tablet shows.