Fix common ARK Survival Ascended server errors

Most ARK: Survival Ascended server problems come from a server that’s still starting, a version or mod that doesn’t match, or a server that ran short of memory. Find the problem below and follow the steps. The most common ones are first.

Quick checks

• Overview says the server is running, not starting.
• You’re searching the Unofficial list, with the exact server name.
• PC players joining by address use the port from the address card, not 7777.
• After a game update or mod update, the server has restarted.

Joining problems

Your server isn’t in the server list

Why it happens: the server is still starting or asleep, it’s on an older game version than the player, or the list’s filter hides it.

Fix it:

1. Look at Overview. ARK takes a few minutes to start, and longer with many mods. Wait until Console shows the server has finished starting.
2. Give a new server a few more minutes after that. It takes a while to show up in the list.
3. Set the filter to Unofficial, and search for the exact name you set in Settings.
4. If the server is asleep, it isn’t in the list. Open your wake link, play.wilderack.com/w/dinoshore, or turn sleep off under Settings > Sleep.
5. If the game just updated, restart the server. See nobody can join after a game update.

PC players can skip the list and join by address. See how to connect.

Joining fails or times out

Why it happens: the server is still starting, the player and server are on different versions, a mod just changed, or the player typed the wrong port.

Fix it:

1. Wait until the server has fully started, then join again.
2. On PC, check the port in your open command. It must be the one on your address card.
3. Restart the server if the game or a mod updated recently.
4. Players can restart their game. On PC, they can also verify the game files in Steam (Properties > Installed Files).
5. Look at RAM on Overview. If it’s at your plan’s limit, see the server crashes or runs out of memory.

The password isn’t accepted

Why it happens: the player typed the admin password instead of the server password, or the password changed and the server hasn’t restarted.

Fix it:

1. Check the server password in Settings. It’s ServerPassword in GameUserSettings.ini.
2. Restart the server after you change it.
3. Players type the server password, not the admin password, when they join.
4. On PC, if joining by address doesn’t get you into a server with a password, join from the list. The game asks for the password there.

Console players can’t find the server

Why it happens: the server is asleep, a start option limits it to PC, or the server is on a different version than the console game.

Fix it:

1. Make sure the server is awake. Console players can only join from the list.
2. Open Settings > Startup. If you see -ServerPlatform=PC, remove it, or add the consoles you want. By default every platform can join.
3. If the game just updated, restart the server so it runs the newest version.
4. Check the console player is searching Unofficial.

A mod error stops players joining

Why it happens: a mod updated on CurseForge after the server started, so the player’s version and the server’s version differ. Or a premium mod in the list hasn’t been bought by that player.

Fix it:

1. Restart the server. It downloads mod updates when it starts.
2. Ask the player to join again, so their game gets the same versions.
3. If the server uses a premium mod, every player must buy it on their own platform. See premium mods.
4. If one mod keeps failing, remove it in Mods, restart and test again.

Nobody can join after a game update

Why it happens: players got the new version, but the server is still on the old one.

Fix it:

1. Restart the server. It installs the newest version when it starts, unless you pinned a version under Settings > Game version.
2. If you pinned a version, change it back to the newest one.
3. Mods sometimes need a few days to catch up after a big update. If the server won’t start, check Console for the mod it stopped on.

Server and admin problems

enablecheats doesn’t work

Why it happens: the password doesn’t match, or the server hasn’t restarted since you changed it.

Fix it:

1. Check the admin password under Settings > Players.
2. Restart the server if you just changed it.
3. Join the server, open the console and type enablecheats, a space, and the password, with no quotes.
4. Put cheat in front of each admin command, like cheat fly.

See admin commands.

The server takes a long time to start

Why it happens: the first start downloads the game from Steam, then your mods from CurseForge. Big maps with many mods take longest every time.

Fix it:

1. Watch Console. As long as new lines appear, it’s working. Don’t restart it halfway.
2. Wait up to about 15 minutes on a big modded map.
3. If it stops at the same mod each time, remove that mod and try again.

The server crashes or runs out of memory

Why it happens: the server needed more memory than your plan has. Many tames, big bases and big mod lists all add up. Console shows a helper card with a hint when it recognises a crash.

Fix it:

1. Look at RAM on Overview for the time of the crash.
2. Restart the server.
3. Lower tame limits and remove mods you don’t use. See performance.
4. Move up a plan if RAM keeps hitting the limit.

Changes to the config files don’t stick

Why it happens: the setting is on the server’s start line, which wins over the files, or the key is in the wrong place in the file.

Fix it:

1. Change the server name, map, max players, admin password and mods in Settings, not in the files.
2. Stop the server, edit the file under Settings > Advanced, then start it again.
3. Check the key is under the right section header, like [ServerSettings] in GameUserSettings.ini. See the config reference.

Still stuck?

Download the latest log from Files and send it to support@wilderack.com with what you tried. Real people read every message.