Fix ARK connection problemsServer not visible, timeout, mod errors

Published on September 2, 2026 · last updated on November 8, 2026

First: is the server running at all?

A look at the web interface settles that in seconds. Two things are important to know:

• Startup takes time. ARK loads the entire world - on large maps with mods, that takes several minutes. During this time, the server is not reachable even though it is running.
• After a restart, getting listed takes longer than becoming reachable. Connecting directly often already works while the browser still shows nothing.

If the server still does not appear after five minutes, move on to the address.

Connect directly instead of searching

The ARK server browser is the least reliable way onto a server - it likes to filter, sort and forget. The reliable way is the fixed server address made of IP and port that is shown for your server in the web interface.

Your fellow players add this address to their favorites list. Once set, it stays there and works regardless of whether the browser currently finds the server. Important: what counts is the port we give you - not the default port from guides on the internet, because with us, servers share an IP and are told apart by their port.

How the address and ports are put together in general is explained in Ports and firewall.

Mods as the cause

If individual players cannot get onto the server while others play without problems, mods are almost always involved:

• The client has a different mod version. After a mod update, the player has to update as well - Steam usually takes care of that at launch.
• The download is stuck. An interrupted mod download on the client leads to failures when joining.
• The server has updated, the client has not. That is why a restart on both sides is worth it after every larger mod update, see Install mods.

A good test: a player who gets onto the server and one who does not compare their mod lists in the game. Usually the difference is visible right away.

Timeout when joining

A timeout does not necessarily mean that the server is unreachable. Common causes:

• The server is still loading - see above, especially after a restart.
• The world is large. On grown servers, joining takes longer; some clients give up too early.
• The client is downloading mods. On the first join, that can take a while.
• The server is overloaded. If it happens reproducibly at peak times, it is worth looking at RAM requirements and restarts.

A second attempt after one or two minutes settles most cases - it sounds trivial, but in ARK it really is the most common solution.

The server does not start at all

If the server stops again right after starting, it is almost never the network but the configuration:

• A faulty INI file. A typo in the Game.ini - especially in the experience curve - can prevent startup.
• A mod map without the matching map setting, see Change the map.
• Two mods that exclude each other. As a test, remove the one added last.
• A damaged save. Rare, but possible - then the last backup helps, see Back up your save.

When only one player has trouble

If everyone except one person gets in without problems, the issue is on that person's side. The usual suspects: a stuck mod download, an incomplete game installation or a network filter on the home network.

What helps, in this order: restart the game, let Steam verify the mods, verify the game files, try joining over a different connection as a test. And in any case, try joining via the favorites list instead of the browser.

Frequently asked questions