Getting started with your Rust server

This guide walks you through the first 30 minutes with a fresh Rust server on our panel: logging in, finding the server, starting it, connecting in-game, and changing the basics.

Before You Start

You need:

• An active Rust server rental
• Your panel credentials (sent to your billing email)
• Rust installed on your client through Steam

1. Log Into the GSK Panel

Open app.gameserverkings.com in a browser and sign in with the email and password from your welcome message. If you have not received your credentials, check spam first, then submit a ticket.

Once you are in, your servers are listed on the dashboard. Click your Rust server to open its management page.

2. Tour of the Server Page

The left-hand sidebar has the tabs you will use most often:

• Console is where the server output streams in real time. You can also send RCON commands from here.
• File Manager is for editing configs, uploading plugins, and managing the server's files.
• Schedules lets you run commands or restarts on a recurring timer (used heavily for wipes).
• Startup is where server name, max players, seed, world size, and other launch arguments are configured.
• Backups creates snapshots of your server volume.
• Databases is used by plugins that need MySQL (most do not).
• Sub-Users grants other accounts limited access to your server.
• Settings holds your SFTP credentials and the server rename field.

3. First Boot

Hit the green Start button at the top of the Console tab. The very first boot for a Rust server takes longer than later boots because:

1. The installer downloads the Rust server files with DepotDownloader (about 11 GB at the time of writing). You will see its progress in the console.
2. The server generates a procedural map from your seed and world size.

First boot takes 10 to 20 minutes

A typical fresh install on a barebones config takes 10 to 20 minutes before you see the Server startup complete message. Watch the console for that line.

If the server crashes mid-boot, check:

• That your map size and plugin load are not too heavy for your plan (see Performance Optimization).
• That the seed and world size in the Startup tab are valid numbers.

4. Join Your Rust Server by IP

Your server's address is shown as Address at the top left of the panel, in the form 203.0.113.10:28015. The part after the colon is your game port. Keep it, because every server on a machine has its own.

To connect to your Rust server with that IP:

1. Start Rust and wait for the main menu. You don't need to pick a server.
2. Press F1 to open the console. (Rust Console Commands covers what else you can do from there.)
3. Type client.connect 203.0.113.10:28015, using your own IP and port, and press Enter.

This works whether or not the server shows in the browser. It's also the quickest way back in after a restart. Always include the :port. The IP alone doesn't identify your server.

Streaming? Use connecthidden

client.connecthidden 203.0.113.10:28015 connects the same way but doesn't print the address to the console. Facepunch suggests binding it to a key off-stream so the IP never appears on screen: bind f6 "client.connecthidden 203.0.113.10:28015;console.clear".

If the connection fails

5. Make Yourself Admin

You cannot use admin commands until you have ownerid set. The cleanest way is from the panel's Console:

ownerid 76561197960287930 "YourName" "owner"

Replace 76561197960287930 with your real SteamID64. You can look it up at steamid.io by pasting your Steam profile URL.

You must reconnect — but you do not need server.writecfg

Rust writes users.cfg itself whenever you add or remove an owner or moderator, so admin status already survives a restart. Facepunch's own server guide states it plainly: "No need to save the changes after doing this, it is done automatically now." What you do have to do is reconnect — the auth level is read when you join, so the commands stay unavailable until you rejoin.

For moderator-level access instead of full owner:

moderatorid 76561197960287930 "YourName" "moderator"

6. Common First-Day Changes

Open the Startup tab. The fields most people change on day one are:

World size and seed changes require a full wipe

After changing any Startup field, restart the server for changes to apply. Some changes (world size, seed) require a full wipe to take effect, since they regenerate the map.

World Size and Seed only apply to a procedurally generated map. To run a community-made map instead, you paste a link to its .map file into the Custom Map field on the same tab and clear those two — How to: Install Custom Maps For Rust Servers covers hosting the file and the errors a bad link produces.

7. What to Read Next

• How to Install Oxide is the very next step for most owners, because almost every quality-of-life plugin requires it.
• Wipe Management covers monthly and weekly wipes.
• Popular Plugins lists the plugins almost every server runs.
• How to Make a Rust PvE Server if you want a server without PvP: server.pve or the TruePVE plugin.
• How to Use External RCON Tools connects external tools like RustAdmin and BattleMetrics.
• How to: Install Custom Maps For Rust Servers if you would rather run a community map than a procedural one.

Made with 💜 by GameServerKings