Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Install Murmur from your Linux distribution or run the official container, expose TCP and UDP 64738, set a SuperUser password, and then lock down ICE and TLS. Murmur is the server component of Mumble (the client is usually called mumble). A small VPS is sufficient for a private voice community when it has persistent storage, reliable UDP, a public address or DNS name, and a firewall you control.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
This guide covers a native Ubuntu-style deployment, the Docker alternative, configuration, certificates, public registration, backups, and the checks that catch the most common failures.
As an Amazon Associate I earn from qualifying purchases.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhat Murmur does and what the VPS must provide
Mumble has two software components: the voice client and the server process, historically called Murmur and commonly packaged as mumble-server. The server stores virtual-server settings, channels, user registrations, ACLs, and other state in its database. Clients connect to the listening voice port; administrators can also connect through the ICE administration interface. ICE is not a client voice protocol and should never be treated as a public service.
Before installing, prepare the host with these properties:
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
- A supported Linux distribution with current security updates and administrative SSH access.
- A public IPv4 address, public IPv6 address, or DNS name that clients can reach. If you publish a DNS name, create its records before testing certificates.
- UDP support in both the VPS plan and any cloud firewall. Voice traffic can fail even when TCP tests succeed if UDP is filtered.
- Persistent disk space for the Murmur database, configuration, certificates, and logs. Container deployments must mount this storage explicitly.
- A host firewall and, where applicable, a separate provider-level firewall or security group.
- A decision between a distribution package managed by the operating system and a container managed by Docker.
Choose a VPS region close to most participants, and check the plan’s bandwidth quota, CPU and RAM headroom, IPv4/IPv6 availability, disk persistence, and support for long-lived UDP sessions. Current provider prices are not universal, so select a plan by these technical limits rather than by a headline price.
Choose native packaging or Docker
Both deployment models run the same Murmur service. Native packaging integrates with the distribution’s service manager, log collection, filesystem permissions, and security updates. Docker gives you an explicit image version and an isolated filesystem, but you must manage the container, volume ownership, image updates, and log limits.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Decision point | Distribution package | Docker image |
|---|---|---|
| Installation | Install the distribution package named mumble-server; the exact package name can vary. |
Install Docker, then run the official Mumble server image. |
| Upgrade control | Follows distribution repositories and their update cadence. | Pin a tested image tag such as vX.Y.Z; latest follows the newest image and can change behavior after a pull. |
| Configuration | Line-oriented INI file managed on the host. | INI settings can be supplied with MUMBLE_CONFIG_<configName> environment variables. |
| Persistent state | Database and logs remain in the package’s configured paths. | Mount a host directory to /data; without that volume, a recreated container can lose state. |
| SuperUser password | Set once with the server’s --set-su-pw option. |
Set with MUMBLE_SUPERUSER_PASSWORD when creating the container. |
| Certificates | Install readable certificate and key files on the host and reload Murmur. | The ACME-enabled image variant can obtain and renew certificates when its email, domain, persistence, and challenge settings are supplied. |
Install Murmur natively on an Ubuntu VPS
1. Update the operating system
Log in over SSH with an account that can use sudo, apply security updates, and install the package. On Ubuntu, the usual sequence is:
sudo apt update
sudo apt upgrade
sudo apt install mumble-serverOther distributions may use a different package manager or package name. Use the service name and configuration path installed by that distribution rather than copying Ubuntu paths blindly.
2. Start the service and inspect its state
Start Murmur through the distribution’s service manager and enable it at boot:
sudo systemctl enable --now mumble-server
sudo systemctl status mumble-server
sudo journalctl -u mumble-server --no-pager -n 100The status output should show an active process. The journal is the first place to look for an invalid INI setting, a certificate permission error, a port conflict, or a database path that is not writable.
3. Set the SuperUser password before inviting users
SuperUser is a special account that bypasses all access controls. It is for initial setup and emergency administration, not for routine use. Set a long, unique password and save it in a password manager:
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
sudo mumble-server --set-su-pw 'use-a-long-random-password'Some package versions document the equivalent -supw form. The executable also documents --ini <inifile>, --foreground, and --verbose options. If the package uses a wrapper or a different binary path, run the command shown by that package’s man page. Avoid putting the password in shell history; use a temporary protected session or clear the history entry after setting it.
After logging in as SuperUser, create a named ordinary account and grant it only the groups and ACL permissions it needs. Daily administrators should use that account so an accidental ACL change cannot be made with an all-powerful identity.
Configure the Murmur INI file
Murmur’s configuration format is deliberately simple: one key=value assignment per line. Blank lines are ignored, and text after a # is treated as a comment. Edit the INI file supplied by your package (often a file under /etc), make a backup, and restart or reload the service after changes.
sudo cp /etc/mumble-server.ini /etc/mumble-server.ini.backup
sudo editor /etc/mumble-server.iniThe path above is common on Debian-family systems, but confirm the actual path from the service unit or package documentation. A configuration can contain settings like these:
| Setting | Purpose and guidance |
|---|---|
welcometext |
Message shown to connecting users. Keep it short and include community rules or a support channel if useful. |
port |
Listening port for the first virtual server. The default is 64738. If you select another value, change the firewall and every client connection to match. |
users |
Maximum simultaneous users for the virtual server. Set a deliberate ceiling that fits the VPS and bandwidth plan. |
serverpassword |
Password required to join. Leave it set for a private server; it must be empty for public registration. |
bandwidth |
Per-user bandwidth limit in bits per second. The documented default is 558000; it is a configuration default, not a promise that the VPS can sustain unlimited users. |
registerHostname |
Public DNS name used when registering the server in the public browser. It must resolve publicly. |
icesecretread and icesecretwrite |
Secrets protecting ICE read and write operations. Use them whenever ICE is enabled, and still restrict the port by address and firewall. |
| Database and log paths | Keep both on persistent storage with ownership that allows the Murmur service account to read and write them. |
Additional virtual servers use additional ports, incrementing from the first bound port. For example, if the first virtual server is on 64738, the next one can use the next configured port. Open only the ports you actually assign; do not expose a broad range “just in case.”
Open only the voice ports
For a default installation, clients need both protocols on port 64738:
- TCP 64738: control and connection traffic.
- UDP 64738: low-latency voice packets.
If you use UFW, an example rule set is:
sudo ufw allow 64738/tcp
sudo ufw allow 64738/udp
sudo ufw status verboseApply equivalent rules in the VPS provider’s firewall or security group. If you change port, update the operating-system firewall, cloud firewall, NAT rules, and client bookmarks together. Keep SSH restricted to your administration addresses where practical. Never add the ICE administration port to a public “allow all” rule.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Protect ICE administration
ICE is powerful enough to administer every virtual server in the Murmur process. The Mumble documentation warns that anyone who can reach an ICE port without configured secrets has full administrative access. Treat an exposed ICE listener as a complete server compromise.
Preferred arrangement: bind ICE privately
Bind ICE to localhost or a private management interface so it is not routable from the internet. Then administer it through a local tool, an SSH tunnel, or a private network. Confirm the listener with a socket inspection command and verify that its address is not the public VPS address.
If ICE must cross a network
- Set strong, randomly generated
icesecretreadandicesecretwritevalues. - Allow the ICE port only from specific administrator addresses in both host and provider firewalls.
- Do not reuse the SuperUser password or any other credential.
- Review logs for unexpected connection attempts and rotate the secrets if an administrator’s device or network is compromised.
After changing ICE settings, restart or reload Murmur as required by the package and test administration from an approved network. A closed port is safer than an ICE service that is reachable but protected only by an unknown firewall assumption.
Configure TLS correctly
Use a certificate whose name matches the DNS name clients enter. If users connect as voice.example.net, the certificate must cover that name; a certificate for an unrelated hostname will produce warnings or failed verification. Keep the private key readable by the Murmur service account but not by ordinary users.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Obtain a certificate and private key from a trusted certificate authority, or use the ACME-enabled container variant described below.
- Store the files in a root-owned directory with restrictive permissions.
- Set the certificate and key paths in the Murmur configuration using the names expected by your package version.
- Check ownership and permissions so the service account can read both files without making the key world-readable.
- Restart Murmur for the first installation, then use the documented reload signal for later certificate renewals so active service is not unnecessarily interrupted.
On systems using systemd, the reload signal can be sent explicitly with a command such as:
sudo systemctl kill --signal=HUP mumble-serverConfirm in the service journal that the new certificate loaded. Test the hostname, expiration date, and certificate chain from a client on another network. Renewal is not complete until the renewed files are in place, Murmur has reloaded them, and a client sees the new expiration date.
Optional public registration
Private communities should leave public registration disabled. To appear in the public server list, the Mumble documentation requires all of the following:
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
serverpasswordis empty.- The server is reachable worldwide, not merely from your own LAN or a restricted VPN.
- A valid TLS certificate is configured, or Murmur’s automatically generated self-signed certificate is being used.
registerHostnameresolves publicly to the server.
Public listing increases unsolicited connections and makes a stable DNS name and certificate especially important. If a server is listed unexpectedly, check that serverpassword was not accidentally cleared and inspect the registration-related settings.
Run Murmur with Docker
Docker is useful when you want an image version that is independent of the host distribution. Install Docker using your operating system’s supported method, create a persistent directory, and run a pinned image tag. The official example publishes both required protocols and mounts ./data/mumble to /data:
docker run --detach
--name mumble-server
--publish 64738:64738/tcp
--publish 64738:64738/udp
--volume ./data/mumble:/data
--restart on-failure
mumblevoip/mumble-server:<tag>Replace <tag> with a tested release tag. Tags such as vX.Y.Z identify stable releases; latest tracks the newest image and is less predictable for unattended upgrades. Create the host directory first and include it in your backup plan:
mkdir -p ./data/mumble
sudo chown -R <container-user>:<container-group> ./data/mumbleThe correct ownership depends on the image’s runtime user. If the container exits immediately, inspect ownership and the container log:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesdocker ps -a
docker logs mumble-serverConfiguration settings can be passed as environment variables named MUMBLE_CONFIG_<configName>. The administrative password can be supplied with MUMBLE_SUPERUSER_PASSWORD. Do not place secrets in a public compose file or shell script committed to source control; use a protected environment file or secret-management facility and restrict its permissions.
The ACME-enabled image variant can issue and renew certificates when you provide an account email, the public domain, persistent storage for the ACME account and certificates, and either HTTP or DNS challenge settings. Ensure the selected challenge can reach the container from the internet and that any required challenge port is allowed temporarily or continuously, depending on the method. Certificate automation does not remove the need to verify hostname, renewal, and Murmur reload behavior.
Validate the installation from outside the VPS
- Check the native service or container status and read its recent logs.
- Confirm that Murmur listens on the intended TCP and UDP port. Verify both protocols, not just a TCP connect test.
- From a different network, connect with the VPS DNS name or IP and the configured port.
- Log in with the SuperUser account, then create and test an ordinary administrative account.
- Join as a normal user and verify channel permissions, welcome text, and the user limit.
- Use a firewall or port-scan view from an untrusted network to confirm that ICE is not publicly reachable.
- Inspect the certificate hostname, expiry, chain, file permissions, and reload behavior.
- Restart the service or container and verify that the database, channels, ACLs, registrations, and credentials persist.
- If public registration is enabled, verify DNS resolution from outside your hosting network and confirm that
serverpasswordis empty.
Troubleshooting common failures
Clients can connect but have no audio
Check UDP 64738 in both the host and provider firewalls. Confirm that the client is using the same port configured in the INI file and that the VPS plan permits UDP. A successful TCP connection alone does not prove that voice packets can pass.
The service will not start after an edit
Read the system journal or container log for the exact key, value, or file that failed. Restore the last known-good INI backup, start the service, then reapply one change at a time. Common causes are a typo in a key, a path that does not exist, invalid permissions, or another process already using the selected port.
The certificate is rejected
Make sure users connect with the hostname covered by the certificate, not an alternate alias or raw IP. Check that the private key and certificate match, that the service account can read them, and that the full chain is present when your certificate authority requires it. Reload Murmur after renewal and check the certificate from a remote client.
SuperUser login fails
Confirm that you are connecting to the intended virtual server and that the password was set for that Murmur instance. For a native installation, run the password command against the same INI file used by the service. For Docker, verify the container’s persistent /data volume and the environment variable used at first startup. Do not repeatedly overwrite the password without checking which instance is listening.
Settings disappear after a Docker restart
Inspect the container definition and verify that the host directory is mounted to /data. A container’s writable layer is not a backup. Stop the container, copy the persistent directory, and recreate the container with the same mount before making further changes.
The server does not appear in the public list
Check all four registration prerequisites: empty serverpassword, worldwide reachability, valid TLS, and a publicly resolving registerHostname. A private firewall, split-horizon DNS, certificate mismatch, or non-empty password prevents listing.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Backups, upgrades, and operational hygiene
Back up the Murmur database and configuration together. Include certificates and private keys only in an encrypted backup with access limited to administrators. Test restoring to a temporary instance; a backup that has never been restored is only an assumption.
For native installations, review package changelogs before upgrades, copy the INI file, upgrade during a maintenance window, and inspect the journal afterward. For Docker, pull the pinned replacement tag, stop the old container, retain the same /data mount, start the new container, and verify clients, channels, ACLs, and certificates before deleting the old image. Keep one known-good image tag available for rollback.
Monitor disk usage, log growth, certificate expiry, process restarts, and bandwidth consumption. Set an explicit user limit and review it when the community grows; the documented 558000-bit-per-user default is not a substitute for measuring the VPS’s actual CPU, network, and bandwidth capacity.
Quick Recap
Deployment decision checklist
- Use the native package when you want the distribution to manage service startup, logs, and updates.
- Use Docker when you need reproducible image versions, isolated filesystems, or the image’s certificate automation, and you are prepared to manage persistent volumes.
- Whichever model you choose, expose only TCP and UDP on the selected voice port.
- Keep ICE private, protected by secrets, and restricted by firewall rules.
- Use a strong SuperUser password once, then administer daily operations with ordinary accounts and ACLs.
- Back up persistent data, test restoration, and verify certificates and UDP after every upgrade.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
