Document Actions
Unable to connect to Mumble server
Up to Support
Posted by
I have gone through the setup routine but cannot connect to server. Get following msg:
11:48:23 AM] Welcome to Mumble.
[11:48:36 AM] Connecting to server mumble.gridmotorsports.com.
[11:48:37 AM] Connected.
[11:48:37 AM] Server connection rejected: Invalid server password.
I am guessing this is a certificate issue, just don't know why.
Hey Bill, I'll look into this tonight when I get home, and see if the server logs give any better indication of what's wrong.
Bill, the server log doesn't say anything more than the message that you already saw. It's odd that 'server password' is even mentioned, because there is no server password.
And I looked at the user database, and you're not already registered, so it's not a mismatched user certificate.
If you're sure you went through the steps as described in the guide then I'm not sure what to suggest...
Here's what the mumble FAQ says:
http://mumble.sourceforge.net/FAQ#Server_connection_rejected:_Invalid_Password.
This simply means the server password was incorrect, next time make sure you type in the password in the password box on the connect window.
hmmm...maybe I did set a server password... if I did, it's the same as the one for teamspeak. If there's a server password, it must be that mumble only makes you provide it once, and then stores it for that server profile, because I don't have to provide a password when I connect now.
Previously David Hostetler wrote:
Here's what the mumble FAQ says:
http://mumble.sourceforge.net/FAQ#Server_connection_rejected:_Invalid_Password.
This simply means the server password was incorrect, next time make sure you type in the password in the password box on the connect window.
hmmm...maybe I did set a server password... if I did, it's the same as the one for teamspeak. If there's a server password, it must be that mumble only makes you provide it once, and then stores it for that server profile, because I don't have to provide a password when I connect now.
Typing in the current league password solved the problem. Thanks.