Set up and use ARK RCONControl the server without being in the game

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

What RCON can do

RCON sends the same commands to the server that you would otherwise enter in the in-game console - just from outside. Typical uses:

• Announcements before scheduled restarts - the friendliest way to stop a server.
• Query the player list to see who is online right now.
• Kick and ban when you get a report while you are out and about.
• Save the world before a manual intervention.

What RCON cannot do: spawn items right in front of you or teleport you - for that, you have to be in the game, see Admin commands.

Requirements

You need three details for the connection:

1. The server address - your server's IP as shown in the web interface.
2. The RCON port - a separate port, not the game port. It is also shown in the web interface.
3. The admin password - RCON uses the same password as the in-game unlock, defined in the GameUserSettings.ini.

On the other end, you use an RCON tool. There are lightweight programs for your computer, browser-based tools and integrations with Discord bots. A simple client is enough to begin with - the only important thing is that it supports the protocol ARK uses.

Connecting

In the tool, you enter the address, RCON port and password and connect. If it works, you get a console where you type commands - the server's response appears directly below.

A good first test is the player list: if a response comes back, the connection is up. If none comes back, it is almost always a wrong port or the password.

Announcing restarts in a friendly way

The most common and best use case. A proven pattern for a restart at midnight:

• 15 minutes before: first announcement.
• 5 minutes before: a reminder with a note to secure your dinos.
• 1 minute before: final warning.
• Right before: save the world, then restart via the task scheduler.

In ARK, this is more than politeness: anyone interrupted while taming may lose hours. An announcement costs you nothing and saves you arguments.

Using RCON as a team

As soon as several people moderate, RCON becomes a tool for everyone - and that is exactly where the question of organization begins. Three approaches have proven themselves, each with its own pros and cons:

• Everyone with their own client. The easiest to set up, but everyone involved has the admin password - and with it full rights, in the game as well.
• A Discord bot as an intermediate layer. The bot knows the password, your team only knows the channel. This lets you limit commands to what the team really needs - such as the player list and kick.
• Only the owner. Completely sufficient for small groups and the safest option.

Because ARK has no tiered roles - whoever has the password can do everything - the middle option is usually the right one for grown communities. For tasks that need no in-game rights at all, such as restarts or file access, there is a better way anyway: subusers in our web interface, see also Admin commands.

Security

RCON is a remote control with full rights - treat the credentials accordingly:

• Use a strong admin password, not the same one as the server password.
• Do not share screenshots of the connection details.
• Change the password when your team changes - it is the only key ARK knows.
• Keep Discord bots with RCON access only in channels your team controls.

When no connection can be established

• Wrong port. The most common case: the game port was entered instead of the RCON port.
• The password is wrong. After a change in the configuration, the server must have been restarted.
• The server is still starting. RCON only responds once the world has fully loaded - on large maps, that takes a while.
• The tool speaks a different protocol. Not every RCON client fits every game.

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

Frequently asked questions