Android Device Whitelisting Guide (Microtouch w/ Esper)
Last updated: August 8, 2026
What are the domains/IP addresses that I need to whitelist for my GRUBBRR device(s) to function?
The table below lists the essential whitelisting options for your GRUBBRR kiosk.
| Address(es) | Ports | Function |
| portal.grubbrr.com | 443 | Allows the kiosk to download data from and upload data to the GRUBBRR Portal |
| pushy.me | 443 | Allows the kiosk to receive notifications from the GRUBBRR Portal |
|
13.248.224.0/24 | Allows the kiosk to communicate with media storage servers. These host the kiosk screensavers, images, and other UI elements of the kiosk software. | |
| *.amazonaws.com | TCP: 443 (HTTPS), TCP: 8883 (MQTT) | Allows the kiosk to download updated software versions from application storage servers. |
| mqtt.shoonyacloud.com | TCP: 1883 (MQTT) | Allows MQTT communication with the kiosk |
| services.shoonyacloud.com | TCP: 443 (HTTPS) | Provisioning services and Remote Viewer APK |
| turn.shoonyacloud.com | TCP/UDP: 3478 (SCTP), TCP/UDP: 5349 (SCTP), UDP: 49152 - 65535 | For Remote Viewer and Remote Control services |
| dpcdownloads.esper.cloud | TCP: 443 (HTTPS) | For the 6-tap QR code method of provisioning and Remote Viewer APK |
| grubbrr.esper.cloud | TCP: 443 (HTTPS) | Grants access to the Esper Console when operating under a network with a restricted outbound firewall |
| grubbrr-api.esper.cloud | TCP: 443 (HTTPS) | For communicating from the device to the Esper Endpoint. (example: device status events and command success/failure messages) |
| mqtt-telemetry-prod.esper.cloud | TCP: 1883 (MQTT) | Deep telemetry from devices |
| 13.52.132.230 | TCP: 40000 - 50000 | Allows secure remote ADB access to the kiosk |
|
fcm.googleapis.com | TCP: 443 (HTTPS), TCP: 5228 (HTTPS), TCP: 5229 (HTTPS), TCP: 5230 (HTTPS) | Backup channel, also used for ping command to wake up a device (Only for GMS devices) |
|
firebasestorage.googleapis.com mqtt.googleapis.com | 443 | Enables Remote Assistance through Microtouch |