VGKAMI
Advertise Get listed

Game Guides

How to Make a The Isle Evrima Server: Step-by-Step Setup Guide

October 27, 2026 11 min read
Avatar photo
Written byVGKami Team

To make a playable The Isle: Evrima server, install the dedicated-server app with SteamCMD, select the Evrima branch, give the host a stable local IP address, forward the game and queue ports, create both configuration files, add the Epic Online Services credentials, and launch the server. Players must also run Evrima; a Legacy client will not discover an Evrima server.

This guide covers the documented Windows workflow, the native Linux path, firewall and router settings, automatic restarts, discovery testing, and the decision between maintaining your own host and renting managed infrastructure.

What do you need before starting a The Isle server?

A Windows PC is the most fully documented self-hosting route, although Evrima also has a native Linux server build. The host must remain powered on whenever people want to play, and you need administrator access to the router and the host operating system.

  • Correct game branch: Evrima on both the server and every client.
  • Disk space: The Isle.info recommends approximately 40 GB free on the host. Flux describes an approximately 1.5 GB first download; that is a provider-stated download size, not a complete storage recommendation.
  • Router access: You must be able to create port-forwarding rules and preferably reserve a stable LAN address for the host.
  • Firewall access: The operating-system firewall must allow the same ports that the router forwards.
  • EOS credentials: The dedicated-server client ID and client secret belong in Engine.ini. Treat them as private credentials.

No independent current minimum CPU, memory, or bandwidth specification is established in the available documentation. In practice, host capacity depends on the number of players, other processes running on the machine, and the quality of the internet connection, so start conservatively and monitor the server log.

Which The Isle branch should you install?

Choose Evrima deliberately. Legacy and Evrima are separate game worlds, and a Legacy client will not see an Evrima server. The dedicated-server command must include -beta evrima; leaving that switch out installs the older Legacy server according to current hosting documentation.

Match every player to the server branch

Before troubleshooting networking, confirm that the server and each player are on Evrima. A correctly forwarded Legacy server still will not appear to an Evrima client, and the reverse is also true. Branch mismatch is the first check when a server seems to be missing.

Windows and Linux availability

Windows has the most complete published self-hosting instructions. Evrima also provides a native Linux build. On Linux, run the server as a normal, unprivileged user rather than root.

How do you install the Evrima dedicated server with SteamCMD?

SteamCMD installs the dedicated-server app and can validate its files after updates. The app ID is 412680. Create a directory for the server, open SteamCMD, and run the following Windows commands:

login anonymous
force_install_dir C:theisleserver
app_update 412680 -beta evrima validate
quit

For Linux, use the same app ID and branch-selection command with a Linux directory, for example:

login anonymous
force_install_dir /home/theisleserver
app_update 412680 -beta evrima validate
quit

Update after every game patch

Run app_update 412680 -beta evrima validate again whenever Evrima receives a server-relevant update. Updating both the server and the client prevents version mismatches that can look like browser or connection failures.

Keep the installation path simple

Use a dedicated folder with enough free space and avoid placing configuration files in a temporary download directory. The path used by force_install_dir is the folder that will contain the server executable and the TheIsle data directory.

How do you give the host a stable local IP address?

Port-forwarding rules target a local address. If the router gives the host a different address after a reboot, the rules can silently point at the wrong computer. Reserve an address in the router’s DHCP settings or configure a fixed address in Windows.

  1. Open Command Prompt and run ipconfig.
  2. Record the active adapter’s IPv4 address, subnet mask, and default gateway.
  3. In Windows, open the adapter’s IPv4 properties and set an address outside the range that the router dynamically assigns, or create a DHCP reservation in the router.
  4. Reconnect or restart the adapter, then run ipconfig again to confirm that the address has stayed consistent.
  5. Use that confirmed LAN address as the destination in every router-forwarding rule.

A reservation managed by the router is often easier to maintain because it keeps the address tied to the host’s network adapter while leaving the rest of the network on automatic addressing.

Which ports must you forward and allow through the firewall?

The documented assignments separate player traffic, the queue, and remote console access. Create matching inbound rules in the router and in Windows Firewall, but do not publish RCON to the public internet.

Purpose Protocol and port How to handle it
Player connections UDP 7777 Forward to the host’s stable LAN address and allow inbound traffic.
Multiple server instances UDP 7777–7779 The Isle.info documents this range when running a multi-server setup; assign each instance its own port.
Queue TCP 10000 Forward and allow it when using the queue service.
RCON administration TCP 8888 Keep private; do not forward or expose it directly to the internet.

