The proposed authentication method in mumble lies in the use of certificates. At the initial launch, mumble will prompt you to import, automatically generate or manually generate a certificate for use with mumble.
If you register your user in mumble server, the hash of the certificate is stored in the server information archive. After the order is saved there, mumble will effectively use the hash of a specific diploma as your user's password. Therefore, in the event that you attempt to connect using a login, but in the absence of * using a certificate or using *another * diploma, you will receive an error message "incorrect password".
Is there a certificate configured in your mumble client?
Personally, do you still have access to our regular certificate configured in the mumble client? (No, i don't expect you to remember the subtleties of the ordered certificate if it was automatically generated by mumble).
Since the resource is generated mechanically and naturally, it is difficult to distinguish it, one of the sources to check whether your diploma has changed is to connect to a random server, right-click on the business user and select "information". After that, in the "user information" dialog box, click the "data for a specific crust. Then check the "valid until" date..
In that situation, if it is old, then it is probably an excellent ordinary certificate, as well as something strange is happening on the server side to voice servers which you are connecting. If it was created recently, you probably accidentally overwritten your old certificate by running the certificate wizard...
In spite of everything, the "correction" of such a mess boils down to forcing the administrator to delete your client's registration on the site using the server -> visitors that have registered tool. After your user is deleted, the server will not try to force everyone who connects with that username to own the diploma with which you originally registered.