Ports and networking

For the maintained Starling Compose deployment, expose 64738/TCP for the Mumble control connection and 64738/UDP for voice. A classic Mumble client sends UDP to the same host and port it used for TCP. The gateway handles the TCP socket and the voice service handles UDP.

The Compose file also publishes 8080/TCP for HTTP file transfers. Its sample public_url points to localhost; replace that URL with an address your users can reach, normally HTTPS through a reverse proxy. File links cannot work for remote clients while they point at localhost.

Screen-share media uses a separate UDP listener when the relay is configured. Set the screenshare service public_url to a reachable literal IP and port; open that UDP port in your firewall. The example TOML shows the relevant settings.

The optional operator API is plain HTTP and should remain on a trusted network. The Compose admin profile binds its port 8081 to the host loopback interface. See the operator API guide before exposing it through a proxy.

Internal gRPC service endpoints are for Starling components, not public client ports. See Ports and protocols for a compact list.