Mumble certificate warnings explained

Mumble encrypts everything. 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

Mumble shows the server's certificate and asks if you trust it. A new PlayNHost server makes its own certificate, so Mumble does not recognise it. If you typed the address from your panel, accept it. Mumble remembers the certificate for next time.

A warning later: certificate changed

If Mumble says the certificate changed for a server you already trust, the server's certificate was replaced. This happens when the server's files were deleted or restored from an older backup. If you did that, accept the new one. If you did not and something feels off, check with the server owner before accepting.

Your own certificate

Mumble creates a personal certificate for you the first time you start the app. It is how the server knows who you are once you are registered.

• Back it up: Configure, Certificate Wizard, Export. Keep the file safe.
• If you lose it, you lose the registered account on every server, and a server admin has to give you the rights again.
• To use the same account on another computer, import the exported file with the same wizard.

Good to know

• You cannot fix a certificate warning on the server by buying one. Mumble does not rely on public certificate authorities for this.
• If a SuperUser or admin tells people to ignore every warning, be careful: accept only for the address you expect.

Related: Cannot connect to your Mumble server: fixes.