The Mumble client for Windows uses a standard installer. During the first launch, do not skip certificate creation or the initial voice-chat setup.

1. Download the current installer from the download section above.
2. Run the file and approve the Windows security prompt.
3. Keep the Mumble client component selected. A regular hosted-server customer does not need to install the server component.
4. Finish the installation and launch Mumble.
5. Create a certificate, complete the Audio Wizard, and add your hosted server.

Related guides: Certificates · Connecting to a server

Most Linux distributions provide the Mumble client in their standard repositories. It can connect directly to a hosted voice server.

# Debian / Ubuntu
sudo apt update
sudo apt install mumble
# Fedora
sudo dnf install mumble
# Arch Linux
sudo pacman -S mumble

1. Install the package with your distribution’s package manager.
2. Launch Mumble from the application menu or by running mumble.
3. Check the selected input and output devices.
4. Create a certificate, complete the Audio Wizard, and add the server.

On macOS, the Mumble client installs like a normal application and then requires microphone permission.

1. Download the current macOS package.
2. Move Mumble to the Applications folder.
3. Launch the application.
4. Allow microphone access.
5. If access was denied, open System Settings → Privacy & Security → Microphone.
6. Complete the Audio Wizard.

Mumble uses a client certificate as a persistent digital identity. A nickname alone does not prove that you are the same registered user.

1. Create a new certificate during the first launch.
2. After signing in, export it to a file.
3. Protect the exported file with a password.
4. Store a backup separately from the computer.

Related guides: V4Game administrator · Certificate backup

To connect to a Mumble Server, you need its voice-server address, port, username, and, when configured, a server password.

1. In the main menu, go to Server → Connect.
2. In the connection window, select Add New.
3. Enter a descriptive bookmark name in Label.
4. Enter the voice-server hostname in Address, not the website URL.
5. Enter the port shown in the V4Game control panel.
6. Enter your nickname or administrator login.
7. Save the bookmark and select Connect.

The Mumble Audio Wizard helps you select the correct microphone, playback device, voice level, and transmission method.

1. Open Configure → Audio Wizard.
2. Select the correct Input Device and Output Device.
3. Check that the microphone indicator responds to your voice.
4. Adjust the level without clipping or excessive background noise.
5. Choose Push-to-Talk or Voice Activity.
6. Finish the test and verify the result with another user.

Related guides: Push-to-Talk · Audio problems

Mumble Push-to-Talk transmits only while you hold a chosen key. It is usually the most reliable mode for a gaming voice server.

1. Open Configure → Settings.
2. Select Push-to-Talk under Audio Input.
3. Open Shortcuts.
4. Add a Push-to-Talk action.
5. Assign a convenient key and check that it does not conflict with game controls.

Voice Activity starts transmission automatically when the input level exceeds the configured threshold.

1. Select Voice Activity in the input settings.
2. Set the lower threshold above the normal background-noise level.
3. Set the upper threshold so normal speech starts transmission reliably.
4. Test the setup both in silence and during normal computer use.

• Download the current client from the verified V4Game download page.
• Use a headset and Push-to-Talk as safe initial settings.
• Export the certificate immediately after the first successful sign-in.
• Never share one certificate between several people.
• Save the server address, port, and purpose in a clearly named bookmark.

Common mistakes

• Confusing the website URL with the voice-server address.
• Skipping the Audio Wizard.
• Keeping the only certificate backup on the same disk.

Mumble binds the server-side identity to the client certificate. The V4Game administrator therefore needs a certificate that is used for the first correct administrator sign-in.

1. Obtain the automatically generated administrator login and password from the V4Game control panel.
2. Before the first admin sign-in, create a new Mumble certificate or select a certificate that will be used only for this administrator.
3. Enter the administrator login in the server bookmark and connect using the administrator password.
4. After the successful sign-in, export the certificate immediately and protect the backup with a password.

Why this is necessary: the server identifies a user not only by the entered name but also by the certificate. Signing in with the wrong certificate creates a conflict between the expected administrator identity and the client identity that has already been used.

Related guides: Your first certificate · Certificate backup · SuperUser

After a server is ordered, the V4Game panel automatically creates a separate administrator account. It has SuperUser-level permissions but can also speak normally in voice channels.

Use this account for routine administration of channels, users, groups, and ACLs. Keep the built-in SuperUser account as an emergency access method.

1. View the generated login and password in the control panel.
2. Create a separate new certificate before the first sign-in.
3. Enter the administrator login in the server bookmark.
4. Connect with the administrator password.
5. Export the certificate and store a protected backup.

Related guides: SuperUser · Certificates

