Troubleshooting

The most common issues on a The Isle Evrima server, and how to fix them. In every case, the panel Console is your first tool: read the last lines shown before the shutdown or error. The full logs are also in TheIsle/Saved/Logs/.

The server does not start

After a configuration change

A misspelled key, a line in the wrong section or an invalid value can prevent startup or make a setting ineffective.

1. Stop the server
2. Compare Game.ini and Engine.ini with your last working copy
3. Undo the last change, then restart
4. If the server starts again, reapply your changes one by one

See Configuring Game.ini and Engine.ini.

The server stops during startup

If the server stops with no obvious error, especially with lots of AI or players, memory may be insufficient: see Lag and insufficient memory.

Modified or incomplete game files

The server runs natively on Linux with the official dedicated server files. Do not replace or delete game files outside TheIsle/Saved/. If the server no longer starts after an update or file changes, contact support: the game files may need to be reinstalled, after backing up your configuration.

Players cannot find or join the server

Symptom	Likely cause	Fix
The server does not appear in the list	Server still starting, or search too broad	Wait for startup to finish in the console, search for the exact name set in ServerName
The server still does not appear	Port changed by hand in the configuration	Put back the port assigned by the panel, restart
Connection refused after an update	Client and server on different versions	See Game version different from the server's
Password rejected	Password changed without a restart	Restart the server after changing ServerPassword
Player refused although everything looks right	Whitelist enabled without their SteamID64	Add them to the whitelist, see Becoming an admin
Server full	Maximum player count reached	Raise the value (keeping resources in mind) or enable the queue
The player is on console	The Isle only exists on PC	Only PC (Steam) players can join

Ports

Port opening is handled by YorkHost. Do not change the game port in the configuration: the server must listen on the port assigned by the panel. See Are all ports open? and Unable to connect to the server.

The queue or RCON does not work

The queue and RCON each use their own port, which must be one of the ports assigned to your server. A port picked at random will not be reachable. See Ports, RCON and queue.

Game version different from the server's

The Isle Evrima is updated frequently. The server must run the same version as your players' game.

• The server is behind: the dedicated server update has not been applied yet. Restart the server; if it stays on the old version, contact support. See Backups and updates.
• The players are behind: they need to let Steam update the game.
• Wrong branch: in the game's properties on Steam (Betas tab), players must be on the Evrima version used by the server, not on an old branch.

Take a backup before every update, and review Game.ini afterwards: some settings may have been renamed.

Lag and insufficient memory

On Evrima, two factors weigh the most on performance: the CPU, mostly loaded on one main core by the simulation, and AI density, which drives RAM usage up.

If the server lags or stops for lack of memory:

1. Lower AIDensity: it is the setting with the biggest impact on RAM. See AI, playable dinosaurs and growth.
2. Reduce the maximum player count if it exceeds your plan's guidelines.
3. Restart the server regularly, for example every night at an off-peak time, with an automatic restart from the Schedules tab.
4. Monitor usage in the panel during peak hours, to see whether the limit is RAM or CPU.

If the server stays saturated despite these settings, a bigger plan is justified: see the guidelines in Getting started. To analyse resource usage, see also Performance debugging.

Still stuck?

Contact support 7 days a week on Discord or through your client area, including:

• your server's name
• what you changed just before the problem
• the last console lines at the time of the error