Official Mumble VoIP Forums

I think I already posted (all of) my ideas of where to debug/what to look for. I checked the code. It looks like it is a SocketError - so within the mumble client we do not have more information than only that. The Qt SocketError class Lists `QAbstractSocket::RemoteHostClosedError` described as The ...
ICE has traditionally been our remoting API for that. Back when we added it it was the best/only good choice. For Mumble servers Ice functionality you can check the slice docs at http://mumble.sourceforge.net/slice/1.3.0/Murmur.html You will want to get a users state information and set the channel ...
I’m not quite sure what you are describing. The in game overlay worked fine for a while, then suddenly became grey? Do you have a screenshot of that? Does relaunching the game fix it?
Sorry for the delayed reply. I tried to find out if our server logs anything. Our registry server does answer with some error information on issues, which I was told should be sent as a reply to the client. I am not sure/I have not verified if the client (in this case the Mumble server) is logging t...
No, I don’t think I’ve ever heard of that specifically. Although it is a pretty generic description, and people do sometimes have issues with their networking.
What's needed to overcome this error? You did not say what your error actually is. The servers side can give information on why the connection is dropped, or at least that is indeed a client side issue rather than server side. I guess as you installed your new router, it is likely that it does some...
Hello NarrowMinded, I will gladly answer your technical interest. :) Mumble introduced user certificates as a better alternative to passwords a long time ago. Using a user certificate also means the public key signature can be shared across servers and other clients, while the private key part remai...
No, I am not aware of any IP blacklist on our public server list server.
Generally, I don't think it should be necessary to forward ports on the client side. Only server side. Because your client initiates the connection, to the servers listening port on TCP. Routers generally allow response packets after a client initiated a connection. The client TCP port is (probably?...
Hm, that sounds pretty strange indeed. Being able to see the ping and user count shows that network packets in general do get through. So connecting to the server should work fine. Can you yourself or ask the server admin to check the server log, if the server logs any reason why you disconnect? Or ...