Cannot connect to any mumble servers, remote host closed connection

Help
strem
2014-04-20
2014-06-07
1 2 3 4 > >> (Page 1 of 4)
  • strem
    strem
    2014-04-20

    I tried alot of shit, restarting router, reinstalling mumble, redoing certificates multiple times, changing username, downgrading mumble, updating mumble, fuckin everything.

    I have tried to find a fix with an admin of a mumble server, he says that my IP is simply timing out. I cannot connect to any servers whatsoever and I assume that I simply time out on every server I try to connect to. I have tried to delete every mumble folder on my computer and reinstalling, that didnt work. If I try to use a proxy, it will no longer tell me "Connection failed: remote host has closed the connection" but it will just say "Disconnected from server."

    pls help

     
    • Noah Patterson
      Noah Patterson
      2014-05-22

      I'm having the same issue. It started last Saturday, after working just fine Friday night.
      I cannot connect to any server, not the one I use for my game group, or any server chosen at random, the result is always a long "connecting" followed by disconnecting and "remote host closed connection".

      In attempting to resolve the problem, I have tried the following:

      • upgrading from 1.2.5 to 1.2.6
      • changing my name
      • uninstalling, deleting all Mumble folders I can find (in Programs x86 and AppData/Roaming) doing registry repair, re-installing
      • deleting and re-entering the server info
      • unchecking QoS
      • checking Force TCP Mode
      • running as Admin
      • connecting to commonly used port numbers on a back up server run by the person who maintains our group server, and he says he sees my IP timing out every attempt
      • port forwarding
      • booting in safe mode with networking and trying to connect
      • disabling firewall and AV
      • making sure Mumble.exe is allowed through the firewall and AV
      • connecting directly to the modem rather than the router
      • generating new certificates
      • tracert and ping tests show no interferences

      I installed Mumble on my wife's computer, which connects to the same router, and her client connects instantly, so it's not a matter of the port being blocked by the ISP. She's on Win7, I'm on Win8.1, with new this year hardware, her system is a few years old.

      I'm at a complete loss as to what the problem is! I've tried everything that can be tried as near as I can tell and nothing even results in a different error message, it is always the remote host one.

      I need help!

       
      Last edit: Noah Patterson 2014-05-22
  • mumblenz
    mumblenz
    2014-05-23

    @strem , Are you also running windows 8.1?

    Can you try launching in compatibility mode for win 7?

    What firewalls are you both running? ill see if i can replicate the issue in a vm

    Also i take it you are both running mumble 1.2.6? Tried downgrading to 1.2.5?

     
  • Noah Patterson
    Noah Patterson
    2014-05-23

    I have since tried launching in compatibility mode for Win7 and XP service pack 3, launching both as administrator and "normally", neither change the "remote host" result.

    I have the standard Windows firewall, and I have let Mumble.exe as an approved program. The install on my wife's computer (1.2.6 on Win7) works out of the box, no adjustments to anything needed (ie allowing through a firewall).

    I've tried downgrading to 1.2.5, no success or change in result.

    Thanks for looking into this, I appreciate it!

     
  • mumblenz
    mumblenz
    2014-05-23

    Well i started windows 8.1 in a vm and had no issues what so ever (other than with windows 8.1 lol). Mumble worked great, as it should. i even tried to break it (unsuccessfully), the only time i was unable to connect to a server was when i blocked mumble in the firewall, but then i didn't get the server list either.

    A few more ideas...

    Do you have multiple network interfaces?

    Also, what does the console.txt say? (C:\Users\USERNAME\AppData\Roaming\Mumble\console.txt)
    you may want to delete console.txt then launch mumble so you only get the output of one launch, not hundreds.

     
  • Noah Patterson
    Noah Patterson
    2014-05-23

    My network is pretty simple - one router with one internet connection to it, two PCs connected off the router and one WDHDTV box.

    I'm not sure what the console.txt says, I'm at work right now so I can't check, but since this issue appeared (last Saturday) any reinstalls I've done have included deleting the AppData\Roaming\Mumble folder completely after uninstalling the program. I delete that, and Program Files(x86)\Mumble, empty the recycle bin and clean the registry before re-installing (cleaning done with Auslogics). So I don't think there's any artifacts left over causing interference, but perhaps I'm wrong?

     
  • mumblenz
    mumblenz
    2014-05-23

    ok, doubtful its any network issue then.

    console.txt is more of a log, it might give an indication why its failing to connect

     
  • Noah Patterson
    Noah Patterson
    2014-05-23

    I'll have to get back to you on that in an hour when I'm home.

    It's utterly boggling, wny my computer only does not connect.

     
  • Noah Patterson
    Noah Patterson
    2014-05-23

    I deleted console.txt, and then tried connecting. This is the log:

    <W>2014-05-23 17:44:47.322 WASAPIInit: Requires Vista SP1
    <W>2014-05-23 17:44:47.322 ASIO: No valid devices found, disabling
    <W>2014-05-23 17:44:47.389 CELT bitstream 8000000b from C:/Program Files (x86)/Mumble/celt0.0.7.0.sse2.dll
    <W>2014-05-23 17:44:47.405 CELT bitstream 80000010 from C:/Program Files (x86)/Mumble/celt0.0.11.0.sse2.dll
    <W>2014-05-23 17:44:47.405 Locale is "en_CA" (System: "en_CA")
    <W>2014-05-23 17:44:47.495 Database SQLite: "3.7.7.1"
    <W>2014-05-23 17:44:47.496 Bonjour: Failed to load dnssd.dll
    <W>2014-05-23 17:44:47.517 Overlay: Listening on "\.\pipe\MumbleOverlayPipe"
    <W>2014-05-23 17:44:47.556 G15LCDEngine_lglcd: Unable to launch G15 helper.
    <W>2014-05-23 17:44:47.805 GlobalShortcutWin: No LowLevelHooksTimeout registry key found.
    <W>2014-05-23 17:44:48.149 Adding device {6f1d2b60-d5a0-11cf-bfc7-444553540000} Mouse Mouse:8
    <W>2014-05-23 17:44:48.150 Adding device {6f1d2b61-d5a0-11cf-bfc7-444553540000} Keyboard Keyboard:127
    <W>2014-05-23 17:44:48.173 Adding device {9108b850-902e-11e3-8002-444553540000} Logitech BT Mini-Receiver Logitech BT Mini-Receiver:652
    <W>2014-05-23 17:44:48.178 Adding device {9109c9c0-902e-11e3-8003-444553540000} Logitech BT Mini-Receiver Logitech BT Mini-Receiver:3
    <W>2014-05-23 17:44:48.772 AudioInput: 40000 bits/s, 48000 hz, 480 sample
    <W>2014-05-23 17:44:48.905 DXAudioInput: Initialized
    <W>2014-05-23 17:44:48.907 DXAudioOutput: Primary buffer of 48000 Hz, 2 channels, 16 bits
    <W>2014-05-23 17:44:48.909 DXAudioOutputUser: New 48000Hz output buffer of 96000 bytes
    <W>2014-05-23 17:44:48.909 AudioOutput: Initialized 2 channel 48000 hz mixer
    <W>2014-05-23 17:44:51.845 OpenSSL Support: 1 (OpenSSL 1.0.0l 6 Jan 2014)
    <W>2014-05-23 17:44:56.997 ServerHandler: QOS2 loaded

     
  • mumblenz
    mumblenz
    2014-05-23

    Apart from your device ID's being different than mine, its exactly the same as my working copy on 8.1 . mumble is loading correctly.

    Have you tried installing the server along with the client, and connecting to 127.0.0.1:64738 , that would at least tell you if its your client that's screwed or if its something external that's causing the issue. the server install is bundled with the client and is like a 30 sec setup on windows. I'm assuming you are getting mumble from SF?

     
  • Noah Patterson
    Noah Patterson
    2014-05-23

    I am getting it from SF, yes (of course!).

    I'll try that suggestion.

     
  • Noah Patterson
    Noah Patterson
    2014-05-23

    Do I need to do anything with the Murmur server once installed? I'm attempting to connect Mumble to the IP and port you indicated, and get "Connection refused".

    The Murmur log says:
    <W>2014-05-23 18:27:17.547 Initializing settings from C:/Program Files (x86)/Mumble/murmur.ini (basepath C:/Program Files (x86)/Mumble)
    <W>2014-05-23 18:27:17.552 OpenSSL: OpenSSL 1.0.0l 6 Jan 2014
    <W>2014-05-23 18:27:17.552 Failed to open logfile murmur.log. No logging will be performed.
    <W>2014-05-23 18:27:19.074 ServerDB: Opened SQLite database C:/Users/Noah/murmur.sqlite
    <W>2014-05-23 18:27:19.081 Murmur 1.2.6 (1.2.6) running on Win: 6.2.9200.1: Booting servers
    <W>2014-05-23 18:27:19.090 1 => Server: TCP Listen on [::]:64738 failed: The bound address is already in use
    <W>2014-05-23 18:27:19.095 1 => Server: TCP Listen on 0.0.0.0:64738 failed: The bound address is already in use
    <W>2014-05-23 18:27:19.098 1 => Stopped

     
    Last edit: Noah Patterson 2014-05-23
  • mumblenz
    mumblenz
    2014-05-24

    you have something already running on port 64738? in the config file change the line host= to host=127.0.0.1, and make sure there is only one copy running

     
  • Noah Patterson
    Noah Patterson
    2014-05-25

    I'm not really clear on setting up a Murmur server, but I did (I think!) what you suggested, and this is the log:

    <W>2014-05-24 20:02:25.158 Initializing settings from C:/Program Files (x86)/Mumble/murmur.ini (basepath C:/Program Files (x86)/Mumble)
    <W>2014-05-24 20:02:25.162 OpenSSL: OpenSSL 1.0.0l 6 Jan 2014
    <W>2014-05-24 20:02:25.163 Failed to open logfile murmur.log. No logging will be performed.
    <W>2014-05-24 20:02:26.656 ServerDB: Opened SQLite database C:/Users/Noah/murmur.sqlite
    <W>2014-05-24 20:02:26.663 Murmur 1.2.6 (1.2.6) running on Win: 6.2.9200.1: Booting servers
    <W>2014-05-24 20:02:26.674 1 => Server listening on [::]:64738
    <W>2014-05-24 20:02:26.678 1 => Server listening on 0.0.0.0:64738
    <W>2014-05-24 20:02:26.680 Bonjour: Failed to load dnssd.dll
    <W>2014-05-24 20:02:26.684 1 => Not registering server as public
    <W>2014-05-24 20:09:00.591 1 => <1:(-1)> New connection: 127.0.0.1:52084
    <W>2014-05-24 20:09:00.592 Connection: Failed to add flow to QOS
    <W>2014-05-24 20:09:55.152 1 => <1:(-1)> Connection closed: The remote host closed the connection [1]

    And this is the Console.txt log:

    <W>2014-05-24 20:02:00.831 DirectSound: Disabled as WASAPI is available
    <W>2014-05-24 20:02:00.831 ASIO: No valid devices found, disabling
    <W>2014-05-24 20:02:00.885 G15LCDEngine_lglcd: Logitech LCD Manager not detected.
    <W>2014-05-24 20:02:00.890 CELT bitstream 8000000b from C:/Program Files (x86)/Mumble/celt0.0.7.0.sse2.dll
    <W>2014-05-24 20:02:00.891 CELT bitstream 80000010 from C:/Program Files (x86)/Mumble/celt0.0.11.0.sse2.dll
    <W>2014-05-24 20:02:00.892 Locale is "en_CA" (System: "en_CA")
    <W>2014-05-24 20:02:01.038 Database SQLite: "3.7.7.1"
    <W>2014-05-24 20:02:01.038 Bonjour: Failed to load dnssd.dll
    <W>2014-05-24 20:02:01.077 Overlay: Listening on "\.\pipe\MumbleOverlayPipe"
    <W>2014-05-24 20:02:01.292 GlobalShortcutWin: No LowLevelHooksTimeout registry key found.
    <W>2014-05-24 20:02:01.611 Adding device {6f1d2b60-d5a0-11cf-bfc7-444553540000} Mouse Mouse:8
    <W>2014-05-24 20:02:01.612 Adding device {6f1d2b61-d5a0-11cf-bfc7-444553540000} Keyboard Keyboard:127
    <W>2014-05-24 20:02:01.635 Adding device {9108b850-902e-11e3-8002-444553540000} Logitech BT Mini-Receiver Logitech BT Mini-Receiver:652
    <W>2014-05-24 20:02:01.641 Adding device {9109c9c0-902e-11e3-8003-444553540000} Logitech BT Mini-Receiver Logitech BT Mini-Receiver:3
    <W>2014-05-24 20:02:01.658 AudioInput: 72000 bits/s, 48000 hz, 480 sample
    <W>2014-05-24 20:02:01.664 WASAPIInput: Latencies 101587 30000 => 100000
    <W>2014-05-24 20:02:01.666 WASAPIOutput: Latencies 101587 30000 => 100000
    <W>2014-05-24 20:02:01.672 WASAPIInput: Stream Latency 58050 (896)
    <W>2014-05-24 20:02:01.674 AudioInput: Initialized mixer for 2 channel 44100 hz mic and 0 channel 48000 hz echo
    <W>2014-05-24 20:02:01.679 WASAPIOutput: Stream Latency 116100 (2646)
    <W>2014-05-24 20:02:01.680 WASAPIOutput: Periods 10158us 3000us (latency 11610us)
    <W>2014-05-24 20:02:01.680 WASAPIOutput: Buffer is 60000us (5)
    <W>2014-05-24 20:02:01.681 AudioOutput: Initialized 2 channel 44100 hz mixer
    <W>2014-05-24 20:08:55.731 OpenSSL Support: 1 (OpenSSL 1.0.0l 6 Jan 2014)
    <W>2014-05-24 20:09:00.574 ServerHandler: QOS2 loaded

     
  • mumblenz
    mumblenz
    2014-05-25

    yeah it looks set up well enough. So it tried to connect to your local server for 55 seconds before giving up? You should at least be able to connect to a local server, that makes no sense.

     
  • mumblenz
    mumblenz
    2014-05-25

    Something my mate just said may help you find the cause. Open "Control Panel" go into "Recovery" then "configure system restore", then click the "system restore" button, then "choose a different restore point".

    and see if anything was installed the day or the day before it stopped working, may give a hint of how to fix it. I'm not recommending you do a system restore to fix the issue, but it may give you a clue why it suddenly stopped working

     
  • Noah Patterson
    Noah Patterson
    2014-05-25

    Looks like the restore point furthest away is May 19, the last day that Mumble connected was May 16. There were no Windows system updates on May 17 (the day it stopped working) and I hadn't installed or updated (of which I am aware) software at that time.

    As for making no sense, tell me about it! I have also tried uninstalling and updating my network adapter drivers and booted into a clean boot. All result in the same scenario

     
  • Athildur
    Athildur
    2014-05-25

    I'd like to add that I am having the exact same issue. I've tried everything I can think of, and tried everything I could find via google, but nothing seems to solve the issue.

    My mumble simply cannot connect to any server anymore. I don't remember installing anything that could interfere (no services using internet or voice protocols, and no programs or services that are running while I try to use mumble) other than recent windows 7 updates.

    Firewall/antivirus isn't the issue, ISP isn't blocking anything and I'm connected directly to the modem, so no router to mess it up.

    Mumble can ping the servers just fine (the whole list shows up fine with latency/users), but once I try to connect it just takes far too long, and then disconnects. The server admin says that I do actually connect, and then immediately disconnect. He suspects it's a timeout issue, but I have no idea how to fix it as this seems only to affect mumble, on all servers I've tried (in different countries, using different port numbers).

    (I swear, these computer issues where you just can't find the problem drive me up the wall!)

     
  • Noah Patterson
    Noah Patterson
    2014-05-25

    Athildur, that is my exact situation.
    When did this start happening for you?

    I've had the fellow who hosts our Murmur server do a Skype screen share with me, we've walked through everything we can think of and find online, he watches my connection come in and I time out, but cannot seem to see exactly why as everything looks normal, right up until the disconnect.

     
  • mumblenz
    mumblenz
    2014-05-25

    This is puzzling me big time. Me and a computer tech are bouncing some ideas around and have come up with not a heck of a lot.

     
  • strem
    strem
    2014-05-25

    The conclusion that a friend and I came to before giving up on fixing it was that something on my PC was specifically restricting mumble and nothing else. If there is known malware that can cause this (babylon, conduit) then maybe my anti-malware didn't remove every bit of the mediocre viruses I had on my PC.

    Another thing that might help you figure out this problem is that it's not only that mumble won't connect to servers, it's also extremely unresponsive. 1.2.6 helped alot with the sluggishness, but it still likes to freeze up and be utterly slow.

    ps. I am not running windows 8.1. I am running windows 7.
    psps. any other computer in my household running on the same connection can use mumble without fail. Including mobile devices. It has to be something specifically on my computer and I cannot for the life of me figure out what it is.

     
    Last edit: strem 2014-05-25
  • mumblenz
    mumblenz
    2014-05-25

    I agree, by setting up a local server we ruled out it was network / isp / rest of the world related.

    I would check windows updates and see if you can find a common update that was installed on the same day for all of you.

    Or any software you all have installed?

     
  • strem
    strem
    2014-05-25

    I looked through my updates and the only things that are around the time my mumble stopped working are basic things like security updates and microsoft silverlight stuff. As for software installed, I cannot think of anything that I installed before my client began to shit the bed.

    It's a long shot but I'll try to update silverlight.

    edit: wasnt silverlight
    editedit: trying to repair .net framework
    editeditedit: not that either

    Another thing I should mention to maybe help you solve this mumblenz: The specific channel I am trying to connect to has a password, and I am not even getting prompted for the password before mumble disconnects me and says "Connection failed: remote host has closed the connection"

     
    Last edit: strem 2014-05-25
  • mumblenz
    mumblenz
    2014-05-25

    what network cards are you all using?

    If any of you would let me do a screen share over skype i could have a better look

     
  • strem
    strem
    2014-05-26

    My network adapters: http://i.imgur.com/mav1ZOO.png
    My skype is Strembitskyz. Add me for a screen share.

     
1 2 3 4 > >> (Page 1 of 4)