First, the why: how come a version mismatch blocks the connection

Minecraft’s client and server talk to each other using a version-specific protocol. When the server runs one major version (say 1.20.x) and your client is on a different major version (say 1.21.x), the protocols don’t line up, the handshake stage gets rejected, and you see a message like “Incompatible version / Outdated client / Outdated server.”

There’s only one way to fix this: get both sides aligned. In the vast majority of cases you can’t change the server, so switch your client to the server’s version. That means the first step is finding out exactly which version the server is — and that’s precisely the kind of information you can look up without paying and without any write access.

Use free monitoring to find the server version, then switch your client

No need to guess, and no need to ask the server owner. Use TopoBlocks’s free “monitor only” mode: just enter the server’s address + port (Java defaults to 25565, Bedrock to 19132) and you’ll see its online status, version number, player count, and latency. Monitoring is read-only with no write access — it doesn’t touch your world or change the server’s configuration.

Once you have the version number:

  • Java Edition: in the official launcher, create or switch to an installation profile for the matching version, then connect.
  • Bedrock: Bedrock usually auto-updates to the latest version; if the server is still on an older version, you’ll most likely have to wait for the server to upgrade, or check whether there’s a matching beta channel.

If you’re not sure how to enter the address and port correctly, or it still won’t connect after you do, see Connecting to a Minecraft server.

Note: Java and Bedrock don’t mix

There’s a kind of “wrong version” that’s actually the wrong branch: Java Edition and Bedrock are two protocols that don’t mix, and no amount of adjusting the version number will let you into the other one’s server. A Bedrock client can’t connect to a Java Edition server, and vice versa — this has nothing to do with numbers like 1.20 or 1.21. Confirm which branch the target server belongs to first; if you can’t tell, see Is the server Java Edition or Bedrock.

If monitoring shows the server is clearly online and the version is aligned but you still can’t get in, the problem may be with online status, the port, or the network — work through Troubleshooting a server that won’t connect / is offline item by item.

If you’re the server owner and want to change the server’s version

Let’s be clear about the boundary first: TopoBlocks won’t change the server-side engine version your existing server runs — upgrading the server software itself is something you (or your host) have to do. What it can help with on the server side is the explicitly authorized, paid “full management”: it safely deploys your world to the server, running through snapshot → validate → atomic switchover → health check → automatic rollback on failure, pre-checks version compatibility before deploying, and never overwrites your source files — each time it preserves the pre-update version and hash, the rollback point is traceable, and if anything goes wrong it can roll back. For the details, see How to safely update the world on your server.

Also, if you’re creating a new server with TopoBlocks’s one-tap managed hosting, you can pick the version, plan, and region directly at setup — provisioning is automatic and you never touch a terminal. Prices are shown in the app, and paid tasks are refunded automatically on failure; monitoring alone is always free and makes no changes.