Router procedure

  1. Sign in to the router’s administration page.
  2. Open the port-forwarding, virtual-server, or NAT section.
  3. Create a rule for UDP 7777 pointing to the host’s stable LAN address.
  4. Create a TCP 10000 rule for the queue.
  5. If you operate multiple instances, add the documented UDP range and map each instance as required by its configuration.
  6. Do not create a public TCP 8888 rule for RCON.
  7. Save the rules and reboot the router only if its interface requires it.

Windows Firewall procedure

Create inbound rules matching the protocols and ports used by the router. A router rule without a host-firewall rule still blocks traffic; the two layers must agree. Flux’s current guidance publishes UDP 7777 and TCP 10000 while keeping TCP 8888 unpublished.

Why RCON must stay private

Flux warns that The Isle RCON can trust an address after one correct password. That behavior makes an internet-facing RCON endpoint an unnecessary security risk. Administer it only from the host or a protected private network.

Where should Game.ini and Engine.ini go?

Create the configuration directory under the installed server’s TheIsleSavedConfigWindowsServer path on Windows. On Linux, use TheIsle/Saved/Config/LinuxServer/. Create the directory if it does not exist and verify that the files end in .ini, not .ini.txt.

What belongs in Game.ini?

Game.ini holds gameplay and server-behavior settings. The documented controls include the displayed server name, player cap, map, password, queue behavior, RCON settings, AI, weather, growth, migrations, allowed classes, and other rules. Start with conservative values, launch once, and change one group of settings at a time so a bad value can be identified quickly.

Keep a backup copy before making substantial edits. If the server stops registering after a change, restore the last known-good file and inspect the launch log before changing another setting.

What belongs in Engine.ini?

The EOS identity is required at startup. Add this block to Engine.ini and replace the placeholders with the credentials issued for your dedicated server:

[EpicOnlineServices]
DedicatedServerClientId=<your-eos-dedicated-server-client-id>
DedicatedServerClientSecret=<your-eos-dedicated-server-client-secret>

The client ID and client secret are credentials. Do not paste real values into public guides, repositories, Discord messages, or support tickets. Store the file with restrictive permissions on Linux and limit access to trusted administrators on Windows.

How do you launch the Windows server?

A Windows launch target can start TheIsleServer.exe on the Gateway map, select UDP port 7777, and open the log window:

TheIsleServer.exe Gateway?Port=7777 -log

Run that command from the server installation directory, or use the full path to the executable. The -log switch keeps startup and registration messages visible while you test.

How do you add automatic restarts?

A batch wrapper can update the files first, launch the server, and restart it after an unexpected exit. The documented approach waits 60 seconds after an exit before trying again, which prevents a rapid crash loop from consuming the host.

@echo off
:loop
steamcmd +login anonymous +force_install_dir C:theisleserver +app_update 412680 -beta evrima validate +quit
cd /d C:theisleserver
TheIsleServer.exe Gateway?Port=7777 -log
 timeout /t 60
 goto loop

Adjust the paths to your installation. Keep the update step in the wrapper only if you want every restart to check SteamCMD; otherwise, run updates on a deliberate maintenance schedule and leave the launch loop focused on restarts. Whichever approach you use, watch the log after an update for configuration or EOS errors.

How do you run the native Linux server?

Use the Linux executable installed by SteamCMD and launch it as a normal user. Do not run the dedicated server as root. The Linux configuration directory is TheIsle/Saved/Config/LinuxServer/, and it uses the same two-file arrangement: Game.ini for gameplay settings and Engine.ini for EOS identity.

Keep data persistent

If you run the server in a container, mount persistent storage for the player database, configuration, and bans. Without a persistent mount, replacing the container can remove the data that players and administrators expect to survive a restart.

Use a service manager or wrapper

A Linux service manager or restart script can start the native executable after boot and recover from an unexpected exit. Keep the process under the unprivileged server account and retain the launch output so EOS registration and listening failures can be diagnosed.

How do you test whether the server is visible?

Test with an Evrima client on another computer or another network. Testing only from the host computer can be misleading because some routers do not support NAT loopback, the feature that lets an internal device reach the public address and come back inside.

  1. Update the client to the Evrima branch.
  2. Open the server browser and set the session filter to Unofficial.
  3. Search for the exact server name configured in Game.ini.
  4. Wait for the server log to show EOS registration and a listening state before judging discovery.
  5. If the browser remains empty, try a direct-IP check from an external network as a second test.

A successful external connection proves more than a same-PC test. If friends can connect from outside your home while the host cannot find its own listing, the remaining issue is likely NAT loopback rather than the forwarding rule.

Why is my The Isle server not showing?

Check failures in this order. Starting with branch selection and software versions eliminates the most common causes before you change networking rules.

1. Verify the branch

Confirm that the installation command contains -beta evrima and that every player is running Evrima. An omitted switch installs Legacy, which is a separate world.

2. Update both sides

Run app_update 412680 -beta evrima validate on the host and update the client. A server and client on different builds may fail to appear or reject a connection.

3. Check the destination address

Compare the router rule’s destination with the host’s current ipconfig output. If the address changed, renew the DHCP reservation or correct the forwarding target.

4. Check firewall scope

Confirm that inbound UDP 7777 and TCP 10000 rules exist on the host and that their profiles apply to the active network. A rule limited to the wrong profile can look identical to a missing port-forward.

5. Read the logs

Inspect TheIsle.log or the launch log for EOS registration failures, inability to bind the listening port, or configuration parsing errors. Correct the first error shown rather than changing several files at once.

6. Keep RCON out of the test

Do not open TCP 8888 as a troubleshooting shortcut. RCON is not required for ordinary player discovery, and exposing it creates a security problem.

Should you self-host or rent a managed The Isle server?

Self-hosting costs no separate server rental when you already have suitable hardware, but you become responsible for updates, restarts, backups, firewall rules, EOS credentials, and home-network reliability. Managed hosting trades direct operating-system access for a provider dashboard and ongoing infrastructure management.

Consideration Self-hosting Managed hosting
Control Direct access to Game.ini, Engine.ini, logs, files, and launch scripts. Configuration and operations are generally handled through a provider panel.
Maintenance You perform SteamCMD updates, restarts, backups, and firewall maintenance. Providers such as Flux and Supercraft describe managed patches, backups, and operational support.
Network and security You configure home-router forwarding and keep RCON private yourself. Provider-routed ports and DDoS protection are part of the advertised service features.
Cost model The server download is free; your existing hardware, electricity, and internet connection carry the operating cost. Flux advertises plans starting at $6.49 per month in 2026, with pricing subject to change.
Scale and location Capacity and location are tied to one home connection and host machine. Flux advertises 30-, 60-, and 100-player options, while Supercraft describes multiple datacenter regions.

When self-hosting is a good fit

  • You want unrestricted access to configuration files and logs.
  • You already have a machine that can remain online.
  • You are comfortable managing router rules, updates, and backups.
  • Your group is small enough that one home connection is practical.

When managed hosting is a better fit

  • You do not want to expose or maintain a home network.
  • You need a selectable region, provider DDoS protection, or routine backups.
  • You want a dashboard rather than a SteamCMD and batch-script workflow.
  • You prefer a recurring fee over maintaining hardware and electricity costs.

Neither model removes the need to match the Evrima branch and keep client and server versions aligned. Managed infrastructure reduces operational work; it does not change the game’s branch or configuration requirements.

What should you check before inviting players?

  • Confirm the server launches with the Gateway map and the intended player port.
  • Confirm the browser filter is set to Unofficial when searching.
  • Test from outside the host’s LAN.
  • Back up both configuration files before editing them.
  • Keep EOS credentials out of public channels and repositories.
  • Verify that RCON is not published by the router.
  • Record the stable LAN address, forwarded ports, and restart procedure for anyone who will administer the server.

Frequently Asked Questions

How much disk space does a The Isle server really need?

The first download is described by Flux as approximately 1.5 GB, but The Isle.info recommends keeping about 40 GB free on the host. The larger figure gives room for installed files, updates, logs, and normal operating overhead rather than describing only the initial download.

Why can friends join while the host computer cannot find the server?

Some home routers do not support NAT loopback, so an internal computer may be unable to reach the public address even when outside players can connect. Use an external test device or network to distinguish that local-router limitation from a real forwarding failure.

Can I expose RCON temporarily while setting up the server?

Do not publish TCP 8888 as a setup shortcut. The documented warning is that RCON can trust an address after one correct password, so administer it only from the host or a private, controlled network.

Is a managed host faster to set up than running the server at home?

A managed service removes much of the router, firewall, restart, and backup work and may offer selectable regions and DDoS protection. Self-hosting remains the more flexible option when you need direct file, log, and launch-script access.