These messages mean your Minecraft version and the server's don't match. "Outdated server" = your client is newer; "Outdated client" = your client is older. Here's how to fix it, including the Forge/Fabric-specific case.
Quick answer
Both messages mean your Minecraft version does not match the server's. "Outdated server" means your client is newer, so choose the server's version in the launcher's Installations tab. "Outdated client" means your client is older, so update it. On modded servers the Forge or Fabric version and the mod list have to match as well.
Which message did you get?
The two messages point in opposite directions — read yours and go straight to the fix:
| Message | What it means | Quickest fix |
|---|---|---|
| "Outdated server!" | Your client is NEWER than the server | Set your launcher to the server's version (or the admin updates the server) |
| "Outdated client!" | Your client is OLDER than the server | Update your launcher to the server's version |
Match the version
The simplest fix: set your Minecraft launcher to the exact version the server runs. The error message tells you the server's version — create a launcher profile for it and join.
Server admin: let multiple versions in
If you don't want to force one version on everyone, run ViaVersion (and ViaBackwards/ViaRewind) on a Paper/Spigot server. It lets newer — and older — clients connect to your server version, so a launcher update never locks players out.
"Outdated server" means YOUR client is ahead of the server — downgrade your launcher or the admin should update the server. "Outdated client" means you're behind — update your launcher.
Match your launcher to the server version, or run ViaVersion on the server so any client version can join.
Forge and Fabric modpacks are stricter
On a modded server, "outdated" errors are often really a Forge/Fabric loader version mismatch rather than the base Minecraft version — ViaVersion doesn't bridge mod loader versions. Every player needs the exact modpack version the server runs, including matching mod jar versions, not just the base game version.
How to prevent this
- Announce the exact version before rolling out a server update, so players can prepare their launcher profile.
- Consider running ViaVersion by default on vanilla/Paper servers so a client-side auto-update never locks anyone out unexpectedly.
- On modpacks, distribute the modpack via a launcher (CurseForge, Modrinth) that keeps client and server versions in sync automatically.
Related errors
If the connection fails outright rather than showing a version message, see fixing "Connection refused: no further information". For setting up a new server, see how to make a Minecraft server.
Minecraft is a trademark of Mojang Synergies AB / Microsoft. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Mojang or Microsoft.