SuperUser is the built-in highest-level Mumble Server account. Its password can be changed in the V4Game panel.

Use SuperUser for initial configuration, emergency ACL recovery, or repair of lost permissions. The separate V4Game administrator is better for everyday voice use.

1. Change the SuperUser password in the control panel.
2. Create a separate bookmark with the username SuperUser.
3. Connect using the new password.
4. Perform the required recovery or administrative action.

The control panel manages the server process without requiring operating-system access.

• Stop — stops the voice server and disconnects users.
• Restart — restarts the Mumble Server process.
• Repair — performs a recovery operation when a normal restart is not sufficient.
• Delete — removes the server.

Settings lets you change the server name, server password, Welcome Message, port, default channel, Remember Last Channel, Hide Ping, and Enable Logs.

1. Open the server in the V4Game panel and select Settings.
2. Change only the required options.
3. Save the configuration.
4. Restart the server when the panel indicates that it is necessary.
5. Verify the result with a normal user account.

A customer can select an available port from 1024 upward at no additional cost.

1. Open Settings.
2. Enter the preferred available port.
3. Save the change.
4. Update the bookmark on every device.
5. Notify all users of the new port.

The server password controls initial connection to the server. It does not replace user registration, groups, or ACL permissions.

1. Open Settings.
2. Set or change the server password.
3. Save the configuration.
4. Share the password only with the intended users.

The Welcome Message is displayed after connection and can contain rules, administrator contacts, and short navigation instructions.

1. Choose a concise and recognisable server name.
2. Add a short welcome message and rules.
3. Avoid oversized images and complex markup.
4. Check the final appearance in the Mumble client.

The slot count defines the maximum number of users who may be connected at the same time.

1. Open the tariff or server-management page.
2. Select the new slot count.
3. Confirm the change.
4. Verify the updated limit.

The panel imports and exports the Mumble database in .sqlite format. It contains channels, registered users, groups, and ACLs.

1. Select Export before major changes.
2. Save the file with a date in its filename.
3. To restore data, open Import and select the required database.
4. Restart the server after import when necessary.
5. Verify channels, groups, users, and ACLs.

Logs help analyse server startup, connections, disconnections, and selected administrative events.

1. Open Logs in the server panel.
2. Locate events around the time of the problem.
3. Compare them with the user’s actions.
4. Before contacting support, copy only the relevant lines and remove unnecessary personal data.

The current API is intentionally simple. Documentation should describe only functions that are already available.

MumbleViewer, web-panel Kick/Ban, and other planned functions should be documented after they are released.

• Use the V4Game admin account for daily work and keep SuperUser as emergency access.
• Create a dedicated certificate before the first admin sign-in. If you already entered without admin credentials, recreate the certificate.
• Export the SQLite database before Import, Repair, deletion, or major Settings changes.
• Change settings in small groups and verify the result after Restart.
• Do not document planned API features as if they were already available.

Common mistakes

• Using SuperUser as an ordinary voice account.
• Changing the port without notifying users.
• Importing a database without first exporting the current one.

Registration binds a user account to its certificate and makes it possible to assign persistent groups and ACL entries.

1. The user connects with their permanent certificate.
2. An administrator right-clicks the user.
3. Select Register.
4. After registration, add the account to a group or a personal ACL where necessary.

The Registered Users list lets administrators find accounts, rename them, and remove registration.

1. In the Server menu, open Registered Users.
2. Find the required account.
3. Use Rename to change its name.
4. Ask the user to reconnect.
5. Remove registration only when it is definitely no longer required.

Administrators and moderators can use moderation actions according to their ACL permissions.

• Mute — prevents the user from transmitting voice.
• Deafen — prevents the user from hearing others.
• Kick — disconnects the user without a persistent block.
• Ban — blocks the user from reconnecting.
• Move — moves the user to another channel.

1. Choose the least restrictive action that resolves the situation.
2. For Kick or Ban, provide a clear reason.
3. Verify the selected user and, for a ban, the duration.

Mumble channels may be permanent or temporary. A temporary channel is removed after its last user leaves.

1. Right-click the server root or the intended parent channel.
2. Select Add.
3. Enter a name and description.
4. Leave Temporary disabled for a permanent channel.
5. Set position and user limit when required.
6. Review the inherited ACL after creation.

A permanent channel can be renamed, repositioned, limited, or deleted.

1. Open Edit for the channel.
2. Change the required options.
3. Before deletion, review child channels.
4. After any structural change, verify inherited groups and ACLs.

An Access Token is a secret text value that grants access to a protected channel without permanent group membership.

