Cannot connect to your Mumble server: fixes

Work down this list. Most connection problems are one of the first three.

1. Is the server running?

Open your server in the panel. It must show Online. If it is Offline, press Start. See How to start, stop, restart and force-stop your server.

2. The address and the port

On Overview the Connect address is shown as address:port. Both parts matter, and the port is not the Mumble default. In the Mumble app, Server, Connect, Add New, enter the address in Address and the number in Port. A wrong port gives Connection refused or timed out. See How to connect to your Mumble server.

3. Server password

If you set a join password, Mumble asks for it. A wrong password shows an Invalid server password message. See How to set a join password.

4. Server full

The message Server is full means every slot is taken. Your plan sets the limit. See How many slots does a voice server need.

5. Your network

• A VPN or school or work network can block the port. Try a mobile hotspot to test.
• Mumble uses TCP for control and UDP for voice on the same port. If voice is missing but you connect, a router or firewall is blocking UDP. Mumble then falls back to sending voice over TCP, which is fine but can add delay.
• Antivirus or a Windows firewall prompt may need allowing for the Mumble app.

6. Certificate warnings

The first time you connect, Mumble shows a certificate it does not know. Accept it. See Mumble certificate warnings explained.

7. Old client

Use a current Mumble version. A very old client may not connect to a modern server.

If none of this works, open a ticket with the exact message and the time: How to open a support ticket.