What ports and IP addresses does my device need access to?
We use a number of services to provide Kiosk Browser/Launcher Remote Management.
Heartbeat & REST API: TCP 443 - *.kbremote.net (CloudFlare)
Mobile Backend (2.6.4 or lower only): TCP 443 - kbremote.azure-mobile.net multiple ip addresses (legacy)
Push (FCM): TCP 5228-5230, 443 - outbound - multiple ip addresses (Google's ASN of 15169)
Fallback for Push (Pushy): TCP 443 - *.pushy.me & *.pushy.io
Storage: TCP 443 - kbremote.table.core.windows.net kbremote.blob.core.windows.net
Authentication (Remote Management UI): TCP 443 *.auth0.com
Heartbeat/Configuration: TCP 443 - klrfunction.queue.core.windows.net, klrfunction.blob.core.windows.net & kioskapi.azure-api.net
App Updates: TCP 443 - klremote.blob.core.windows.net
Push (FCM): TCP 5228-5230, 443 - outbound - multiple ip addresses (Google's ASN of 15169)
Fallback for Push (Pushy): TCP 443 - *.pushy.me & *.pushy.io
Authentication (Remote Management UI): TCP 443 *.auth0.com
Classic Remote Management
Heartbeat & REST API: TCP 443 - *.kbremote.net (CloudFlare)
Mobile Backend (2.6.4 or lower only): TCP 443 - kbremote.azure-mobile.net multiple ip addresses (legacy)
Push (FCM): TCP 5228-5230, 443 - outbound - multiple ip addresses (Google's ASN of 15169)
Fallback for Push (Pushy): TCP 443 - *.pushy.me & *.pushy.io
Storage: TCP 443 - kbremote.table.core.windows.net kbremote.blob.core.windows.net
Authentication (Remote Management UI): TCP 443 *.auth0.com
Unified Remote Management
Heartbeat/Configuration: TCP 443 - klrfunction.queue.core.windows.net, klrfunction.blob.core.windows.net & kioskapi.azure-api.net
App Updates: TCP 443 - klremote.blob.core.windows.net
Push (FCM): TCP 5228-5230, 443 - outbound - multiple ip addresses (Google's ASN of 15169)
Fallback for Push (Pushy): TCP 443 - *.pushy.me & *.pushy.io
Authentication (Remote Management UI): TCP 443 *.auth0.com
Updated on: 15/05/2023
Thank you!