1. Obtain the token from the server administrator.
2. In the Server menu, select Access Tokens.
3. Add the value without leading or trailing spaces.
4. Apply the change and try to enter the channel again.

Whisper lets you speak to a specific user, group, or channel without leaving your current channel.

1. Open Shortcuts.
2. Add a Whisper/Shout action.
3. Choose the target.
4. Assign a dedicated key.
5. Check the transmission indicator so that normal speech and Whisper are not confused.

Linked channels let users hear voice between several rooms. Actual Speak and listening behaviour still depends on ACLs.

1. Verify that the administrator has Link Channel permission.
2. Link the required channels.
3. Check Speak and listening permissions.
4. Test the arrangement with normal users.
5. Remove the link when it is no longer needed.

The Mumble Overlay displays active speakers over the game window.

1. Open Configure → Settings.
2. Enable Advanced if the Overlay section is hidden.
3. Enable Overlay and configure its appearance.
4. Launch the game.
5. If it does not appear, check display mode and privilege level.

• Register permanent users and manage access through groups.
• Build a short, understandable channel tree.
• Give moderators only the permissions they need: Move, Mute/Deafen, and Kick; add Ban only when required.
• Use tokens for temporary access instead of shared administrator accounts.
• Before deleting a channel, check child channels, groups, and ACLs.

Common mistakes

• Creating dozens of empty channels.
• Trying to place an unregistered user in a persistent group.
• Giving moderators Write ACL without a clear need.

Mumble ACL is the channel permission system. It determines who can see a channel, enter it, speak, send text, and perform administrative actions.

Channels normally inherit groups and ACL rules from parent channels. A mistake at the root level can therefore affect the entire server.

1. Open Edit for the required channel.
2. Select the ACL tab.
3. Review inherited rules first.
4. Choose a user or group.
5. Set whether the rule applies to this channel, subchannels, or both.
6. Select the required Allow or Deny permissions.
7. Test the result with a normal user account.

ACL entries are processed in order. When several entries affect the same permission, the entry positioned lower in the list has higher priority.

Example: an upper @all rule denies Enter, while a lower members rule allows Enter. A member can enter if inheritance and all other relevant rules are configured correctly.

1. Place broad restrictions near the top.
2. Place exceptions for groups and individual users below them.
3. Review inherited entries as well as local entries.
4. Test as a guest, member, moderator, and administrator.

A channel may inherit ACL rules and groups from its parent.

• Inherit ACLs — use parent-channel rules.
• Applies to this channel — apply the rule here.
• Applies to subchannels — apply the rule below this channel.

1. Start analysis at the root channel.
2. Do not disable inheritance without a clear reason.
3. After every change, test child channels.
4. Document intentionally isolated branches.

Mumble provides special groups that describe a user’s authentication state or position in the channel tree.

• @all — all users covered by the rule.
• @auth — authenticated or registered users.
• @in — users currently in the relevant channel.
• @out — users outside the relevant channel.
• @sub — users in subchannels of a specified part of the tree.

Labels may vary slightly between versions, but their purpose remains broadly consistent.

• Traverse / Access — see or pass through the channel tree.
• Enter — enter a channel.
• Speak — transmit voice.
• Whisper — whisper to the channel.
• Text Message — send text messages.
• Make Channel / Make Temporary Channel — create channels.
• Link Channel — link channels.
• Move — move users.
• Mute/Deafen, Kick, and Ban — moderation.
• Register / Self Register — register accounts.
• Write ACL — edit permissions.

Mumble groups simplify permission management when several registered users need the same access.

1. Register the users.
2. Open Groups in the channel properties.
3. Create a role such as members, moderators, or leaders.
4. Add the relevant accounts.
5. Configure inheritance.
6. Create an ACL entry for the group.

A Guest Channel in Mumble allows new or unregistered users to join without exposing the server’s internal channels.

Server
├── Guest
└── Members ├── Team 1 └── Team 2

In the internal branch, Enter is denied to general guests. In Guest, a lower rule allows Enter and Speak. The registered members group is allowed to enter Members, while moderators receive Move permission.

1. Create a permanent Guest channel.
2. Configure the initial channel for new users.
3. Deny Enter to guests in the internal branch.
4. Add a lower-priority exception for Guest.
5. Test with a new, unregistered certificate.
6. Verify that a moderator can move the guest.

A Jail Channel in Mumble is a practical ACL design for temporarily isolating a disruptive user without fully banning them from the server.

• Users cannot enter it voluntarily.
• A user moved into it must not be able to leave independently.
• Speak and text may be denied when required.
• Moderators retain Enter, Speak, and Move permissions.

