Intercom: Host setup for phones

Host setup for phones

1. Open Mobile browser access · host settings in Intercom. Set a reachable,

trusted HTTPS origin, for example https://crew.example.com:8917.

2. For direct access, choose the matching PEM certificate chain and unencrypted

private key for that hostname. Phones must trust the issuing CA and hostname. Self-signed desktop certificates are not sufficient for normal mobile access. Certificate files stay in the host’s private Intercom data directory.

3. Alternatively, use a dedicated trusted HTTPS reverse proxy that forwards to

this host’s HTTPS signaling port, 8917 by default. Preserve the external Host header (including its port), cookies and Origin header. Forward /mobile, /api/local, /api/control and the page’s static assets. Use a dedicated origin, not a URL subdirectory. The proxy must explicitly trust the upstream host certificate; do not publish the loopback desktop UI on port 8916.

4. Save before starting a room. Start the room as usual, then share **Join from a

phone** using its QR code or mobile link. The invitation is in the URL fragment and is not sent to the web server in the page request. Share only with crew.

5. On the phone, open the link, enter a crew name, tap Join crew, allow the

microphone prompt, then unmute or select Hold to talk. If no prompt appears, check that the address is trusted HTTPS and enable microphone access in that browser’s site/device settings. Embedded social-app browsers may need Open in Safari/Chrome. A desktop invitation alone cannot supply trusted HTTPS.

All devices must reach the HTTPS address. Across different networks, configure STUN/TURN under the host’s remote network settings, plus appropriate firewall and DNS routing. HTTPS transports signaling; WebRTC audio connectivity still requires working network paths or TURN. There is no hosted internet relay included.