Minecraft server not showing up? Fixes that work

Check 1: Is the server actually running?

Open the console. The last startup line should say Done. If it shows an error, stopped, or is still loading a modpack, wait or fix that first.

If you just restarted, give it a minute. Large modpacks can take several minutes to start.

Check 2: The address and port

The most common cause by far.

Java: the address is host:port. If the port is 25565, you can leave it out. Any other port must be written after a colon, no spaces: 203.0.113.10:25612.
Bedrock: address and port go in two separate fields. The Bedrock port (default 19132) is not the Java port.
Copy and paste the address instead of typing it. A missing digit looks fine at first glance.
Try Direct Connection in the multiplayer menu. If that works but the saved entry does not, delete and re-add the saved server.

Check 3: What the error says

The message tells you most of the story.

Message	Meaning	Fix
“Outdated client” / “Outdated server”	Game and server version differ	Match the version in your launcher
“You are not white-listed on this server!”	Whitelist is on, player is not on it	`/whitelist add <name>` (exact spelling)
“Connection refused”	Nothing listens on that port	Wrong port, or server not running
“Connection timed out”	Traffic never arrives	Firewall, port forwarding, or wrong IP
“Unknown host” / “Can’t resolve hostname”	The domain does not resolve	DNS record missing or not propagated
“Failed to verify username”	Login check with Mojang failed	Restart the game launcher; check the account
“Mismatched mod list”	Modded server, different mods	Same pack and version as the server

Check 4: It shows in the list, but with no info

The entry shows “Can’t connect to server” or no player count, but the server is running.

enable-status in server.properties is set to false. Set it to true and restart.
The server was started a moment ago; press Refresh.
A proxy or plugin hides the status. Check its config.

Check 5: Home server — ports and firewall

If you host at home and it works for you but not for friends:

Can you join with localhost? If not, the server itself has a problem.
Can someone on your Wi-Fi join with your local IP (like 192.168.1.20)? If not, the Windows firewall blocks Java. Allow Java through it.
Can someone outside join with your public IP? If not, port forwarding is missing, wrong, points to an old local IP, or your provider uses CGNAT.

The full walkthrough is in port forwarding vs hosting.

Check 6: Custom domain and SRV record

If the IP and port work but the domain does not:

The SRV name must be _minecraft._tcp. plus your subdomain, for example _minecraft._tcp.play.
The SRV target must be a hostname with an A record, not an IP.
On Cloudflare, the A record must be DNS only, not proxied.
New records can take a few hours to reach every provider. Test with the IP in the meantime.
Bedrock ignores SRV records. Bedrock players always need the address plus port.

Check 7: Bedrock and Geyser

If Java players join but Bedrock players cannot:

The Geyser port must be open for UDP, not only TCP.
The port in the Bedrock “Add Server” screen must match the Geyser port.
Consoles cannot add custom servers directly and need a workaround.

See crossplay with Geyser and Floodgate.

Check 8: Only one player cannot join

If everyone else gets in:

Their game version differs. Check the version they launch.
They are not whitelisted, or banned (/pardon <name> if that was a mistake).
They play on a network that blocks game ports, for example school or work Wi-Fi. Try mobile data.
Their username changed and the whitelist still has the old one. Re-add them.

Check 9: After a move or reset

If you moved to a new server, the old address or DNS record may still point to the old one.
If you reset the world, ops.json and whitelist.json may be missing. Re-add players.

Still stuck? Read the last 50 lines of logs/latest.log while a player tries to connect. If nothing appears at all, the connection never reached the server — it is a network or address problem. If an error appears, it is a server problem, and the message is your lead. The whitelist and permissions guide covers the access side.