Short answer. A Mumble server runs 24/7 on any machine that stays switched on and can be reached from the internet. Install the free, open-source Mumble server (the program is called mumble-server, and older guides call it Murmur) from your Linux distribution's packages or with the official Docker image mumblevoip/mumble-server, open port 64738 for both TCP and UDP, set a SuperUser password, and connect with the Mumble app. It needs very little: in our test (Mumble server 1.5.915) it used about 28 MB of memory with nobody connected and 53 MB with 250 people connected. If you would rather not run the machine yourself, rent a Mumble server from PlayNHost: 10 to 250 slots, from $1.99 a month, with the SuperUser password set in the panel. Checked on 6 November 2026 against Mumble 1.5.939, the newest stable release.
What "24/7" takes
A machine that never sleeps. A Linux VPS or a home server. A gaming PC that goes to sleep takes the voice server down with it.
A public address. A VPS has one. At home you forward port 64738 (TCP and UDP) on your router to the machine and give your friends your public IP address or a domain name.
Port 64738 open for TCP and UDP. TCP carries the connection, login and text chat; UDP carries the voice, because it has lower latency. If UDP is blocked, Mumble tunnels the voice through the TCP connection instead, which works but gives up UDP's lower latency.
A start on boot. The Linux package installs a systemd service (with Restart=always if it crashes); the Docker command below uses --restart unless-stopped, so Docker starts it again after a reboot.
Updates and a backup. Everything the server knows (channels, groups, permissions, registered users and its own certificate) is in one SQLite database file. Stop the server, copy that file, and you have a backup.
Option 1: the official Docker image
Mumble's own project publishes the image on Docker Hub as mumblevoip/mumble-server. This is the command from its README with two changes: a version tag instead of latest, and --restart unless-stopped instead of on-failure so the server comes back after a reboot. We ran the image v1.5.939 on our own server:
With the image already downloaded, the server was listening 1.6 seconds after the command. The image is 338 MB on disk.
The server runs as user ID 10000 and took ownership of the ./data/mumble folder by itself. That folder holds mumble-server.sqlite (the database) and the config file the image writes, so docker rm followed by a new docker run keeps your channels.
Settings come from environment variables named MUMBLE_CONFIG_ plus the setting's name, for example -e MUMBLE_CONFIG_USERS=25 or -e MUMBLE_CONFIG_SERVER_PASSWORD=yourpassword.
Set the SuperUser password with -e MUMBLE_SUPERUSER_PASSWORD=.... Without it, the first start makes a random one and writes it to the log:
docker logs mumble-server 2>&1 | grep SuperUser
<W>2026-11-06 05:04:00.420 1 => Password for 'SuperUser' set to '...'
Option 2: the Linux package (Ubuntu 24.04 and Debian 13)
Install the server:
sudo apt update
sudo apt install mumble-server
Set the SuperUser password. dpkg-reconfigure asks three questions (start on boot, a higher priority, the SuperUser password); the password is the one that matters:
sudo dpkg-reconfigure mumble-server
Then make sure the service starts at boot:
sudo systemctl enable --now mumble-server
Edit the settings in /etc/mumble/mumble-server.ini (for example users=, serverpassword= and welcometext=), then restart the service:
sudo systemctl restart mumble-server
Open the port. On Ubuntu with ufw:
sudo ufw allow 64738/tcp
sudo ufw allow 64738/udp
Distribution packages are often behind Mumble's own releases. On 6 November 2026, Ubuntu 24.04 installed version 1.5.517 and Debian 13 installed 1.5.735, while Mumble's newest stable release was 1.5.939 (9 October 2026), whose release notes ask server administrators in particular to update. The Docker image tagged v1.5.939 (also v1.5) was published on 11 October 2026. On 6 November 2026 the latest tag still pointed to 1.5.915, so name the version in the command. Older releases (Ubuntu 22.04, Debian 12) ship Mumble 1.3.4, with the settings in /etc/mumble-server.ini.
On Windows, Mumble's downloads page has a server download for Windows (x64). Mumble no longer provides new macOS builds for the 1.5 series; the last one is 1.5.901.
Connect and become admin
Install the Mumble app: from mumble.info on Windows and macOS, from your distribution's packages on Linux. Mumble's downloads page lists Mumla and MumbleWay as third-party apps for phones.
In the app choose Server, Connect, Add New, and enter your server's address and port 64738.
The first time, the app shows the server's certificate and asks whether to trust it. The server made that certificate itself on its first start (ours was valid for 20 years), so the warning is expected once: Mumble certificate warnings explained.
To manage channels, connect with the user name SuperUser and the SuperUser password. SuperUser can change everything but cannot speak or whisper, so give your normal account admin rights and use that day to day: How to become admin on your Mumble server.
We ran Mumble server 1.5.915 (the version on our servers) in containers on one of our own servers, with the same memory and CPU limits as our plans: 128 MB for 10 to 100 slots and 256 MB for 250 slots, each with half a CPU core. The "users" were test connections that logged in and stayed connected without sending audio:
Connected users
Memory (resident)
0
about 28 MB
10
about 30 MB
50
about 34 MB
100
about 40 MB
250
about 53 MB
The plan limit counts the container's memory, which stayed between 5 and 31 MB in these tests.
Start: the first start took 2.0 to 2.7 seconds to the line Server listening on, most of it a one-time password-hashing benchmark (Performed initial PBKDF2 benchmark). Restarts took 0.5 to 0.7 seconds.
Disk: the whole server folder was 128 KB new and 220 KB after the 250-user test.
Not measured: CPU and bandwidth while people talk. Mumble's default bandwidth=558000 caps what each user may send at 558,000 bits per second.
Problems you can run into
Server is full (max 10 users): the users= limit is reached. The person must wait for a free slot or you raise the limit.
Invalid server password: the server has a join password (serverpassword=) and the person typed none or the wrong one.
Wrong certificate or password for existing user: a wrong SuperUser password, or a registered name used from another computer without its certificate.
Many people from one address get locked out. By default the server ignores an IP address for 300 seconds after 10 connection attempts from it within 120 seconds, successful ones included (autobanAttempts, autobanTimeframe, autobanTime). In our test the eleventh connection from one address in about ten seconds was refused with Ignoring connection: ... (Global ban) in the log. A LAN party behind one router can hit this; on your own server you can raise or switch off these settings.
Not registering server as public, or, if you set registerName, Registration needs nonempty 'registername', 'registerpassword' and 'registerurl': harmless. Both are about Mumble's public server list, which a private server does not need.
Renting instead of self-hosting
A PlayNHost Mumble server is created when you order and stays online around the clock; you do not install, update or forward anything:
Pick a plan (10, 25, 50, 100 or 250 slots) and click Create Server.
In the panel, open Settings, Game Settings and fill in SuperUser Password, plus a Join Password and Server Name if you want them. They apply the next time the server starts.
Copy the Connect address from Overview, or press Connect there to open it in the Mumble app. Each server has its own port, so use the one shown, not 64738.
We use cookies to keep the site working, to understand how it is used, and to measure our marketing. You can accept all, accept essential cookies only, or choose per category.We use cookies to keep the site working, to understand how it is used, and to measure our marketing. They are on by default here. You can switch off anything you do not want.Read our privacy policy