Troubleshoot Profinity Mobile

This page lists the discovery, certificate, and sign-in problems that Profinity Mobile can show, with the remedy for each. To set up discovery first, refer to Connect Profinity Mobile to a server.

Issue	Remedy
No servers in the list	Confirm that Send Profinity Heartbeat is on, that the phone and server are on the same subnet, that the firewall allows UDP port 49025, and that the network does not block broadcast traffic between Wi-Fi and wired segments or VLANs
No servers in the list, and Profinity runs in Docker	UDP broadcasts do not leave a Docker bridge network, so run the container with host networking on Linux (refer to Docker Installation)
Android emulator list is empty	Emulators cannot receive LAN broadcasts, so use a physical phone
Certificate warnings	Install a trusted HTTPS certificate on the server, or accept the prompt once per server
SSO does not complete	The site must use the Sso sign-in method, and the identity provider (IdP) sign-in is completed in the app's embedded browser

For single sign-on setup, refer to SSO and Sign-In. For the server-side discovery settings, refer to Discovery.