Can't Join a Server After Updating to Minecraft 26.3?

If your launcher has put you on Minecraft 26.3 since September 15 and your usual server now refuses to let you in, the server is almost certainly still on 26.2, and Java Edition only lets a client and a server connect when they run the same version. Nothing on your end is broken. The fastest fix is to make a 26.2 installation in the launcher and join with that until the server updates. If you'd rather stay on the new version, the 26.3 server list shows servers that are already running it.

Why 26.2 and 26.3 won't connect

Each Java release talks to servers over a numbered network protocol, and the server checks for an exact match the moment you connect. 26.2 is protocol 776 and 26.3 is protocol 777. Being one number apart doesn't help, so a 26.3 game can't join a vanilla 26.2 server and a 26.2 game can't join a 26.3 one. What protocol version 26.3 uses has the full breakdown if you want it.

It happened without you touching anything because the launcher's default installation, Latest release, moves to each new version as soon as Mojang ships it. Mojang's own release notes tell players to keep the launcher on that option. Servers update when their owner decides to, which for most public servers takes a lot longer.

What you'll see when it fails

The exact message depends on the server's software and on which side is newer. Most public servers run Paper or Spigot, and those use their own wording:

You're on 26.3 and the server is on 26.2. This is where most people are this week, and the message is "Outdated server! I'm still on 26.2".
You're on 26.2 and the server is on 26.3. The message is "Outdated client! Please use 26.3". You'll run into this if you never updated, or later on, when your 26.2 installation meets a server that has already moved.

On a vanilla server (and on Fabric), the message is the same whichever side is newer: "Incompatible client! Please use 26.2" if you're on 26.3 and the server is on 26.2, or "Incompatible client! Please use 26.3" the other way round. The vanilla wording confuses people, because "incompatible client" sounds like your game is out of date even when it's the newer of the two. Paper and Spigot owners can also rewrite their messages in spigot.yml, so some servers will say something else entirely. Whatever the wording, go by the version at the end of the message, since that's the one the server wants you on. The guide to "Outdated server!" and "Outdated client!" goes deeper on these messages.

The Multiplayer screen usually tips you off before you even click Join Server. A server on a different version gets an incompatible icon and the status "Incompatible version!", along with the version name the server reports. A flagged server is still answering the list's ping, which tells you the problem is a version gap and not a server that's down.

Fix 1: Join with a 26.2 installation

All it takes is the official Minecraft Launcher.

Open the launcher, choose Minecraft: Java Edition, and go to the Installations tab.
Click New installation.
Name it something you'll recognize, like "26.2 servers", and pick 26.2 from the Version dropdown.
Click Create, then launch that installation and connect as usual.

Your Latest release installation stays on 26.3, so you end up with both. On the launcher's main screen, the dropdown next to the Play button switches between them, so you pick the 26.2 one for servers that haven't updated and Latest release for everything else. Installations share the same game folder by default, so your saved server list and settings come along.

That shared folder is also the one thing to be careful about. The 26.2 installation will list single-player worlds you've already opened in 26.3, and you shouldn't open those in 26.2. A world gets upgraded when a newer version loads it, and loading it in an older version afterwards can damage it. This only matters in single-player, and if you really need one of those worlds in 26.2, back it up first.

Fix 2: Wait for the server, or play one that has updated

A vanilla server can update the day a release comes out, but most public servers run Paper or another plugin platform, and those usually wait until the software and their plugins support the new version. As of September 18, 2026, every Paper 26.3 build is still an alpha, and Paper's downloads page leads with 26.2 and keeps 26.3 behind a toggle for experimental builds. That alone is a good reason for a server to stay on 26.2 for a while, and plenty will. There's no date to count down to, so watch your server's announcements, or check that downloads page yourself.

If you updated to see the dappled forest and the rest of what's new in 26.3, the easier route is to pick a server from the 26.3 list, which shows servers reporting 26.3 right now. Your old favorites still on 26.2 are on the 26.2 list, and that's where the installation from Fix 1 comes in.

