How to Update a The Isle Server and Fix Version Mismatch

What “version mismatch” really means on The Isle

On The Isle, “version mismatch” is usually shorthand for one of two conditions: the client and the dedicated server are on different branches, or they are on the same branch but different patch builds. In practice, branch mismatch is the bigger offender because the Steam default branch is still public, which is Legacy, while most active communities actually run evrima.

The timing part catches owners every patch day. Steam updates players’ clients automatically, but a rented or self-hosted server stays on the old files until its panel updates it or you run SteamCMD yourself. That old server often remains visible in the browser, so players click it, wait about twenty seconds, then get Client Disconnected or a timeout. If the player is on the wrong client branch entirely, they may see a different server list, an empty list, or a server they can never join.

The timeline below shows how often the live Evrima branch has moved recently. Every one of these patches meant a window where updated players could not join a server that had not been updated yet. HordeTest is a separate test branch on top of this, so a test-branch player can look “more updated” than everyone else and still be unable to join your live community server.

The branches that matter, and why Legacy keeps causing trouble

The Isle has separate branch lists for the client and the dedicated server, and they are not identical. The important rule is simple: if your community runs live Evrima, both sides must be on evrima. Do not assume Steam’s default is the live game.

Two points matter more than the list itself. First, public is the Steam default for both apps, so a fresh client install and a bare app_update 412680 both produce Legacy unless you explicitly choose Evrima. Second, there is no public hordetesting server branch listed for the dedicated server app. HordeTest runs on the developers’ own official servers, so a player on hordetesting cannot join your normal Evrima community server, and you should not try to build your community routine around a test branch.

The matrix below is the quickest way to think about it: matching live branches join, mixed branches do not.

How to update a rented The Isle server

Most managed panels handle The Isle in one of three ways: update on restart, a separate Update button, or a scheduled restart/update task. The useful habit is the same for all of them: stop the server cleanly, trigger the update, watch the console until the patching stage finishes, then let the server boot once and sit. On patch day, the worst mistake is repeated restarts because each restart can interrupt the update or reset the registration window.

What you are watching for in the console is not a specific line so much as a sequence. First the panel fetches new files, then it validates or swaps them, then the dedicated server process starts, loads config, and settles into its normal running state. If the panel has a patch-waiting notice, respect it; if it says updates apply on restart, do a full stop and start rather than a hasty reboot.

After the process is up, wait for the Epic Online Services registration window. A freshly started Evrima server can take 2-5 minutes before it appears properly in the in-game browser. During that period, do not assume the patch failed and do not hammer the restart control. The browser depends on EOS registration, not a separate query socket.

If your host supports scheduled updates or restarts, use them on patch days. That reduces the gap between players receiving the client patch and your server receiving the server patch, which is the gap that produces most Client Disconnected reports.

How to update a self-hosted server with SteamCMD

Self-hosted means you control the timing, but it also means you must protect your own data. Stop the server cleanly before touching files. Back up TheIsle/Saved in full, because Databases holds player progress and Config holds your Game.ini and Engine.ini. Do not edit those files while the server is running; the server rewrites Game.ini on shutdown, so live edits can be overwritten or leave you chasing a stale file.

The dedicated server is the separate free Steam app 412680, installed through SteamCMD with login anonymous. To update the live Evrima branch, use the command below and keep the -beta evrima part in place every time.

steamcmd +force_install_dir "C:\TheIsleServer" +login anonymous +app_update 412680 -beta evrima validate +quit

On Linux, use the same command with your Linux install path instead. The important parts are the app ID, the branch name, and validate. Validation costs disk activity and a bit of time because SteamCMD checks shipped files, but it is worth it after a patch: it can restore missing stock files, including files a bad manual edit or half-failed reinstall has broken.

Why the -beta evrima switch matters: without it, app_update 412680 follows the default branch, and the default branch is public, which is Legacy. That is why owners sometimes reinstall “cleanly” and still come back on the wrong game.

Typical config locations are TheIsle/Saved/Config/WindowsServer/Game.ini on Windows and TheIsle/Saved/Config/LinuxServer/Game.ini on Linux. The install’s steamapps folder also contains the app manifest used to confirm the actual branch and build. If you self-host, keep firewall rules aligned with what Evrima actually uses: the game port is UDP 7777 in the 7777-7779 range, the queue uses TCP 10000, and RCON uses TCP 8888 in the standard setup. Evrima honours -Port and ignores -QueryPort, so changing query port values will not fix browser registration.

Check the active branch and build before blaming anything else

Do not rely on a panel label or on what you think you selected last month. Check what is actually installed. In a SteamCMD install, the file steamapps/appmanifest_412680.acf inside the install folder records both the installed build and the beta branch key. A trimmed example looks like this:

"AppState"
{
    "appid" "412680"
    "buildid" "24664709"
    "UserConfig"
    {
        "MountedConfig"
        {
            "BetaKey" "evrima"
        }
    }
}

If that BetaKey says evrima, you are on the live Evrima server branch. If it is missing, blank, or effectively on public, you are on Legacy. You can also ask SteamCMD directly:

app_status 412680

Then compare the result to the latest live Evrima patch date, not to the client’s raw build number. Build IDs are per app, so a matching patch can still show different IDs between the client and the server. For example, the client’s Evrima build 24664737 and the server’s Evrima build 24664709 both belong to the 11 August 2026 patch. That difference is normal. What matters is that both sides are on the same branch and patch generation.

