The Mumble documentation refers to the server for Mumble with several naming conventions: mumble-server, murmur, and murmurd all refer to the same server binary /usr/bin/mumble-server. This package includes a system-wide installation of mumble-server. If you want a personal server running on your own user account, use the mumble-server-user-wrapper script. Starting with Mumble 1.5.517 release candidate, the client only supports the OPUS codec and all other codec support has been removed. Historically Mumble supported CELT 0.7.1 as the base communication codec, so versions Mumble older than mid-2012 that do not have OPUS support will have text messaging work but will not be able to communicate via audio. The configuration file how now been moved to /etc/mumble/mumble-server.ini. During installation of mumble-server if a configuration file from a prior version exists, it will be moved to the new location prior to installatoin of the new config file to prompt the administrator about changes. Mumble-server's root user is called SuperUser. To set the password for SuperUser, simply use 'dpkg-reconfigure mumble-server'. Mumble-server now uses systemd by default and upstream no longer ships and init script (see more about this below). Startup and shutdown is done via systemctl [start|stop] mumble-server To stop and disable mumble-server with systemd: systemctl stop mumble-server systemctl disable mumble-server systemctl mask mumble-server To re-enable and start mumble-server with systemd: systemctl unmask mumble-server systemctl enable mumble-server systemctl start mumble-server Some notes about Mumble and Tor (Tor = "The Onion Router"): ------------------------------------------------------------------------------ If you have never heard of Tor before, it is not just "the dark web"; it is also a very useful tool you can use at home and at work. Mumble and mumble-server can be used in either UDP or TCP mode. Tor is only capable of TCP connections. In TCP mode Mumble is capable of being run over Tor to hide the originating IP address of the client. Mumble audio over Tor can work well. Mmumble-server can be used over a Tor Onion Service to run a server from an IP address behind a NAT (e.g. from your server at home) and still allow remote connection from the outside world. This works because a Tor Onion Service creates a .onion address name that exists at a "rendezvous point" at a Tor Exit Node in the public Internet space which is then connected to from Mumble running over Tor. So there's good reasons to want to run Mumble and Mumble-server over Tor even if you may not need the extra privacy and security Tor can provide. Instructions on using Tor with Mumble is in the README.Debian file for the mumble package. To create a Tor Onion Service for mumble-server, install the 'tor' package, then edit /etc/tor/torrc and at the bottom of the file add the following configuration (or at least this should be a working example): HiddenServiceDir /var/lib/tor/mumble-server HiddenServiceVersion 3 HiddenServicePort 64738 127.0.0.1:64738 and restart the Tor daemon. After the restart Tor will create an Onion service for mumble-server, and the .onion address will be in /var/lib/tor/mumble-server/hostname. Explanation for last config line above: HiddenServicePort 64738 127.0.0.1:64738 The left-hand port number is the port number created for the service at the remote rendezvous point on the Exit Node, and the IP address:port # combo on the right is the local IP:port for the local service (mumble-server) to be made available. In this way the Tor daemon is capable of creating any number of Tor Onion Services for any number of services on the local network. Additional HiddenServicePort lines for other services can connect services on other ports using the same Tor Onion Service hostname for them. Behind the scenes, when Tor creates an Onion service, the daemon makes an outbound connection to a Guard Node, a Middle Relay Node, and then an Exit Node where the rendezvous point is created. As it does this, when using a standard NAT router/firewall the NAT router makes an entry for the open connection to allow traffic -- and since the connection stays open and kept alive, so do the firewall rules through various routers allowing the traffic along the way. When the rendezvous is connected to over Tor, the connection comes down the open pipe through firewalls that have kept the connection open, down to the destination service. This type of service is also amazingly useful for ssh to host VMs at home and be able to easily log into or transfer files to them with rsync over ssh. For some "Hosting Onion Services Best Practices", see: https://help.riseup.net/en/security/network-security/tor/onionservices-best-practices ------------------------------------------------------------------------------ For convencience for those running alternate init systems, the old init script, /etc/default settings file, and logroate file are included in /usr/share/doc/mumble-server/examples/ The mumble-server init script is silent concering messages to the console on startup/shutdown by default; if you wish to see start/stop messages to the console on upgrades, uncomment "VERBOSE=yes" in /etc/default/rcS. To enable or disable the mumble-server daemon under sysvinit, this now needs to be done via update-rc.d at the command line as root or via sudo: update-rc.d mumble-server [disable|enable] This has been changed compared to upstream because disabling daemons via an environment variable in /etc/default/ causes problems for init systems (e.g. systemd) so it has been deprecated by Debian Policy ยง9.3.3.1 since Policy version 4.1.3.