Add-ons

Minecraft’s server port may not be the only part of a server’s network traffic. Bedrock support, voice chat, web maps, and other plugins each use a unique port and protocol. Installing these add-ons by themselves doesn’t configure their network settings.

Even if an add-on/service isn’t listed below, you can usually work out its network requirements by looking for a bind address, port, and protocol in its configuration. In the server’s Settings, use Edit Configuration Files to browse add-on settings in the configuration editor. Identify what the service actually listens on, then apply the same local-to-public testing methodology but for its specific network configuration.

Terminology:
Bind/LAN address	The network interface this service is assigned to, usually the same as the server
Local port	Where the service receives connections on the computer running auto-mcs
Protocol	TCP, UDP, or both
Public address/port	The address people outside your network will connect to this service (can differ from the local port)

Note

Similarly to the server itself, you’ll need to port forward the local port or configure a tunnel using playit.gg for access to these services over the internet

Geyser

Geyser allows Minecraft Bedrock Edition players to join a Java Edition server by translating the Bedrock network protocol. auto-mcs manages this as a compatibility bundle: Geyser translates the connection, Floodgate supports Bedrock accounts, and ViaVersion helps with protocol compatibility where available. You don’t need to install these manually when using the built-in Bedrock Support (Geyser) switch in the server’s Network Settings.

The switch is available for Spigot, Paper, Purpur, Fabric, Quilt, and NeoForge on Minecraft 1.13.2 or newer, and needs an internet connection to download the add-ons. After enabling it, restart the server to apply the change. Learn more about Geyser.

Java Edition normally connects over TCP, while Bedrock connects through Geyser over UDP on port 19132 by default. You can modify the configuration by searching for “Geyser” in the configuration editor. On the filesystem, these are under plugins/Geyser-Spigot/config.yml on Bukkit-based servers, or config/Geyser-Fabric/config.yml on Fabric.

Version compatibility

auto-mcs supports automatically updating Geyser and its dependencies. The Add-on Manager checks for updates to Geyser, Floodgate, and ViaVersion, and you can install available versions using Update or Update All. When you update your server or change your server’s type/version, auto-mcs attempts to install compatible versions of the Geyser bundle.

However, there may not be an official compatible update available for a brand-new Minecraft release. If Bedrock players can’t join after updating Minecraft, check the latest available Geyser version at geysermc.org/download. Bedrock players generally won’t be able to connect if Geyser doesn’t support the new version’s protocol immediately.

For very recent releases or snapshots, newer experimental builds can sometimes be found in the GitHub Actions workflows for both Geyser and Floodgate. Make sure both files are for the correct Minecraft version, and compatible with the server’s type. GitHub may require you to sign in to download workflow artifacts, and development builds aren’t guaranteed to be stable.

You can download the .jar files and import them through the Add-on Manager, then restart the server and check the Console for errors. If they fail to load, see Add-on Troubleshooting.

• Port forwarding: Forward UDP to Geyser’s active Bedrock port on the computer running auto-mcs. A Java TCP rule alone won’t accept Bedrock connections

Bedrock players must enter the address and UDP port of their public Bedrock endpoint. This may not be the same as the Java address.

playit with Geyser

When Bedrock support is enabled, auto-mcs currently only requests a TCP tunnel on the server’s active port. To use Geyser with playit, you’ll need to configure a separate Bedrock UDP tunnel in the playit panel targeting Geyser’s active port. Test the public Bedrock endpoint from another network. For more details, follow playit’s Geyser setup guide. If a Geyser tunnel is configured correctly, the tunnel address will be displayed in the Console.

If Bedrock players can join but their real IP addresses aren’t shown, see Proxy protocol.

Troubleshooting Geyser

If Java players can join but Bedrock players can’t, the Java connection has passed its test. That doesn’t test Geyser’s separate UDP listener.

1. Check the listener. Open the active Geyser config.yml and confirm its bedrock settings. If clone-remote-port: true, use the Java server’s active port instead of 19132.
2. Read the Console. Start the server and look for Geyser or Floodgate startup errors, especially a failed port bind or an add-on that didn’t load. If Geyser didn’t start, investigate that first using Server Troubleshooting.
3. Test Bedrock locally. On a Bedrock client connected to the same LAN, enter the host computer’s LAN IP and Geyser’s active port. Don’t use the playit hostname or public IP for this test.
4. Test the public route. If Bedrock connects on the LAN, try the actual public Bedrock endpoint from a different network. Match its UDP route to the port found in step 1.

If the LAN test fails: check Geyser’s startup messages, installed dependencies, active port, and whether that port may already be occupied

If LAN works but the public test fails: double-check the port forwarding rule, or set up Geyser with playit.gg

For general IP address discovery and public-client testing, see Networking Troubleshooting and Test the public connection.

Simple Voice Chat

Simple Voice Chat sends audio over UDP, separately from the normal Minecraft connection. Its default port is 24454, but the server’s actual configuration takes precedence.

Find voicechat-server.properties in the server directory:

Bukkit-based	plugins/voicechat/voicechat-server.properties
Modded	config/voicechat/voicechat-server.properties

Open this file in the configuration editor and check the port:

port=24454

This is the local UDP listener, not necessarily the port people will use outside your network.

