Simple Voice Chat UDP Port 24454: Firewall and Hosting Fix

Q: Can I use the same port as Minecraft?

No. port=-1 does that, and the wiki warns it may crash the server because the query uses UDP on the game port. Give voice chat its own port.

Q: Why does the plug icon still show after opening the port?

Check that port= matches the allocation, that voice_host is empty, that you restarted the server, and that the client mod version matches.

Published on 2026-06-17 | Updated 2026-09-28

Simple Voice Chat uses UDP port 24454 by default. How to give it a working UDP port on a hosting panel with an extra allocation, and how to open it in Linux firewalls, Windows Firewall and routers.

Voice chat plugin

Simple Voice Chat usually shows "not connected" because its UDP port is not reachable from the internet. Minecraft itself can work perfectly while the voice chat stays disconnected, because Minecraft Java uses TCP and the voice chat sends its audio over UDP on a separate port.

Quick fix

Give voice chat its own UDP port, on the same public IP as your Minecraft server, and put that port in the voice chat config.

Protocol: UDP
Default port: 24454
Config file: config/voicechat/voicechat-server.properties for mods, plugins/voicechat/voicechat-server.properties for Paper and Spigot
Property: port=
Restart required: yes

On a hosting panel the port you use is the one the panel gives you, not necessarily 24454. On a Space-Node server you create it yourself in the Network tab with Create Allocation. That is free, and your plan includes three allocations. If you need more, we can raise it to five on request.

Why TCP 25565 is not enough

Minecraft Java listens on TCP, 25565 by default. Simple Voice Chat sends real-time audio over UDP, which suits voice because it does not wait for lost packets to be resent.

So these can both be true:

Players can join the Minecraft server.
Simple Voice Chat still says not connected.

Reinstalling the mod will not fix that. Making the voice port reachable will.

Hosting panel fix (Pterodactyl and Pelican)

Panel hosts run each server in a container. Only ports that are allocated to your server reach it. The voice chat port has to be one of those allocations.

On Space-Node:

Open the Network tab of your server.
Click Create Allocation and note the new port.
Put that port in the voice chat config:

port=25590
bind_address=
voice_host=

Use your own allocation's port instead of 25590. Leave bind_address and voice_host empty. The official wiki says not to change voice_host unless you know exactly why you need it, and on a Space-Node server the allocation's port is the same inside and outside the container, so there is nothing to redirect.

Restart the server after editing. If it still fails after that, ask in live chat.

The extra port costs nothing on our Minecraft server hosting: three allocations are included, and up to five on request.

On another host, look for that host's own guide. The Simple Voice Chat wiki keeps a list of hosting guides and warns: "Do not follow guides that are not for your specific hoster!"

Linux firewall fix

If you manage your own VPS, open the voice port for UDP. The examples use the default 24454.

UFW:

sudo ufw allow 24454/udp
sudo ufw reload

Firewalld:

sudo firewall-cmd --permanent --add-port=24454/udp
sudo firewall-cmd --reload

iptables:

sudo iptables -A INPUT -p udp --dport 24454 -j ACCEPT

Running the server in Docker yourself? Publish the port as UDP. The wiki is explicit: use 24454:24454/udp, because plain 24454:24454 only maps TCP.

Router port forwarding fix

For home-hosted servers:

Open your router admin page.
Find Port Forwarding.
Add UDP 24454.
Forward it to the local IP of the Minecraft server PC.
Make sure Windows Firewall also allows UDP 24454.

Do not forward only TCP. Voice will still fail.

Windows Firewall fix

On the server PC:

Open Windows Defender Firewall.
Advanced settings.
Inbound Rules.
New Rule.
Port.
UDP.
Specific local ports: 24454.
Allow the connection.
Apply to private and public networks if needed.

How to test the UDP port

Normal online port checkers cannot test this port. The wiki explains why: UDP is connectionless, and only the application itself can answer. A checker will often report the port as closed even when voice chat works.

Checks that do work:

In game, run /voicechat test PlayerName. It needs voicechat.admin, which operators have by default.
From a PC, use svc-cli-utils, the tool the wiki links to: svc ping your.server.address:24454 while the server is running.
In the console, look for the line saying the voice chat server started on your port.

Common error: port already in use

If the server log says:

Failed to run voice chat at UDP port 24454, make sure no other application is running at that port

then another process already uses the port. On a Minecraft server that is often Geyser or the server query. The query uses UDP and Geyser uses its port over TCP and UDP, so neither may share a port with voice chat. Move voice chat to its own allocation.

FAQ

What is the default Simple Voice Chat UDP port? 24454. On a hosting panel, use the port of the allocation you created for it.

Does Simple Voice Chat need TCP or UDP? UDP. Opening TCP alone will not fix voice chat.

Can I use the same port as Minecraft? No. port=-1 does that, and the wiki warns it may crash the server because the query uses UDP on the game port. Give voice chat its own port.

Can voice chat share a port with Geyser? No. Geyser uses its port over TCP and UDP, and the Geyser setup guide says no other program can use it, voice chat mods included. Give each one its own port.

Why does the plug icon still show after opening the port? Check that port= matches the allocation, that voice_host is empty, that you restarted the server, and that the client mod version matches.