If you run the server

Owners have a way to let both versions in. ViaVersion on a 26.2 server lets 26.3 players join it, and ViaBackwards, an add-on that needs ViaVersion installed, goes the other way and lets 26.2 players onto a 26.3 server. As of September 18, 2026, ViaVersion's 26.3 support is finished and announced but not yet out as a public release, so check ViaVersion's Modrinth or Hangar page for a version that lists 26.3 before you count on it.

Players can't add any of this to someone else's server, but if yours has it set up, you can stay on 26.3 and join anyway.

Crossplay servers and Bedrock players

Bedrock got Wilderness Bound on the same day, but on its own version line. The Bedrock release is 26.50, with a 26.51 hotfix after it, and Bedrock doesn't use Java's protocol numbers, so "26.3" doesn't apply to Bedrock at all. Crossplay servers let Bedrock players in through Geyser, which already supports Bedrock 26.50 and 26.51, so Bedrock players can connect as long as the server has updated its Geyser.

The catch is on the Java side. As of September 18, 2026, Geyser supports Java 26.2 but not 26.3, which so far only exists in preview builds that Geyser's team labels experimental and not for production. Crossplay servers are likely to hold on 26.2 until that changes, so Java players joining them will need the 26.2 installation unless the server also runs ViaVersion. Geyser's supported-versions page on geysermc.org is the place to check.

Modded servers

Fabric was ready on release day. Its announcement tells players to use the latest stable Fabric Loader, which is 0.19.5, and Fabric API had 26.3 builds out at launch. Your mods are a separate question, because each one needs its own 26.3 build, and a modpack usually waits until every mod in it has one. If a modded server is still on 26.2, join with a 26.2 Fabric profile and the 26.2 versions of its mods. If it has updated, you need the 26.3 version of every mod it uses. Installing Fabric to join a modded server covers setting up a profile for a specific game version. On NeoForge, only beta builds exist for 26.3 as of September 18, 2026.

Joining a friend's brand-new 26.3 server

26.3 changed one default that trips up people starting a server for friends. In a freshly created server.properties, white-list is now true, so a new 26.3 server turns away everyone who hasn't been added to it. If you get "You are not white-listed on this server!" (or "You are not whitelisted on this server!" on Paper), your version is fine, since the version check happens before the whitelist one, and the fix is on your friend's side. They can type whitelist add YourName in the server console, or /whitelist add YourName in-game if they're an operator. If they'd rather not run a whitelist at all, /whitelist off turns it off, or they can set white-list=false in server.properties and restart. The not-whitelisted fix has more on getting added.

FAQ

Will a 26.3.1 patch fix this?

There's nothing for a patch to fix, because two different versions refusing each other is the game working as designed. For the record, no 26.3.x hotfix exists as of September 18, 2026, and the launcher's latest release is plain 26.3.

Do I need a different Java version for 26.3?

No. 26.3 requires Java 25, the same as 26.2 and 26.1, and the Minecraft Launcher downloads the runtime it needs by itself. Only people hosting their own server need to think about Java, and anyone who ran 26.2 already has the right one.

Why doesn't my server just go back to 26.2 so everyone can join?

Because a world that has been opened on 26.3 has been upgraded, and it can't be taken back down. Spigot's team says it plainly: downgrading a server to an earlier version isn't possible. An owner who updates and regrets it has to restore a backup and lose everything that happened since, which is exactly why careful owners wait instead of updating on day one.

My friend upgraded their existing server to 26.3 and now I'm not white-listed. Is that the new default?

Probably not. The new default should only apply when server.properties is created from scratch, or when the file has no white-list line. An existing file already has a white-list line written in it, so an upgraded server should keep whatever setting it had. If you're being turned away after an upgrade, the whitelist was most likely already on and you weren't on it, or the file was regenerated during the update. The fix is the same whitelist add either way.