1. Create a permanent Jail channel.
2. For @all, deny Enter.
3. Configure restrictions for a user who is already inside, taking the Traverse, Enter, and Move permissions of your channel structure into account.
4. When required, deny Speak and Text Message.
5. In a lower rule, allow the moderators group Enter, Speak, and Move.
6. Move a test user into the channel and verify that the user cannot leave.

Several common patterns that can be adapted to your server.

Private team channel

• @all: Enter — Deny.
• team-a below it: Enter and Speak — Allow.
• moderators: Enter, Move, Mute/Deafen — Allow.

Listen-only channel

• @all: Enter — Allow, Speak — Deny.
• speakers below it: Speak — Allow.

Registered users only

• @all: Enter — Deny.
• @auth below it: Enter — Allow.

Temporary rooms for members

• members: Make Temporary Channel — Allow.
• Do not grant Make Channel when permanent channels should be created only by an administrator.

The following are practical baseline architectures rather than abstract permission lists. In every design, broad restrictions are placed above and exception rules below because a lower ACL entry has higher priority.

1. Gaming server or public community

Root
├── Lobby / Guest
├── Games
│ ├── Game A
│ └── Game B
└── Staff

• Lobby: @all receives Enter, Speak, and Text Message.
• Games: an upper @all rule may deny Enter to unregistered users; below it, @auth or members allows Enter and Speak.
• Staff: upper @all — Enter Deny; lower moderators — Enter, Speak, Move, Mute/Deafen, Kick.
• Temporary rooms: the members group may receive Make Temporary Channel but not Make Channel.

Why it works: a guest always has a safe entry point, registered members receive access to internal channels, and administrative permissions remain isolated in Staff.

2. Clan or team server

Root
├── Recruitment
├── Clan
│ ├── Squad 1
│ ├── Squad 2
│ └── Leaders
└── AFK

• Recruitment: available to guests; recruiters receive Move and Register.
• Clan: upper @all — Enter Deny; lower clan-members — Enter and Speak.
• Squad 1 / Squad 2: separate squad-1 and squad-2 groups receive Enter; leaders may use Whisper or channel linking.
• Leaders: access is limited to leaders; a lower moderator rule ensures that administrators do not lose access.
• AFK: Enter is allowed and Speak is denied for @all.

Why it works: membership is managed through groups, permissions are not duplicated for every user, and leaders receive a separate communication area.

3. Corporate or workplace server

Root
├── Reception
├── Departments
│ ├── Support
│ ├── Development
│ └── Management
└── Meetings

• Reception: a place for external guests; Speak is allowed, while access to Departments is denied.
• Departments: each department has its own group; upper @all — Enter Deny, lower department rule — Enter Allow.
• Management: a separate management group; text and voice are available only to its members and administrators.
• Meetings: organisers may be allowed to create temporary channels; permanent channels are created only by administrators.
• Moderation: IT staff or administrators receive Move and Mute/Deafen, while Write ACL remains restricted to a small trusted group.

Why it works: the model follows organisational roles, applies least privilege, and avoids personal ACL entries for every employee.

Testing only as SuperUser or a full administrator does not reveal what ordinary users will experience.

1. Export the SQLite database.
2. Create a separate guest certificate.
3. Create a registered-member test account.
4. Create a test moderator if required.
5. Test visibility, Enter, Speak, text, Move, and leaving restricted channels.
6. Remove test accounts after verification.

Channels, groups, ACLs, and registered users are stored in the server database.

1. Open Export in the V4Game panel.
2. Download the SQLite file.
3. Add the date to its filename.
4. Make the ACL changes.
5. If access is lost, use SuperUser or restore the database through Import.

• Place broad rules above and exceptions below.
• Create groups at the highest common channel where their inheritance should begin.
• Do not use Deny when simply withholding Allow is sufficient.
• Always test as a guest, registered member, moderator, and administrator.
• Keep a short description of the purpose of every non-standard permission design.

Common mistakes

• The exception is positioned above the general denial.
• An inherited rule is overlooked.
• Deny is unintentionally applied to all subchannels.
• Testing is performed only as SuperUser.

A Mumble certificate is the user’s digital identity. Protect its backup as carefully as an administrator password.

1. Open certificate management.
2. Export the current certificate.
3. Set a strong password.
4. Store the backup separately.
5. On a new device, import it before the first connection.

Use a separate certificate for the V4Game administrator login. Do not mix it with the certificate of an ordinary user.

1. Create a new certificate before the first admin sign-in.
2. Connect with the administrator login and password.
3. Export the certificate.
4. After changing the login, verify the new certificate binding.

