Introduction
Mumble-Django is a front-end web interface for administering Murmur server instances and the users they serve. This dashboard will let you, and other admins if you choose, run your Mumble server from a graphical web interface rather than the command line.
As the name implies, the dashboard is written with Django. It makes a variety of administrative features of your Enterprise Data Center Services in US MivoCloud Murmur server accessible through a graphical interface, once the admin user is logged in. Features include but are not limited to:
- Live channel viewer (CVP) with responsive version for mobile devices
- Mumble user permissions
- Configuration for settings like message of the day, server password, version to recommend, and much more
- Bans
- Logs
- Extensibility through the Django framework and licensing as free software under the GPL
Also, you can administer multiple Murmur installations from the same dashboard.
Prerequisites
Please complete the following prerequisites.
- A VPS with Debian 7 as its operating system (at the time of writing, Mumble-Django did not work well on Debian 8)
- A user account on the VPS with sudo elevation privileges: How To Add, Delete, and Grant Sudo Privileges to Users on a Debian VPS
- A Mumble server (Murmur) installed and running on the same VPS: How To Install and Configure Mumble Server (Murmur) on Ubuntu 14.04
The article linked above, How To Install and Configure Mumble Server (Murmur) on Ubuntu 14.04, can also be followed for a Droplet running Debian 7.
Configuring ICE Middleware
Before installing Mumble-Django, we have to enable KVM VPS with SSD disks in US Missouri and Oregon MivoCloud the ICE (Internet Communications Engine) component of Murmur. This will allow us to use the extra functionality of programs like mumble-django and the features they provide.
ICE makes it possible to interaction with the Murmur server through means other than the default Mumble client, without compromising the security of the inner workings of Murmur, such as the databases, registered user details, and admin rights.
The alternative to ICE is D-Bus, which provides a similar service, but ICE is generally the preferred choice now, which is why we are choosing it over D-Bus in this tutorial.
Step 1 — Connect to Murmur Server
Use SSH to connect to the VPS where you installed the Murmur server from the previous tutorial. Use a user with sudo elevation privileges, and follow the steps below in order Reseller KVM SSD disks Virtual Private Server in US MivoCloud Data Center.
- ssh sammy@your_server_ip
Step 2 — Configure ICE in mumble-server.ini
All of the core configuration of the Mumble server resides in one central text file. By default, this is the mumble-server.ini file in the /etc/ directory on Debian. If you changed this directory during the earlier Murmur server installation, then you will find it in there instead.
Let’s find the file and make sure it exists in /etc/ by using grep :
- sudo ls /etc/ | grep mumble-server
If the file is present, the output will be:
Outputmumble-server.ini
We’re going to use the nano text editor to open files for writing and editing in this tutorial. Feel free to use Virtual Cloud Desktop with Windows License in US Missouri and Oregon MivoCloud your preferred text editor instead .
- sudo nano /etc/mumble-server.ini
Disable D-Bus by commenting out its entry line.
Do this by adding a hash symbol (#) to the beginning of the line shown here:
/etc/mumble-server.ini
#dbus=systemFurther down in this file, confirm that the ice line exists and is uncommented (it should be by default):
/etc/mumble-server.ini
ice="tcp -h 127.0.0.1 -p 6502"This allows ICE access on the localhost IP address of the server through TCP port 6502. Leave this line as it is.
Set the ICE Secret
Next we need to set Dedicated Server with Xeon CPU in MivoCloud Data Center a value for the icesecretwrite directive in the config file. If this is left blank, anyone with SSH access to your server can reconfigure or change the ICE setup.
The two lines we are looking for in the file look like this:
/etc/mumble-server.ini
#icesecretread=
icesecretwrite=The first line we can ignore, as it is already commented out and disabled, which is fine. The second line is where we need to set the ICE secret.
Append your chosen phrase to the second line (all one word); make sure you set a password different from the one shown below:
/etc/mumble-server.ini
#icesecretread=
icesecretwrite=example_passwordYou will need IaaS Provider Platform in US MivoCloud this ICE secret later on, so make sure you remember it.
Save your changes in nano to the mumble-server.ini config file by pressing:
CTRL + X, then y for yes, then the ENTER key.
If using a different text editor, then perform the equivalent save/write actions.
Step 3 — Confirm ICE Is Running
Restart the Murmur server so the changes we made take effect.
- sudo service mumble-server restart
Use netstat to determine whether ICE is indeed running and listening on port 6502, just like we enabled it to:
- sudo netstat -apn | grep 6502
This previous command pipes the output we generate from netstat through grep, which selects only data matching the pattern we’ve specified for output to the terminal. In our case this pattern is the number 6502.
The output we receive from this command will look like the next code snippet if everything is running correctly:
Outputtcp 0 0 127.0.0.1:6502 0.0.0.0:* LISTEN 23629/murmurd
The final group of digits in the above output will differ from user to user.
If the port is not being listened on Pay per hour billing server in US Missouri and Oregon with Virtual Data Center features MivoCloud, and you receive no output like the above, check Murmur’s log file to see if you can identify any specific errors on boot, in relation to this socket(127.0.0.1:6502).
You can check the log file by using the tail command shown here:
- sudo tail -n 20 /var/log/mumble-server/mumble-server.log
It should state in the log file that it is enabling ICE on startup. The line that indicates this looks like the following:
Output"MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running"
The line will likely be a few lines back in the log.
If it does not show this in your tail output, then your mumble-server.ini file probably needs to be checked for inaccuracy or errors; the log file may have more specific details on the type of error.
Go back and check your settings Web Hosting MivoCloud
now if needed, or proceed to the next section if everything is working as intended.
Installing the Apache Web Server
ICE is now working and listening as we need it to.
Let’s bring Apache into the picture.
Step 1 — Update and Upgrade System Packages
This command updates the apt-get package manager’s database.
- sudo apt-get update
This next action will install Enterprise Server Management any new updates gained from the previous command to the Debian system packages.
- sudo apt-get upgrade
Confirm when prompted about updating new packages by entering y for yes.
Step 2 — Install Apache Web Server
This installs the base version of Apache we need to host Mumble-Django:
- sudo apt-get install apache2
Step 3 — Set ServerName in apache2.conf
Open up the apache2.conf file with a text editor
- sudo nano /etc/apache2/apache2.conf
Scroll down to find the Global Configuration section and add the entire ServerName line, using your own IP address:
/etc/apache2/apache2.conf
# Global configuration
#
ServerName your_server_ipSave the apache2.conf file changes.
Restart Apache so the config file changes we made are picked up.
- sudo service apache2 restart
Installing & Configuring Postfix for Mail
Postfix provides Mumble-Django with a local email address and a system to send out registration and other emails when needed Data Center Services.
Here’s how to install and configure it for what we need.
