A plugin port must belong to this server and must not already be occupied by another listener using the same protocol. Changing a number in a plugin configuration does not allocate that port in the hosting.
Step by step
- Open Overview and copy the current IP, main port, Query / plugin port and any additional ports. Check them again after restoring a server or changing its allocation.
- Compare each plugin configuration with this list. With shared IPs, only your assigned ports are available. Common defaults such as 19132 or 24454 are not a reservation.
- Give Geyser and Voice Chat different ports. Inspect enable-query and query.port in /server/server.properties: disable Query if unused, or assign it a separate available port. The Properties tool, Fix Tool or restoration can reapply Query defaults, so recheck afterwards. Do not change the main server-port to fix a plugin.
- Check the listener address inside the container. Geyser normally listens on 0.0.0.0; Simple Voice Chat can use bind_address=*. The public IP is for players to connect to, not for binding inside the container.
- Save, restart and read the startup messages. Address already in use suggests a conflicting listener; Cannot assign requested address suggests an unsuitable bind address. Check missing dependencies or unsupported plugin versions too.
- Use an actual Bedrock client or the Voice Chat connection test. For NetherNet, check TCP and UDP on the Geyser port and any separate webrtc-port. A successful Java connection does not prove these services work.
- If it still fails, contact support with your server ID, current IP and affected port, plugin version, test time and relevant log excerpt. Do not send passwords, access tokens or Floodgate key.pem.
Check the result
Normal panel allocations cover TCP and UDP; you do not need a separate UDP purchase for an allocated port. Geyser, Voice Chat and Query still need non-conflicting listeners. Additional port availability depends on your plan.
Important
Do not disable all authentication or try random ports as a workaround. A generic TCP-only port test cannot establish UDP reachability; the intended service must be running and answering.