• Export a certificate immediately after registration or the first administrator sign-in.
• Protect the file with a separate strong password.
• Keep at least one backup away from the computer.
• Use separate certificates for separate administrative identities.
• After a token leak, replace the token rather than merely asking users not to use it.

Common mistakes

• Assuming that a nickname restores registration.
• Giving the certificate to another person.
• Using one token for every protected channel.

On Android, use a compatible Mumble Client that connects to a voice server by hostname and port.

1. Install a compatible client from a trusted source.
2. Create a server profile.
3. Enter the address, port, username, and password.
4. Allow microphone access.
5. Choose Push-to-Talk or Voice Activity.
6. If the connection stops when the screen is locked, allow background operation.

On iPhone and iPad, use a compatible Mumble Client with microphone access and support for Mumble servers.

1. Install a compatible client.
2. Add the address, port, and nickname.
3. Allow microphone access.
4. Check whether audio is routed to the receiver, speaker, wired headset, or Bluetooth device.
5. Save the profile.

• Install clients only from a trusted store or source.
• Review microphone and background-operation permissions.
• Use Push-to-Talk on unstable mobile connections.
• Check audio routing after connecting Bluetooth devices.
• Do not expect every desktop-client feature to be available on mobile.

Common mistakes

• Android closes the client because of battery optimisation.
• Audio is routed to the phone speaker instead of the headset.
• Mobile-network instability is mistaken for a server problem.

A certificate warning may refer to the server certificate or to the user’s personal client certificate.

1. Verify the server address.
2. If the server fingerprint changed, ask V4Game support whether the certificate was renewed.
3. Do not accept an unexplained change automatically.
4. If the server no longer recognises your account, import the old client certificate.
5. For the V4Game admin account, verify that you are using its separate certificate.

When Mumble has no sound, the microphone does not work, or users hear noise or echo, begin with local audio devices and operating-system permissions rather than ACLs.

Reducing noise

• Do not place the microphone directly beside a fan.
• Reduce microphone gain or boost.
• Use Push-to-Talk.
• Set an appropriate Voice Activity threshold.

1. Check Mute and Deafen.
2. Verify Input Device and Output Device.
3. Run the Audio Wizard.
4. Check the system microphone permission.
5. Close applications that may hold exclusive access to the audio device.
6. Reduce Microphone Boost.
7. Use headphones to prevent echo.
8. For Bluetooth, verify the active profile.

V4Game currently uses one OVH location with AntiDDoS, so latency depends on the network route from each user to that location.

1. Test without a VPN or proxy.
2. Use Ethernet or stable 5/6 GHz Wi-Fi.
3. Pause downloads, torrents, cloud synchronisation, and video streaming.
4. Check packet loss and stability, not only download speed.
5. Compare another network.
6. For support, record the time of the problem and a traceroute.

Common causes include an incorrect address or port, a stopped server, a server password, or firewall restrictions.

1. Compare the address and port with the V4Game panel.
2. Verify that the server is running.
3. Check the server password.
4. Perform Restart.
5. Try another network.
6. Review Logs.
7. Send support the exact error message.

A client connecting to a hosted Mumble Server does not require port forwarding on the home router.

Port forwarding is mainly required when someone runs a server inside their own private network.

A firewall may block Mumble itself or outbound connections to the assigned server port.

1. Allow Mumble through the system firewall.
2. Review antivirus network rules.
3. Allow outbound TCP and UDP traffic to the server address and port.
4. Restart the client.
5. On a corporate or guest network, contact the network administrator or test another connection.

If an incorrect ACL or certificate prevents administrator access, use the available recovery mechanisms.

1. Try the SuperUser account.
2. Verify the SuperUser password in the panel.
3. Check the dedicated V4Game admin certificate.
4. Restore the previous SQLite database through Import.
5. Use Repair or contact support when necessary.

Short answers to common customer questions.

Can I change the port for free?

Yes. You can choose an available port from 1024 upward.

Can I change the server location?

Not currently. V4Game uses one OVH location with AntiDDoS.

What does Export contain?

The Mumble database in SQLite format.

How does the V4Game admin differ from SuperUser?

It has full administrative permissions and can also speak in channels.

Why does an ACL not work?

Check inheritance and order: a lower ACL entry has higher priority.

Do I need port forwarding?

No, not for a normal client connecting to a hosted server.

• Record the exact error message and the time it occurred.
• Change one setting at a time.
• Compare another network, device, or certificate.
• For ACL problems, check order and inheritance; for audio problems, check local devices and permissions.
• Before Repair or database restoration, preserve the current Export.

Common mistakes

• Disabling the entire firewall immediately.
• Deleting the server because of an ACL mistake.
• Judging network quality only by download speed while ignoring ping and packet loss.