Project Reality Forums

I've not been able to play PR for about three months due to the fact that mumble just will not connect up

I've tried most of the solutions out there; Getting certificates, turning off quality of service, running as admin, compatibility mode, etc. I can't really think of anything else that I could have missed, so an ideas?

Hopefully it's not just me being a tard

142.56.165.196 port 64739

You can copy your shortcut to PRMumble. IN the new shortcut, edit the Target

from

"C:\Program Files (x86)\PR Mumble\pr_mumble.exe" mumble://[email protected]:64739/?version=1.2.0 -m

to

"C:\Program Files (x86)\PR Mumble\pr_mumble.exe" mumble://[email protected]:64739/?version=1.2.0 -m

Make sure to change the above to your actual location of PRMumble, I'm using the default file location in the example.

Make sure your firewall, antivirus, router firewall all allow passthrough UDP and TCP port 64739 and IP address of 142.56.165.196 .

I've done that, and I'm pretty sure my firewall should be letting me through, but the connection is timing out now

Let's see if PRmumble is able to connect to some public mumble servers...
1. Start PRmumble
2. Top Left corner, Select Server->Connect
3. The Server browser will be in new pop up window,
4. Expand the "Public Internet" list, and try to connect to a few servers.

It's possible you'll get kicked for using mumble version 1.2.0 instead of mumble version newer than 1.2.4, but there should be some servers that allow 1.2.0

Let us know if this works or not.

I get the disconnected by the remote host again. And when you say mumble 1.2.0 that's the regular mumble that PR mumble 1.0 is built on, right?

Bump.

Is there any solution? Not had any new ideas for a while now

Towll wrote:Bump.

Is there any solution? Not had any new ideas for a while now

If you want me to have a look through teamviewer (take control of your PC and troubleshoot myself) drop me a PM.

Ok so I jumped on teamviewer last night with Towll and it took us about an hour, troubleshooting various things.

In the end, through installing the latest vanilla version of mumble and confirming that worked, I ruled out a networking config issue and that pointed to a PRmumble config issue. The only thing I could think of was PRM network settings (which turned out to be fine) and as a last resort I checked his certificate.

He had a custom one made and so I made an new one from scratch for him. This resulted in Mumble being fixed.

So essentially it was an invalid/unacceptable certificate issue which resulted in every mumble server blocking his client.