NEW 📢 Black Friday: our launch offer ends 30 Nov. Up to 70% off your first month on every game!See plans
Black FridayUp to 70% off your first month, ends 30 NovEnds in 9d 04h 25mBlack FridayUp to 70% off your first month, ends 30 NovEnds in 9d 04h 25mBlack FridayUp to 70% off your first month, ends 30 NovEnds in 9d 04h 25m

Mumble certificate warnings explained

Mumble and voice serversUpdated Nov 6, 20264 min read

Mumble encrypts every connection. Each server has a certificate, and each user has one too. That is where the warnings come from.

The first time you connect to a server

The Mumble app says Server presented a certificate which failed verification., lists the reasons and asks whether to accept the certificate anyway. This is normal for a server that made its own certificate, which is what a Mumble server does on its first start when nobody gave it one. We checked one of our servers: its certificate is self-signed, named Murmur Autogenerated Certificate v2 and valid for 20 years.

If you typed the address from your panel's Overview, choose Yes. You can press View Certificate first to see it. The app stores the certificate for that address and port and does not ask again for that address.

A warning later: certificate changed

If the app says WARNING: The server presented a certificate that was different from the stored one., the server's certificate is not the one you accepted before. It shows both fingerprints.

  • A Mumble server that made its own certificate keeps it inside its database file (on PlayNHost murmur.sqlite). In our test it stayed the same after a restart. It changes when that file is deleted or replaced, for example when the server's files were wiped and the server started fresh.
  • If the server owner tells you that is what happened, accept the new one. If nobody changed anything and you are not sure, ask the server owner before you accept.
  • Connecting by a different address (an IP address instead of a name, or a different port) also asks again, because the app stores certificates per address and port.

Your own certificate

The Mumble app identifies you with a personal certificate. The first time it starts it opens the Certificate Wizard; if you close it without making one, the app creates a certificate by itself and saves a backup file named MumbleAutomaticCertificateBackup.p12. Once you are registered on a server, that certificate is how the server knows it is you.

  • Back it up: Configure, Certificate Wizard, export the current certificate. Keep the file safe.
  • If you lose it, the server no longer recognises your registered name: logging in with it gives Wrong certificate or password for existing user. An admin has to remove the old registration under Server, Registered Users; then you register again and the admin adds you back to your groups.
  • To use the same account on another computer, import the exported file with the same wizard.

Can the warning be avoided?

Yes, with a certificate from a public authority such as Let's Encrypt for a domain name that points at the server. Mumble's server config has sslCert and sslKey for that, and the -acme version of Mumble's official Docker image can request and renew one by itself. The app only shows the warning when the certificate fails verification. On a PlayNHost Mumble server these settings are not offered in the panel, so each person accepts the certificate once per device.

Related: Cannot connect to your Mumble server: fixes.

Already hosting it somewhere else? Move your server to us

OUR LATEST BLOGS