Replies: 3 comments 19 replies
-
To me this seems as if the underlying issue is that for some reason you are really losing the connection to your host - aka you can't reach it over the network anymore. At least long enough for Mumble to decide that the connection is probably dead and so automatically performs a disconnect. Did you check whether you can successfully ping your server when your Mumble client disconnects? |
Beta Was this translation helpful? Give feedback.
-
So apparently this issue only happens when I'm live streaming on Odysee. Perhaps there is an issue with routing somewhere that causes client to disconnect? Maybe it's my wiring in the house. Cant test unless I'm live, and I cant do that til Friday or Saturday night. I have been connected to the server almost continuously since I posted without a hiccup. Strange. |
Beta Was this translation helpful? Give feedback.
-
I've been doing a lot of testing and have a few print outs of syslogs during times it disconnects. The issue is persistent on all version of mumble I've tried, and on both Windows, and Linux. It happens both on Ethernet and Wifi. The Linux computers show I bought a Klein Tools ethernet cable tester to test all my terminations and cables. Everything checks out as good. I'm wondering now if there is something wrong with the router. I always see this in logs when it disconnects: |
Beta Was this translation helpful? Give feedback.
-
Can anyone help me discover why mumble is randomly disconnecting? I recently switched hosts and moved my website, my SSL certificates, and mumble server over to a new VPS. This wasn't happening before I moved hosts. One time when this happened, I logged in through a terminal and the server was so unresponsive I couldn't type. Didn't resolve until I did a hard reboot at the host's panel.
About Server
It's a single virtual CPU with 1GB RAM and 25GB NVME drive & 2000GB bandwidth
Running Apache2 with 4 virtual hosts serving up very small and simple static websites + my mumble server.
murmurd -- 1.3.4-1
Debian 11 bullseye kernel 5.10.0-16-amd64
Free memory is around 42% (using 561MB out of 976MB)
I check the mumble log and the only thing I see during the times it's randomly disconnecting was this:
kern.log is basically a constant barrage of UFW blocks
I have fail2ban set with jail.local sending bad SSH attempts to the jail.
Server is secured with SSH keypair authentication and root login disabled.
About client
Mumble (1.3.4-1)
Debian 11 bullseye kernel 5.10.0-16-amd64
I have experienced this with "Force TCP mode" ticked on and off. Same result.
Thanks for your help.
Beta Was this translation helpful? Give feedback.
All reactions