![]() ![]() This is a problem we have been experiencing since updating the servers last night. Once your user is removed, the server will not try to enforce anyone connecting with that username to have the certificate you initially registered with. If it's recent, you might have accidentally overwritten your old certificate by running the Certificate Wizard.Īnyway, a "fix" for this issue is to get an administrator to delete the registration for your user on the server using the Server -> Registered Users tool. If it's old, it's probably your usual certificate, and something's weird on the server-side of the server you're connecting to. Then, in the User Info dialog, click the 'Details' button for your certificate. If it is auto-generated, and thus hard to distinguish, one way to check whether your certificate changed is to connect to a random server, right-click on your user and chose 'Information'. Is there a certificate configured in your Mumble client?ĭo you still have our usual certificate configured in the Mumble client? (No, I'm not expecting you to remember the details of your certificate if it was auto-generated by Mumble). That is, if you attempt to connect using the username, but *without* using a certificate, OR using *another* certificate, you'll get the 'Wrong Password' error. Once it's stored there, Mumble will effectively use the hash of your certificate as your user's password. When you register your user with a Mumble server, the hash of the certificate is stored in the server's database. On first launch, Mumble will ask you to either import, auto-generate or manually generate a certificate for use with Mumble. The suggested method of authentication in Mumble is by using certificates. I'm also not sure how much you know about the Mumble user registration process, so I'll try to describe that as well. and next time, remember to import that certificate! It's important.The 'Wrong Password' error is a little ambiguous, because it doesn't only refer to passwords, but also certificates. Register with the server and ask the admin to regrant you the privs you previously had. ![]() When the admin tells you he's done deleting your account, log out, then log in with your "official" nick.While the admin processes your request, change your nickname to login anyway if you're in a hurry.Put it somewhere safe (say, Dropbox) for later retrieval. While he does that, open Configuration → Certificate wizard, then choose Export Certificate.(The relevant dialog can be reached via Server → Registered users.) Ask an admin of your server to delete your account.If you don't have the certificate anymore, because you probably never even knew about this whole thingadongdong, what you must do is: Select your certificate and continue you'll be able to login normally. If you still have it saved somewhere, import it: open Configuration → Certificate wizard, then pick Import certificate. With that certificate, you can only login with that username without that certificate, you cannot login with that username. When you registered, or were registered with your favourite server, what actually happened was a binding between your certificate and your nickname. ![]() That is your "password." You should've saved it somewhere safe, and reimported it when reinstalling Mumble. When you install Mumble for the first time, a certificated was created for you. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |