Few things kill a dinosaur server’s momentum faster than a wave of “I can’t connect” messages in Discord right after you spin it up — or right after a patch drops. The good news: nearly every “can’t connect to server” problem in The Isle Evrima comes down to a short list of well-understood causes — UDP ports, a version mismatch, EOS registration, a stray password or whitelist toggle, or NAT hairpinning when you try to join your own box. This guide walks through each one in the order you should actually check them, with the real config keys, ports, and values that matter on the live Evrima branch.
Everything here applies to the current Evrima build of The Isle — the live game — not the old Legacy branch. That distinction matters more than you’d think, because a lot of outdated guides still reference Legacy ports (27015–27017) and a ?listen launch flag that simply don’t apply to Evrima anymore. If you’re following along on a fresh build, our full Evrima dedicated server setup walkthrough covers install from scratch; this article focuses purely on the connection failures.
Start here: the 60-second triage
Before you change a single config value, narrow down which kind of failure you have. The symptoms point you to the cause:
- Server doesn’t appear in the browser at all → almost always a version/branch mismatch, blocked UDP ports, or missing EOS credentials.
- Server shows up but won’t let players in → password, whitelist, full server, or a port collision between instances.
- Everyone can join except you (from the same network) → NAT hairpinning / reverse-NAT. The server is fine; your own machine just can’t loop back to it.
- Worked yesterday, broke today → a game patch shipped. Your server is now a different version than your players. Update it.
Hold those buckets in mind as you read — they’ll tell you which section to jump to.
Cause #1: Version / branch mismatch after a patch
This is the single most common reason a previously-working server vanishes from the list. The Isle’s client and server must run the same game version. When a patch lands on Steam, players auto-update — but your dedicated server does not update itself. Until you re-run SteamCMD, the server is a version behind and becomes invisible (or unjoinable) to up-to-date clients.
The fix is to re-run the update against the evrima beta branch. The dedicated server App ID is 412680, and you must keep the -beta evrima flag — without it, SteamCMD pulls the old Legacy build instead of the live game:
login anonymous
force_install_dir C:\theisleserver
app_update 412680 -beta evrima validate
quitOr as a one-liner: steamcmd +login anonymous +force_install_dir . The validate keyword forces SteamCMD to re-check every file, which also repairs a half-finished update that can leave the server in a broken, won’t-list state. Make a habit of running this immediately whenever you see “this server is running a different version” or the server simply disappears from the browser.
If you host with a managed provider, this update is usually a one-click action in the panel. Either way, restart the server after updating so it re-registers with the live server list.
Cause #2: Ports and firewall (the most common fresh-install failure)
Evrima’s networking is UDP-first, and the ports are different from the old Legacy branch. Get these exactly right and most “doesn’t show up” problems evaporate. Here’s the full port map for a single Evrima server:
| Purpose | Port | Protocol | Notes |
|---|---|---|---|
| Game port | 7777 | UDP | Primary traffic — this is the one that breaks connections if blocked |
| Query port | 7777 | UDP | Evrima reuses the game port; forward the 7777–7779 UDP range to be safe |
| RCON port | 8888 | TCP | Remote admin only — not needed for players to connect |
| Queue port | 10000 | TCP | Used when the join queue is enabled |
Two practical points. First, unlike many Source-engine games, Evrima does not use a separate Steam query port on 27015 — that’s Legacy advice and it does not apply. The game and query both live on UDP 7777. Second, because some tooling expects a small block, the safe move is to forward the entire UDP 7777–7779 range to your server’s LAN IP. (One source lists 7778 as the query port; forwarding the 7777–7779 range covers that ambiguity completely.)
The fix has two layers that people frequently confuse:
- Router port forwarding — forward UDP 7777–7779 to the internal IP of the machine running the server. This is what lets outside players reach you at all.
- OS firewall rule — even with forwarding correct, Windows Defender Firewall (or
ufw/iptableson Linux) can silently block the inbound packets. Add an explicit inbound allow rule for the UDP ports and for the executable itself:TheIsleServer.exeon Windows orTheIsleServer.shon Linux.
If players still can’t reach you after both are set, double-check you forwarded UDP and not TCP — this is a remarkably common slip. RCON (8888) and the queue port (10000) are TCP, but the actual game traffic that lets a player connect is UDP.
Cause #3: Missing or invalid EOS credentials (server won’t list)
Evrima registers with the server browser through Epic Online Services (EOS), which also powers its cross-play. If the EOS dedicated-server credentials are missing or wrong, the server can run perfectly fine locally yet never appear in the public list — which looks exactly like a “can’t connect” bug to your players.
These credentials live in Engine.ini, under the [EpicOnlineServices] section:
[EpicOnlineServices]
DedicatedServerClientId=
DedicatedServerClientSecret= The exact ID and secret ship with the standard Evrima server template and are environment-specific — don’t copy a random value off a forum. Use the values from the official server template or, if you’re on managed hosting, the ones your provider pre-configures (they’re usually filled in for you). These can also be passed as launch flags, e.g. -ini:Engine:[EpicOnlineServices]:DedicatedServerClientId=..., which is handy when a panel manages your config files. If your Engine.ini is on the Windows path TheIsle\Saved\Config\WindowsServer\ (or TheIsle/Saved/Config/LinuxServer/ on Linux) and the block is present and intact, EOS registration should succeed on the next restart.
Cause #4: Password set but players aren’t entering it
A password mismatch produces a clean “connection refused” rather than an invisible server — so if players see the server but get bounced, check this first. In Game.ini under [/Script/TheIsle.TIGameSession], two keys control this:
bServerPassword=true
ServerPassword="your-password-here"If bServerPassword=true, every player must enter the exact value of ServerPassword to join. Common gotchas: you set the password but never shared the current one, the password has a typo, or you changed it and forgot to tell people. To run a fully public server, simply set bServerPassword=false and restart. Remember that any change to Game.ini only takes effect on a server restart — editing a live config does nothing until you reboot the instance.
Cause #5: Whitelist is on
If you’ve enabled whitelist mode, anyone whose Steam64 ID isn’t on the list is blocked — even with the correct password. This catches people who turned on whitelisting during a private testing phase and forgot. In Game.ini under [/Script/TheIsle.TIGameStateBase]:
[/Script/TheIsle.TIGameStateBase]
WhitelistIDs=7656119xxxxxxxxxx
WhitelistIDs=7656119yyyyyyyyyyThe toggle itself, bServerWhitelist, lives in [/Script/TheIsle.TIGameSession]. Either add each player’s Steam64 ID on its own WhitelistIDs line, or set bServerWhitelist=false to open the doors to everyone. You can also manage the whitelist live over RCON with togglewhitelist, addwhitelist and removewhitelist — useful so you don’t have to restart for every new player.
Cause #6: Full server or a join queue
If the slots are maxed, new players can’t get in until someone leaves. The cap is set by MaxPlayerCount in [/Script/TheIsle.TIGameSession] (e.g. MaxPlayerCount=100). If you want would-be joiners to wait in line rather than be turned away, enable the queue:
bQueueEnabled=true
QueuePort=10000With the queue on, make sure the queue port (TCP 10000 by default) is forwarded and open, exactly like your other ports — otherwise the queue itself becomes a connection blocker. You can check the live queue state with the RCON command getqueuestatus.
Cause #7: Port collision between multiple servers
Running more than one Evrima instance on a single box? Two servers fighting over the same Port, RconPort, or QueuePort will cause one (or both) to fail to bind and never list. Give each instance a clean, non-overlapping block of ports and forward each separately:
| Setting | Server 1 | Server 2 |
|---|---|---|
| Game/Query Port (UDP) | 7777 | 7787 |
| RconPort (TCP) | 8888 | 8889 |
| QueuePort (TCP) | 10000 | 10001 |
Increment in tidy blocks like this and forward every port for every instance. If you under-provision the hardware, performance problems can also masquerade as connection issues — our Evrima server requirements and RAM guide breaks down how many slots a given CPU and memory budget can actually carry.
Cause #8: You can’t join your own server (NAT hairpinning)
This one panics people unnecessarily. If everyone else can join but you — on the same network or the same machine as the server — cannot see or connect to it, your server is almost certainly working fine. The problem is NAT hairpinning (also called reverse NAT or NAT loopback): many routers won’t route a request from inside the LAN back to your own public IP. This behavior is well documented for The Isle specifically.
- Best test: have a friend on a completely different network try to connect. If they can, your server is healthy and this is purely a loopback quirk.
- To join it yourself anyway: enable NAT loopback / hairpinning on your router if it’s supported, or connect via the server’s local LAN IP instead of the public address when you’re on the same network.
Cause #9: Browser filters hiding the server
Sometimes the server is up, listed, and reachable — but a player’s browser filters are hiding it. Region or ping filters, or a “password servers” filter, can all suppress a server that’s working perfectly. Ask the player to clear every filter in the browser and search directly by the exact server name. It’s a low-tech fix, but it resolves a surprising number of “I just can’t find it” reports.
A note on anti-cheat and “direct connect”
The Isle uses client-side anti-cheat, but there is no standard player-facing server-side anti-cheat toggle in Game.ini — so don’t go hunting for an “EAC” key to flip when troubleshooting connections. If you find a guide telling you to edit an EAC setting in your server config to fix joins, treat it with skepticism; that’s not a documented Evrima configuration key. The connection-level causes above (version, ports, EOS, password, whitelist) are what actually govern whether a player can join.
Similarly, Evrima’s server browser plus EOS registration is the normal join path. There isn’t a separate Legacy-style ?listen mechanism to enable, and the modern launch form is simply something like ?Port=7777 -log. If your server registers with EOS and your ports are open, players reach it through the in-game browser.
Verifying the fix with RCON
Once the server is listing and accepting players, RCON is the fastest way to confirm everything’s healthy and to manage the live session. Enable it in Game.ini under [/Script/TheIsle.TIGameSession]:
bRconEnabled=true
RconPassword="something-long-and-secret"
RconPort=8888One critical caveat: standard Source-engine RCON tools and mcrcon do NOT work with Evrima. The Isle speaks its own RCON protocol, so you must use an Evrima-compatible RCON client (community tools and bots built for The Isle). Don’t waste an hour trying to connect a generic RCON tool — it’s a protocol incompatibility, not a config error. Once connected, useful verification commands include playerlist (see who’s actually on), getqueuestatus, and announce to confirm two-way communication. Argument formatting (comma vs space) varies by client, so check your chosen tool’s docs for exact syntax. For the full command set and moderation workflow, see our Evrima admin commands and moderation guide.
Quick reference: the keys that affect connections
| Key (section) | What it does | Set it to… |
|---|---|---|
bServerPassword / ServerPassword (TIGameSession) | Require a join password | false for a public server |
bServerWhitelist + WhitelistIDs (TIGameSession / TIGameStateBase) | Restrict to listed Steam64 IDs | false to allow everyone |
MaxPlayerCount (TIGameSession) | Slot cap | e.g. 100 |
bQueueEnabled / QueuePort (TIGameSession) | Join queue when full | true + open TCP 10000 |
bRconEnabled / RconPort (TIGameSession) | Remote admin access | true + open TCP 8888 |
[EpicOnlineServices] block (Engine.ini) | EOS server-list registration | Valid client ID + secret |
If you’d rather not wrestle with port forwarding, EOS credentials and patch-day updates at all, managed The Isle Evrima hosting handles the version updates, opens the right ports out of the box, and pre-fills EOS so your server lists on first boot. For the complete configuration reference — every Game.ini key, growth and migration settings, and step-by-step panel screenshots — see the The Isle documentation.
Frequently asked questions
Why can’t I connect to my The Isle Evrima server after a game update?
Because your server is now a different version than your players. Steam auto-updates the client, but the dedicated server doesn’t update itself. Re-run SteamCMD against the live branch — app_update 412680 -beta evrima validate — then restart. Once the server version matches the client version, it reappears in the browser and accepts connections. This is the number-one cause of a server that “suddenly stopped working.”
What ports do I need to open for The Isle Evrima?
The essential one is the game port, UDP 7777, which Evrima also uses for queries. The safe approach is to forward the entire UDP 7777–7779 range to your server’s LAN IP and add a matching inbound firewall rule. RCON uses TCP 8888 and the join queue uses TCP 10000, but neither is required for players to simply connect. Ignore any guide mentioning ports 27015–27017 — those are from the old Legacy branch.
Players can see my server but can’t join — what’s wrong?
A visible-but-unjoinable server points to an access setting rather than a network problem. Check, in order: bServerPassword=true with a password players don’t have or are mistyping; bServerWhitelist=true blocking anyone not in WhitelistIDs; the server being full (MaxPlayerCount reached); or a port collision with a second instance sharing the same Port/RconPort/QueuePort. Fix the relevant setting in Game.ini and restart.
Why can everyone join except me on the same network?
That’s NAT hairpinning (NAT loopback). Many routers can’t route a request from inside your LAN back to your own public IP, so you can’t reach your own server via its public address even though outside players can. Confirm by having someone on a different network join — if they succeed, your server is healthy. To play on it yourself, enable NAT loopback on your router or connect using the server’s local LAN IP instead.
My server isn’t showing in the server list at all — how do I fix it?
An entirely invisible server usually means one of three things: a version/branch mismatch (update with -beta evrima validate), UDP 7777–7779 not forwarded or blocked by the firewall, or missing/invalid EOS credentials in Engine.ini’s [EpicOnlineServices] block. Work through those three, restarting after each change. We cover this specific symptom in depth in our guide on fixing an Evrima server that won’t appear in the list.
Do I need to configure EAC or anti-cheat on the server to let players connect?
No. The Isle’s anti-cheat runs client-side, and there is no standard player-facing server-side anti-cheat toggle in Game.ini to edit. Don’t add an invented “EAC” key in an attempt to fix connections — it won’t exist and won’t help. What actually governs whether players can join are the version match, open UDP ports, valid EOS registration, and your password/whitelist settings. Focus your troubleshooting there.
Work through the nine causes above in order and you’ll resolve virtually every “can’t connect” report. Most of the time it’s a one-line SteamCMD update after a patch, or a forgotten UDP forward — both quick fixes once you know where to look.
Free The Isle Tools
Speed up your server with our free The Isle tools:
Ready to play?
Run your own The Isle Evrima server with XGamingServer
Spin up an always-on The Isle Evrima server your friends can join in minutes — no port-forwarding, no tech headaches.