• Port forwarding: Add a UDP rule forwarding that port to the LAN IP of the computer running auto-mcs

playit with voice chat

The server’s default TCP tunnel doesn’t carry Simple Voice Chat’s UDP traffic. Create another tunnel for Simple Voice Chat in the playit panel. Point its local port to the port in voicechat-server.properties (usually 24454).

Copy the tunnel’s public hostname & port into voice_host. For example:

port=24454
voice_host=example.tun.ply.gg:34567

Here, port stays at 24454, where the add-on listens locally. voice_host tells Minecraft clients which public UDP address to use. Leave bind_address blank unless you need to bind a specific interface. Finally, restart the server to apply these changes.

Note

Simple Voice Chat also needs to be installed for each client for players to talk. For additional tunnel and client setup steps, see playit’s Simple Voice Chat guide

Troubleshooting voice chat

If Minecraft works but players can’t hear each other, test the voice chat independently:

1. Check the Console. Restart the server and find Simple Voice Chat’s startup messages. If it failed to initialize or couldn’t bind its port, fix the add-on configuration or be sure that there isn’t another server running with the same add-ons, and networking settings
2. Check the configuration. Open voicechat-server.properties and be sure that port matches the UDP rule or tunnel’s local destination
3. Test it locally. Have two players on your LAN join the server and test the voice chat. If this fails, check its listener, firewall, and advertised voice_host; clients may still be directed to a public address even when they’re local
4. Try the public address. If local voice works, test with a player on a different network. With playit, compare voice_host to the public UDP hostname/port and confirm the tunnel targets the local port from step 2

For finding the LAN address and testing from another network, use Networking Troubleshooting and Public connection tests

BlueMap

Note

You can download BlueMap and other supported map plugins directly from the Add-on Manager, or import a compatible .jar

This guide uses BlueMap as an example; other map plugins will have their own configuration files, but you can use the same methodology to find their web server settings. BlueMap renders an interactive 3D view of your Minecraft world, and serves it through a separate HTTP web server. Install a compatible version and start your server once to generate its configuration files:

Bukkit-based	plugins/BlueMap/
Modded	config/bluemap/

First, open core.conf in the configuration editor and allow the required Mojang resource download:

accept-download: true

Next, open webserver.conf and check the web server:

enabled: true
port: 8100

By default, BlueMap uses TCP 8100 independently of the server port. Its optional ip setting controls where the web server listens. Without it, BlueMap listens on 0.0.0.0 (all interfaces). Setting ip: "127.0.0.1" allows connections only from the computer running auto-mcs or a local reverse proxy, not directly from other devices on your LAN.

Restart the server or run /bluemap reload to apply changes, then check the Console. Open http://localhost:8100/ in a browser on the computer running auto-mcs, with the previously identified port. To make the map reachable through port forwarding, forward its TCP port and share the corresponding public web address.

See the BlueMap configuration reference for its remaining web server options.

playit with BlueMap

The Minecraft game tunnel won’t publish BlueMap’s website. It needs its own tunnel targeting the web server’s TCP port.

If you want to make the map available through HTTPS using playit, see playit’s HTTPS tunnel guide, which uses BlueMap as its example. This setup requires playit Premium and a local HTTPS reverse proxy, such as Caddy

Troubleshooting BlueMap

Start with BlueMap’s own web server before changing any public network settings:

1. Check the Console. Look for BlueMap’s Webserver started message, or an error about loading configuration or binding a port. Check enabled and port in webserver.conf
2. Test on the host. Open http://localhost:8100/ from the computer running auto-mcs. Replace 8100 with your configured port, and use http:// rather than https:// unless you’ve deliberately configured HTTPS
3. Test on LAN. From another device on your network, open http://192.168.1.50:8100/ using the host’s actual LAN IP. If localhost works but this doesn’t, check the host firewall and BlueMap’s optional ip bind address
4. Test the public connection. Once LAN works, try the publicly forwarded address or playit tunnel from another network. Make sure the TCP route goes specifically to BlueMap’s port

If you get 404 - Not Found: the web server may be running but unable to serve the map files. Check accept-download: true in core.conf, and confirm the webroot values in webserver.conf and webapp.conf refer to the correct location.

If the site loads but the map isn’t updating: check rendering progress in the Console, allow time for Minecraft to save the world data, then try Update Map in BlueMap’s web interface.

For other map plugins, identify their equivalent settings and use the same testing methodology with their own configuration and ports. See the BlueMap FAQ or Networking Troubleshooting for more details.

Remote access

Tip

If you’re using auto-mcs, you don’t need a separate remote console at all. Telepath lets you pair another auto-mcs installation and manage its servers directly in the normal Server Manager, including the Console, configuration editing, and much more. It works with desktop or headless hosts without a separate web interface. See Pairing to get started

Other tools can expose separate remote console or administration ports, independent of Minecraft’s game port. Check the tool’s own configuration for its port, protocol, and authentication before connecting or opening any route.

Caution

Don’t expose an administration interface publicly just because a tunnel makes it possible. Prefer a private VPN and access controls. For Telepath itself, use a protected connection for internet access: its default HTTP transport isn’t end-to-end encrypted. See Telepath Security