Minecraft: Can't connect to server

Fix a Minecraft Java connection by matching the exact release and modpack, using the full host:port, checking the whitelist, and configuring Geyser correctly.

Last updated 14 September 2026

If Minecraft cannot connect, work through these checks in order. Leave the world untouched during diagnosis. The most common failure is a client on the wrong version or a launcher that is not running the same pack as the server.

Stop as soon as one fix works. If you are helping somebody else, test with one player before asking the whole group to retry.

1. Match the client, loader, and pack

Minecraft refuses the handshake when the protocol versions differ. That includes a vanilla mismatch and a modpack mismatch.

Vanilla and Paper: the client's release must match the server exactly.
Forge, Fabric, NeoForge: the loader and Minecraft version must match.
Modpacks: every player must launch the same pack and pack version the server is running.

Read the version the server is actually running

On berrybyte, open Settings → Game Settings → Server software. For a pack, also check Overview → Modpack.

Launch that exact client

Use the official launcher for vanilla or Paper. Use CurseForge, Modrinth, FTB, or Prism for a pack, and install the same pack the server has. Do not join a Forge world from a vanilla profile.

Update both sides after a patch

Close the game, install the store or launcher update, then restart the dedicated server so it pulls the matching build.

At this page's update, Java 26.2 is the current release. Java 26.3 Release Candidate 3 is a testing build. Stable, snapshot, pre-release, and release candidate profiles must match the server's exact version.

See Install a Minecraft modpack. To pick the pack at checkout, rent a Minecraft server that installs it for you.

2. Paste the full host:port

Java uses one address field. The default port is 25565. A hosted allocation often uses a different port. Leaving the port off sends the client to 25565 on the right IP and the wrong process.

Copy Server address

On berrybyte, open Overview and copy Server address. The value looks like 203.0.113.10:25565 (your port may differ).

Use Direct Connection or Add Server

Launch Java Edition, open Multiplayer, then Direct Connection or Add Server. Paste the full address into the single field, including the port after the colon.

Use a Java address for Java Edition

berrybyte hosts Java Edition. Bedrock, Xbox, PlayStation, Switch, and mobile connect through Geyser when it is installed on that Java server.

The full join flow is How to join a Minecraft server. A hosted panel keeps the live address on Overview. Rent a server if you would rather not hunt ports on a home router.

3. Confirm the server finished starting

A Minecraft process can show as running while it is still generating the world, applying a pack, or waiting on the EULA.

Check Overview

The server must be running, not stopped or still installing.

Read Console

Wait for the Done line (or your loader's ready equivalent) before anyone clicks Join. A first boot of a heavy pack can take several minutes.

Accept the EULA if the process exited

A fresh vanilla or Paper server stops until eula=true is set. On berrybyte the panel handles this; a self-hosted box must edit eula.txt.

4. Check whitelist and online-mode

Two server.properties flags refuse players who otherwise have the right address.

white-list=true turns the whitelist into a strict allowlist.
online-mode=true (the default) requires a legitimate Microsoft account. An offline or cracked client is rejected.

Stop the server before editing

server.properties is read at boot. Edits made while it is running are discarded.

Open or disable the whitelist

Add the exact Java username, or set white-list=false for a public test. On berrybyte you can also manage this from Game Settings.

Keep online-mode on unless you know why

A timeout comes from the network path. online-mode controls account authentication.

Mojang changed white-list to true by default for newly generated 26.3 server configurations. The official 26.3 Snapshot 2 notes record the change. Existing server.properties files keep their saved value, so check the file or berrybyte Game Settings.

5. Align mods, proxies, and Geyser

A required client mod that the player does not have looks like a failed join. A proxy that points at the wrong backend does too.

Match every required client mod

If the server is a pack, reinstall that pack on the launcher. If it is a custom Forge or Fabric set, copy the same mods folder version for version.

Check a Velocity or Bungee frontend

The address players use must be the proxy address. The backend port is not the public join port.

Install Geyser for Bedrock players

Bedrock cannot speak Java by itself. Add Geyser from Overview → Plugins → Manage plugins. Its Bedrock listener typically uses UDP 19132, which must be reachable. Share that Bedrock address with console and mobile players.

Add Floodgate when players lack Java accounts

Geyser can authenticate Bedrock players through paid Java accounts. Install Floodgate when they only have Bedrock accounts.

See the official Geyser setup guide for the UDP listener and the Floodgate overview for Bedrock-only account access.

6. Treat a timeout as a path problem

If the handshake never starts, you will see Connection timed out. That is a reachability problem, not a pack problem.

Confirm the process is still up

Check Overview and mcsrvstat.us against the same address.

Try a different route

Switch to Cloudflare WARP or another VPN if only some players fail.

Follow the timeout checklist

See How to fix Minecraft's Connection timed out error for keepalive, proxies, and MTR.

If none of the six fixes worked

Confirm Console reached a ready state. Then check the leftover causes:

Custom domains need the A and SRV records from Network → Custom Domain. The raw IP still works while DNS updates.
Check berrybytestatus.com.
A player on a school or work network may have 25565 blocked.
enforce-secure-profile=true requires Mojang-signed player profile keys. A client or proxy that cannot supply them may be refused after reaching the server.

Join with Java Edition

Paste Server address into Direct Connection or Add Server.

Fix Connection timed out

Status, WARP, proxies, and MTR when the handshake never starts.

Install the same modpack

Match the pack and pack version on every launcher.

Set up Minecraft hosting

One-click packs, the live address on Overview, and support.

Frequently asked questions

Why can't I connect to a Minecraft server?

Check the game version and pack first. A Java client on the wrong release, or a launcher missing the same modpack, is refused immediately. If those match, paste the full host:port, wait until the server is ready, check whitelist and online-mode, then treat a timeout as a network path problem.

Why does Minecraft say Incompatible version or Failed to login?

The client and server may use different Minecraft releases. The same error can come from a mismatched loader or modpack. Select the exact version shown by the server and launch the same pack build.

Why does Minecraft say Connection timed out?

The client sent a request and never got a reply. Confirm the server is running and the address includes the allocated port, then test a different network path. See the dedicated Connection timed out guide for WARP and MTR.

Why am I not whitelisted?

When white-list=true in server.properties, only listed players can join. Add the exact Java username or set white-list=false. Fresh Java 26.3 servers enable the whitelist by default.

Can Bedrock join a Java Minecraft server?

Install Geyser on the Java server and give Bedrock players its UDP address, usually port 19132. Add Floodgate when those players need to join with Bedrock accounts that do not own Java Edition.