Simple Voice Chat shows a plug icon and "not connected" when the client mod cannot reach the server's voice port. That is almost always a port problem, not a broken install: the mod might be missing on the server, the UDP port might not be open, or a host's networking setup needs one extra step. Work through the causes below in order; the first three clear most cases.
What the plug icon and not connected mean
Simple Voice Chat uses the same plug icon for two different situations: the mod not being installed at all, and the mod being installed but unable to connect. Press V to open the voice chat settings screen. If that screen opens normally, the mod is installed and the icon is a connection problem, not a missing install.
Confirm the mod or plugin is actually on the server
Simple Voice Chat needs a matching install on both sides. On a modded server it ships as a mod for Fabric, Forge, NeoForge, and Quilt, and every player also needs the client mod for their own loader and version. On a vanilla-based server it ships as a separate plugin for Bukkit, Spigot, Paper, Purpur, and Folia, installed only on the server; players still need the client mod either way. Velocity, BungeeCord, and Waterfall proxies have their own build too. See the Simple Voice Chat page for the current download links, and the plugin installation guide if you are setting up the Bukkit, Spigot, or Paper build for the first time.
Match the client and server versions
Like any Java mod, Simple Voice Chat only works when the client and server run the same major Minecraft version and a compatible build of the mod or plugin for that loader. A client on a newer or older version than the server, or a build meant for the wrong loader, fails to connect even if the port is open. Update or downgrade whichever side is out of step before troubleshooting further.
Open the voice chat's UDP port
This is the fix that clears most "not connected" reports. Simple Voice Chat needs an open UDP port, separate from the Minecraft server's own TCP port, and the client mod cannot reach the server without it.
- Default port: 24454/UDP. Check the port key in the server config in case it was changed.
- Config file: config/voicechat/voicechat-server.properties for Fabric, Forge, NeoForge, and Quilt, or plugins/voicechat/voicechat-server.properties for Bukkit, Spigot, and Paper.
- On a VPS or dedicated server, open the port in the server's own firewall and, if present, in the hosting panel's port or allocation settings.
- On a home network, open the port in your computer's firewall and forward it in your router, the same as any self-hosted server.
- With Docker, map the port as 24454:24454/udp specifically. Mapping 24454:24454 alone only forwards TCP and voice chat stays unreachable.
Fix it on a host that only gives you one port
Many Minecraft hosts, including Aternos, only open a single port per server, which conflicts with voice chat's default setup that expects its own separate UDP port. Aternos documents a specific fix for this: install the mod or plugin, start the server once to generate its config files, stop the server, open voicechat-server.properties, and change port = 24454 to port = -1. That tells the mod to reuse the Minecraft server's own port instead of requesting a second one, at the cost of losing the ability to run other mods that also need their own UDP port, such as Geyser, on the same server.
If your host is not Aternos, check whether it documents its own Simple Voice Chat or UDP port setup before changing anything. A guide written for a different host can break your setup instead of fixing it.
Adjust voice_host and bind_address only if you are told to
Two settings in the server config exist for edge cases and default to blank for a reason. bind_address sets which server IP address voice chat binds to; leave it blank unless you were specifically told to set it, since it normally falls back to the server-ip value in server.properties. voice_host overrides the hostname or port clients use to reach the voice server; changing it without a specific reason, such as a reverse proxy setup, usually breaks connections rather than fixing them.
Rule out your own connection last
If you are the only player who cannot connect while everyone else on the same server is fine, the problem is more likely on your end: an ISP or mobile data connection blocking UDP, or a VPN or local firewall. Test on a different network if you can, and confirm the same problem does not happen on another server running Simple Voice Chat.
Frequently asked questions
What does the plug icon mean in Simple Voice Chat?
The plug icon covers two different states: the mod is not installed, or it is installed but cannot connect to the server's voice port. Press V to check. If the voice chat settings screen opens, the mod is installed and the icon means a connection problem, most often a closed UDP port.
What port does Simple Voice Chat need open?
UDP port 24454 by default, set by the port key in voicechat-server.properties. This is separate from the Minecraft server's own TCP port and has to be opened on its own, whether that means a firewall rule, a router forward, or a Docker 24454:24454/udp mapping.
Why is Simple Voice Chat not connecting on Aternos?
Aternos only opens one port per server, which conflicts with voice chat's default separate UDP port. Aternos's own setup guide fixes this by changing port = 24454 to port = -1 in voicechat-server.properties, so voice chat reuses the server's existing port instead of requesting a second one.
Does Simple Voice Chat need to be installed on the server, not just the client?
Yes. Installing only the client mod leaves it with no voice server to connect to, which shows the same plug icon as a blocked port. The server needs either the mod, for a Fabric, Forge, NeoForge, or Quilt server, or the plugin, for Bukkit, Spigot, Paper, Purpur, or Folia, alongside the client mod every player installs.
Why does voice chat keep disconnecting and reconnecting?
This is usually an unstable internet connection rather than a server setting, on either your side or the server's. Check your own connection first, since a wired connection or a different network often resolves it; if only one player is affected, it points at their network rather than the server.
