2020-10-24 19:05 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0006405Spring engineGeneralpublic2020-09-19 11:58
Reporteresainane 
Assigned Toabma 
PrioritynormalSeverityminorReproducibilityN/A
StatusresolvedResolutionfixed 
Product Version 
Target VersionFixed in Version 
Summary0006405: mumble.springrts.com maintenance
DescriptionAnarchid is apparently now unable to join the springrts mumble server, since it's now very old and doesn't speak modern security protocols that the newer clients now apparently require.

Do we know who to contact about the mumble server?

There are a lot of little things that could use tweaking, from raising the bandwidth limit on voice, to a higher limit on image size, to using a proper SSL certificate. But if people are currently unable to join, that's going to be the most important point.


I'm not sure to what extent this service is maintained or who's running it these days, so I'm cautiously reporting an issue here, in the hopes that it might reach someone relevant? If it turns out to be necessary, I already run multiple mumble servers and would be happy to host another for springrts given a CNAME, with or without the current user/channel database. If this is not an appropriate place, my apologies and do feel free to close this issue!
TagsNo tags attached.
Checked infolog.txt for ErrorsIrrelevant
Attached Files

-Relationships
+Relationships

-Notes

~0020463

abma (administrator)

Last edited: 2020-07-10 09:29

View 2 revisions

the service is running since 2019, i've manually restarted it. does this already solve some of your issues?

~0020470

esainane (reporter)

Anarchid forwarded me this screenshot just under four hours ago. It looks like we're still having problems. There might be some more detailed information in the mumble server logs around that time, too.

~0020530

abma (administrator)

i've upgrade the server to debian buster:

Unpacking mumble-server (1.3.0~git20190125.440b173+dfsg-2) over (1.2.18-1+deb9u1) ...

did anything change?



https://springrts.com/phpbb/viewtopic.php?f=38&t=41865

~0020531

esainane (reporter)

It looks like the server is now using a modern protocol, and now has a proper SSL certificate for springrts.com!

Would it be possible to add a Subject Alternate Name to the certificate, for mumble.springrts.com?

My client still prints a warning on connection: "Server maximum network bandwidth is only 72 kbit/s. Audio quality auto-adjusted to 57 kbit/s (20 ms)"

I think the relevant setting in mumble-server.ini would be "bandwidth=131072"?

To be sure, I'll check with Anarchid and NCG to make sure that TLS works for them now without workarounds, but my information panel says it's using TLS_AES_256_GCM_SHA384, so I don't expect there to be any problems there now. :)

~0020532

abma (administrator)

why 131072?

the docs say, above 130000 nothing changes:

https://wiki.mumble.info/wiki/Murmur.ini#bandwidth

~0020533

abma (administrator)

i've setup a letscrypt certificate for mumble.springrts.com.

wrt bandwith some infos would be nice, the default IMHO looks reasonable.

~0020534

esainane (reporter)

131072 is 128*1024, which is I suppose what they mean by 'about 130000'?

It's been a while since I last configured by own server, but I think that was the first round interval that didn't print any warnings regardless of the outcome from audio wizard setup.

~0020535

abma (administrator)

ok, i've set it to

bandwidth=131072
+Notes

-Issue History
Date Modified Username Field Change
2020-07-10 05:04 esainane New Issue
2020-07-10 09:28 abma Status new => feedback
2020-07-10 09:28 abma Note Added: 0020463
2020-07-10 09:29 abma Note Edited: 0020463 View Revisions
2020-07-15 01:24 esainane File Added: anarchid-2020-07-15--07-35-29.png
2020-07-15 01:24 esainane Note Added: 0020470
2020-07-15 01:25 esainane Status feedback => new
2020-09-09 22:39 abma Assigned To => abma
2020-09-09 22:39 abma Status new => feedback
2020-09-09 22:39 abma Note Added: 0020530
2020-09-09 22:56 esainane Note Added: 0020531
2020-09-09 22:56 esainane Status feedback => assigned
2020-09-09 23:06 abma Note Added: 0020532
2020-09-09 23:13 abma Note Added: 0020533
2020-09-09 23:17 esainane Note Added: 0020534
2020-09-19 11:58 abma Status assigned => resolved
2020-09-19 11:58 abma Resolution open => fixed
2020-09-19 11:58 abma Note Added: 0020535
+Issue History