What to ask players to check on their side

Once your server is updated, most remaining join failures are on the player side. Give players a short checklist rather than a vague “verify files”. The key instruction is to put the client on evrima: in Steam, right-click The Isle, open Properties, then Betas, and select evrima. Legacy shows a different, mostly dead list, so a player on the default branch can think your server vanished when they are simply looking at the wrong version.

• If they joined a test recently, make sure they leave hordetesting and return to evrima. A HordeTest client cannot join a normal Evrima community server.
• After a patch, let Steam finish updating, then fully restart Steam. That helps Easy Anti-Cheat reinitialise cleanly.
• If the update does not appear straight away, tell them to restart Steam again before doing anything more drastic.
• Run Verify integrity of game files after the restart. That costs local disk checks on the client, but it fixes partial patching and missing stock files.
• If the list looks half-empty, clear session filters and raise Steam’s Max pings per minute setting so the browser does not cut discovery short.
• Make sure the system clock is set automatically and that The Isle and EAC are allowed through the local firewall. A bad clock can break backend handshakes.
• As a fallback, use Steam Favourites or direct connect with the server IP and port, with 7777 as the default game port.

This is worth doing before you reopen publicly. If even one staff member is accidentally sitting on HordeTest or Legacy, they can report a “server problem” that is really only a client branch problem.

Server updated but still not showing: what to check next

If the files are current and the server process is running, the next suspect is registration rather than patching. A freshly started Evrima server takes 2-5 minutes to register with Epic Online Services and appear in the browser. During that time, leave it alone. Restarting a healthy process because it is not visible after a short wait simply starts the registration clock again.

After that window, check Engine.ini. It must contain the [EpicOnlineServices] block with the shipped DedicatedServerClientId and DedicatedServerClientSecret. Without that block, the server cannot register with EOS and will never show in the browser. Because those values ship with the server files, a validate pass or clean reinstall can restore them if they were removed.

Also check your settings files. Patches can reset Game.ini, which is why you keep your own copy outside the live folder. Restore your known-good copy only after the server is stopped, then start once and watch for a stable boot. If you need a clean reference for file locations and option names, see The Isle server settings explained.

A server sitting at about 1.3 GB RAM with no real CPU activity and no browser presence is often boot-looping on a missing or invalid Game.ini. That pattern points to config load failure, not player traffic. Finally, remember that browser presence does not rely on a separate query socket: Evrima ignores -QueryPort. If every server disappears for everyone at once, that points to an EOS outage rather than anything unique to your machine.

A patch-day routine that protects saves and cuts down join errors

Good patch days are mostly about order. When the developers announce that official servers are being taken down while they update the Evrima public branch, treat that as your signal that the live patch is in motion. Keep a short maintenance window, update deliberately, and do not reopen until one updated client has joined successfully. If a big content patch shifts performance after the move to Unreal Engine 5.6, work through reducing lag on a The Isle server after you are back online.

Troubleshooting by symptom

Follow this order rather than changing several things at once: branch, build, registration, config, then player-side checks.

When it is worth letting a host handle patch day

If you are tired of branch mistakes and late-night restarts, look for a panel that exposes the Evrima branch clearly, updates on restart or with one click, supports scheduled restarts, and gives you straightforward backups. For a UK community, a London location is also sensible because it keeps routing and support expectations aligned with your player base. If you are planning a move or sizing a fresh setup, start with The Isle server requirements.

The point is not convenience for its own sake. A good panel shortens the dangerous gap between client patch and server patch, makes it obvious which branch is installed, and gives you a clean recovery path if Game.ini resets after an update. If you want a side-by-side view of those panel differences, backup handling, and branch support, see our The Isle server hosting comparison.

The Isle server FAQ

How do I update my The Isle server?

For rented hosting, stop the server, use the panel’s update method, then let the server boot and sit until EOS registration finishes. For self-hosting, stop the server, back up TheIsle/Saved, then run SteamCMD against app 412680 with -beta evrima validate. Always confirm the installed branch afterwards instead of assuming the update target was correct.

Why does The Isle say version mismatch when I join?

It usually means the client and server are not on the same branch or patch generation. The common cases are a player left on Legacy, a player still on HordeTest, or a server that has not yet been updated after the latest Evrima patch. Right after a patch, timing is often the whole problem.

What is the evrima branch on The Isle dedicated server?

It is the live dedicated server branch for the current version of The Isle, installed from server app 412680. If you run a normal community server for current players, this is the branch you want. On SteamCMD installs, the app manifest should show BetaKey “evrima”.

Can I host a The Isle server on the HordeTest branch?

Not as a normal public community server through the public dedicated server app. The listed dedicated server branches do not include a public hordetesting branch, and HordeTest is used on the developers’ own official test servers. Players on HordeTest cannot join your live Evrima server.

Why is my The Isle server not showing after an update?

The first thing to check is patience: a fresh Evrima boot can take 2-5 minutes to register with Epic Online Services. If it still does not show, verify the [EpicOnlineServices] block is present in Engine.ini and that the server is not boot-looping on a bad Game.ini. If every server disappears for everyone at once, the problem is likely EOS rather than your host.

More The Isle server guides

Compare hosts, tune your settings, size your server or fix lag after a patch.