To connect, first use the address and port that your server shows in the panel. Default ports explain the protocol, but do not replace a concrete port assignment. If joining fails, check the server start, client and address before you change any network rules.
Telling the Two Game Connections Apart
| Connection | Usual default | Relevant for your server |
|---|---|---|
| Java players | TCP 25565 | Displayed Java address and assigned TCP port |
| Bedrock players | UDP 19132 | Displayed Bedrock address and assigned UDP port |
| Bedrock via Geyser | Separate UDP entry point | Actual Geyser configuration and port assignment |
| RCON | Separate remote administration | Not required for normal play |
The Paper configuration reference and the BDS reference describe the server parameters. An open TCP port is no proof of a working Bedrock UDP entry point.
RCON is not an additional game port. Do not open this administration access as an attempt to fix a failed join. An optional web map also has its own connection and is not necessary for the normal Minecraft login.
Check in This Order
- Open the correct server in the panel. Is its installation complete and has the process actually started?
- Read the start of the console. A server with missing mods or a port binding error does not reliably accept connections.
- Compare the edition and supported client version. For modpacks, the intended client instance must be started.
- Copy the address and port exactly from the panel. Do not accidentally use SFTP, web or administration data.
- Test a new connection and note the exact message, time and time zone.
For an additional Java port, an address looks like play.example.net:25570, for example. This is an example, not an address of your server. Depending on the client, Bedrock offers separate fields for address and port. Consoles differ in whether you can add custom servers.
Using Error Messages as Clues
| Observation | Next sensible check |
|---|---|
| Unknown host | Spelling and DNS resolution |
| Connection refused | Start status, assigned port and listening service |
| Timeout | Reachability of the correct protocol and network path |
| Outdated client or server | Supported versions on both sides |
| Whitelist or ban message | Access rules for the affected account |
| Mod handshake fails | Pack, loader and shared gameplay mods |
Compare a failed attempt via your domain with the same connection via the assigned direct address and the same port. If the direct connection works, check A/AAAA and, where applicable, SRV responses: an old AAAA record can point to a different server even though the A record is correct. If, on the other hand, only one account fails, check its version, whitelist or ban before you change the network access of the entire server.
Custom Domain and SRV
A Java SRV record can point to the correct target host and port. A typical form for the example domain is:
_minecraft._tcp.play.example.net. 3600 IN SRV 0 0 25570 node.example.net.
The target host must be resolvable accordingly. The record does not open a port and does not replace a reachable server assignment. For the setup, use the guide Connecting a Custom Domain and then test with a fresh connection attempt. DNS caches can retain old responses.
Do not transfer this Java method as a universal Bedrock solution. There, use the documented address and the explicit port of the respective client. For Geyser, you need an actually reachable Bedrock entry point; an arbitrary free port in a text file is not enough.
Rented Server or Home Server?
With a rented server, you normally don't have to set up port forwarding on your home router. The server is located at the host. If the address shown in the panel is not reachable despite a successful start, give support the concrete error message and the time.
With a self-hosted home server, public reachability, router assignment and firewall come into play. Only open the required connection to the correct internal machine. A private LAN address is not a public destination outside your network. With provider NAT, router forwarding alone may be insufficient.
Do not blanket-disable firewall, antivirus or account verification. Also do not change online-mode to work around a network issue. Doing so changes the login and possibly the assignment of player data.
What Helps Support With Diagnosis
Note the server, edition, client and server version, exact message, time, the address type used and whether other players are affected. Add the relevant start and connection lines from the console. Do not share passwords, session codes or access keys.
For a real startup error, the Paper error diagnosis helps. For a modpack problem, the guide on joining a modpack server is a better fit than further port changes.
FAQ
Does my Java server absolutely have to use port 25565?
No. What matters is the assigned connection. With a different port, you either specify it directly or set up the matching domain resolution.
Does an online port checker prove that Bedrock works?
Only if it meaningfully tests the actual Bedrock connection. An ordinary TCP test says little about UDP. Test with a suitable Bedrock client.
Do I need RCON to play?
No. RCON is an administration feature and is not part of fixing a normal connection error.
Related Guides
- Bedrock Server: Choosing BDS or PocketMine-MP
- Minecraft Loads a New World: Finding Your Old Map Again
This Guide in Other Languages
English · Español · Français · Nederlands · Português · Русский