Mumble server not reachable (UDP blocked): fix checklist

1) Confirm the basics (you’d be surprised)

• Are you connecting to the right hostname/IP?
• Is the port correct (default 64738)?
• Is the server actually running?

sudo systemctl status mumble-server.service --no-pager

# Is anything listening on 64738?
ss -lunpt | grep -E ':64738\b' || true

2) Check the provider firewall (cloud control panel)

Many VPS providers default to “deny inbound unless allowed”. You must allow UDP 64738 to the droplet.

DigitalOcean-specific: Open UDP 64738 in a DigitalOcean firewall.

3) Check UFW (host firewall)

If you use UFW:

sudo ufw status verbose

# Allow Mumble (UDP is the important one)
sudo ufw allow 64738/udp

# Optional TCP fallback
sudo ufw allow 64738/tcp

If UFW is disabled, make sure your provider firewall is doing the job instead.

4) Confirm DNS points where you think it points

DNS issues look like “server offline” even when the server is fine. If you use a subdomain (recommended), confirm it resolves to the droplet IP.

# From your local machine:
nslookup mumble.yourdomain.com

# Or:
dig +short mumble.yourdomain.com A

If you use Cloudflare DNS: Cloudflare DNS for a Mumble subdomain.

5) Common “it’s not the firewall” cases

• Wrong IP: you copied the private/VPC IP instead of the public IP.
• IPv6 mismatch: clients try IPv6 first; your firewall only opened IPv4 (or vice versa).
• NAT/port mismatch: you’re behind an unexpected NAT layer.
• Local network blocks: some workplaces/hotels block UDP broadly.

6) If you need evidence: log what’s happening

On the server, watch for connection attempts while you try to connect:

sudo journalctl -u mumble-server.service -f

If nothing appears, the packets probably aren’t reaching the server (firewall, routing, DNS).