Minecraft Server Ports Explained – 25565, 19132, SRV Records

Minecraft ports determine whether players can reach your server: Java uses TCP 25565 by default, Bedrock uses UDP 19132, and RCON often uses TCP 25575. If you use your own domain, an SRV record can hide the port. The important part is always the combination of the correct edition, correct protocol, reachable address, and properly configured firewall.

Minecraft Ports – Complete Overview

Default Ports

Minecraft Java Edition uses port 25565 over TCP by default for normal player connections. Bedrock Edition uses port 19132 over UDP by default. This distinction matters because an open TCP port 19132 does not help Bedrock players, and an open UDP port 25565 does not allow a normal Java login.

RCON is a separate administration access point. It should only be enabled if you really need it, with a strong password and preferably restricted access. Dynmap or similar web maps also run separately from the actual Minecraft port and only need to be exposed if the map should be publicly reachable.

As an official primary source for the default server configuration, the Minecraft Wiki documentation for server.properties lists server-port for Java servers, among other settings: documentation at minecraft.wiki. For modified servers, also check the documentation of the software you use, because plugins or proxy setups may use their own ports.

When Do You Need Which Port?

Java Edition

For a classic Java server, one TCP port is usually enough. If your server runs on the default port 25565, players can usually enter only the domain or IP address. If the server runs on a different port, the port normally has to be specified as well, for example server.de:25566.

If you run versions, test servers, or multiple instances in parallel, each instance gets its own port. For version changes and server software, not only the port matters, but also the server JAR. The internal guide Change Minecraft Server Version – Vanilla, Paper, Purpur, Forge & Fabric Without Reinstalling fits this topic.

Bedrock Edition and Geyser

Bedrock players connect via UDP 19132 unless another port is set. Geyser is used when Bedrock clients should access a Java server. In that case, you still need the Java port for Java players and an additional UDP port for Bedrock players.

The basic rule is: Java players connect via TCP, Bedrock players via UDP. If cross-play does not work, first check whether the Bedrock port is actually reachable as UDP and whether Geyser matches the installed server version. For deciding between Bedrock software and alternative setups, PocketMine or BDS? Minecraft Bedrock Server Software Compared helps.

What Is an SRV Record?

An SRV record allows players to connect without specifying a port. Instead of server.de:25566, server.de is enough.

_minecraft._tcp.server.de. 86400 IN SRV 0 5 25566 node1.server.de.

The record tells the Minecraft client: For the Minecraft service over TCP on server.de, internally use port 25566 on node1.server.de. The target host should be resolvable as an A or AAAA record. Do not enter an IP address directly as the target in the SRV record; use a hostname instead.

For Java servers, the service name is usually _minecraft._tcp. In Bedrock setups, SRV support is not used the same way in every client and platform context. So with Bedrock, do not blindly rely on an SRV record replacing the manual port entry everywhere.

Port Forwarding and Hosting Panel

If you host a server at home, you need to forward ports in your router:

1. Open the router admin interface (usually 192.168.1.1)
2. Add port forwarding / NAT
3. Forward port 25565 TCP to your PC's local IP
4. For Bedrock: forward port 19132 UDP

With a rented game server, router forwarding is usually not needed because the server runs in a data center environment. What matters then is which address and ports your provider shows in the panel and which additional openings are intended for optional services. At game-serverhosting, the focus is running a paid multi-game server: technical control, understandable settings, support, and transparent processes matter more than router tinkering on a home connection.

If you want to know what technically happens after an order, the internal overview Server Provisioning Explained: What Happens After Your Order? fits.

Firewall Configuration

On Linux servers with ufw:

sudo ufw allow 25565/tcp   # Java
sudo ufw allow 19132/udp   # Bedrock
sudo ufw allow 25575/tcp   # RCON (only if needed)

Only open ports you actually use. RCON should not generally be publicly reachable. If you need RCON, restrict access to known IP addresses if possible or use a protected administration environment. After every change, you should reload or restart the server if the affected software only reads its port configuration at startup.

Check the Result

Start the Minecraft server fully and wait until the log shows that the world has loaded and the server accepts connections. Then test with an external client, not only from the same machine or the same local network. If you use a domain, also check whether DNS has already updated. Depending on the TTL, a change may become visible with a delay.

For Java, test the address once with and once without the port if an SRV record is set. For Bedrock, make sure the client uses the correct server address and the correct UDP port. If you also switch or upload worlds, make sure the server starts fully again afterward; Upload & Switch a Minecraft World – Your Own Map on the Server is helpful for that.

Troubleshooting

"Can't connect"

Usually the address is wrong, the port is not reachable, or DNS still points to an old target. Check IP, domain, port, protocol, and whether the server process is really running.

"Connection refused"

This error often means that no application is listening on the specified port at the target. The server may be stopped, crashed, or configured for another port.

Bedrock Does Not Work

Check whether UDP is open. A port opened only for TCP is not enough. With Geyser, also check the Geyser configuration and whether the Bedrock port matches the published port.

SRV Record Does Not Apply

Check the service name, protocol, target host, port, and DNS resolution. The target host of the SRV record must itself be resolvable. Also wait for the TTL before judging a change as failed.

Verification, Limits, and Safe Rollback

The guide “Minecraft Server Ports Explained – 25565, 19132, SRV Records” applies to the server type described in the article and the version state visible at the time of review. Menu names, available versions, mod or plugin compatibility, and required resources may differ after updates. Therefore, do not transfer values to another game, loader, or server version without checking them.

Before making changes to a world, savegame, configuration, or extensions, create a backup of the affected files. Then change only one related step and test it with the same client and server version you want to play with later.

A successful single test is not a guarantee of performance or availability. World size, mods, plugins, player count, network path, and simultaneous load can change the result. Document the version, change, and test result so you can understand later deviations.

FAQ

Which Port Does a Minecraft Java Server Need?

By default, a Minecraft Java server uses TCP 25565. If your server runs on another port, players must specify that port or you set up a matching SRV record.

Which Port Does Minecraft Bedrock Need?

Minecraft Bedrock uses UDP 19132 by default. Make sure you really open UDP, not only TCP.

Can I Run Multiple Minecraft Servers on One IP?

Yes, but not all on the same port. Each instance needs its own port or an upstream proxy or DNS solution that cleanly points to the respective instance.

Do I Need Port 25575 for RCON?

Only if RCON is enabled and should be reachable externally. RCON is not needed for normal player connections. For security reasons, you should only open RCON deliberately and with protection.

Why Does the Domain Not Connect Without a Port?

Either the Java server is not running on 25565, or the SRV record is missing or configured incorrectly. Check the _minecraft._tcp record, the target host, and the configured port.