Updated 30 October 2026
A checklist for the most common reasons a server works for you and not for your friends, from versions and modpacks to whitelists and new addresses.
It is usually one of four things: the server has not finished starting, their Minecraft version does not match the server, they are missing the server's modpack, or they are not on the whitelist.
Go through these in order.
A server can take a minute or more to start, and a big modpack much longer. Until the console says "Done", nobody can join. If it keeps restarting, the console or crash report will say why.
Java Edition players need the same Minecraft version as the server, unless the server has a plugin like ViaVersion that lets newer clients join. The error usually says "Outdated client" or "Outdated server". In the launcher, make a profile for the server's exact version.
If the server runs a modpack, every player needs that same modpack, in the same version, installed through a launcher like CurseForge, Modrinth or Prism. A missing or mismatched mod usually shows up as "Mod rejections" or a list of mismatched mods.
With the whitelist on, only names on the list can join, and everyone else sees "You are not whitelisted on this server". Add them with /whitelist add <name>, spelled exactly as their Minecraft name.
If someone tried your new address before it was set up, their computer can remember "this does not exist" for up to half an hour. Restart the Minecraft launcher, or on Windows run ipconfig /flushdns. If it works on a phone on mobile data, the address is fine and their computer just needs to catch up.
Check /banlist. And a server with online mode on (the normal, safe setting) only lets in players who own Minecraft and sign in with a Microsoft account.
On LunaHost, your server's Overview has a "How players join" card with the exact address, what players need to install, and a message you can copy and send to your friends. The Players tab manages the whitelist, ops and bans without typing commands.
See the plans