Connecting RCON and Host Access

RCON

Servycore uses Rust's WebRCON (rcon.web 1). Open the server's Configuration (in the menu, under the server) and its Connection tab, enter the IP, the RCON port and the RCON password, then Test the connection.

This is the only place where the server's addresses and RCON are set: the Control Center and the linking commands use the same connection. In the Settings tab, the connection method decides how linking commands reach the server: RCON uses this connection, or pick Plugin or Pterodactyl to send them another way.

• After 2 refused passwords, Servycore pauses RCON for this server until you fix the password (it tries again after 10 minutes, and the minute check once an hour): Rust bans an IP for 5 minutes after 5 wrong passwords, and Servycore never gets that far.
• Servycore opens short connections and spaces them out (at most 4 new connections every 5 seconds per server), because some hosts refuse a burst of connections for a few seconds.
• The Overview shows what Servycore knows about the server: address and ports, map, framework (Oxide / Carbon), protocol, FPS limit, save interval and more.

Host access (optional)

Host access lets Servycore manage files and power. It comes after RCON: set up RCON first (Servycore checks your server over RCON before and after every action on your host). In the Connection tab, under Host access, pick one:

Secrets are never sent back to your browser, and private network addresses are refused.

To remove host access, pick None and Save: Servycore asks you to confirm, then deletes the saved credentials (the auto-wipe system turns off). Replacing a panel with SFTP / FTP asks to confirm too. If your linking commands go through your Pterodactyl panel, removing or replacing that panel sends them over RCON instead: set up RCON first, Servycore keeps the panel until then.

Find your panel API key

Pick Pterodactyl / Pelican / WISP / AMP, then Pterodactyl / Pelican / WISP under Panel. Servycore needs three things from your panel: its address, the server id and a client API key. It finds by itself whether the panel is Pterodactyl, Pelican or WISP (AMP works differently, see below).

1. Panel address: the address you open to manage your server, for example https://panel.yourhost.com.
2. Server id: open your server in the panel and copy the code after /server/ in the address bar (https://panel.yourhost.com/server/1a2b3c4d → 1a2b3c4d).
3. API key: create one on the page of your panel:

The key is shown only once: paste it in Servycore right away. Use an account that only has access to this server (a subuser), so the key cannot reach your other servers. When you type the panel address in Servycore, the form gives you the direct links to these pages.

After Save, Servycore tests the panel: it says which panel it found and checks that the server id is this server (the panel's address of the server must match the one Servycore reaches over RCON). A wrong server id is shown in red: a wipe would otherwise stop and delete the other server.

Connect AMP

AMP (by CubeCoders) has no API key. Pick Pterodactyl / Pelican / WISP / AMP, then AMP under Panel: the form asks for the AMP address, your AMP username and password (and the 2FA code if your account has one).

• Servycore uses the password once: it logs in, creates a login token named "Servycore · your project · your server" and keeps only that token. The password is never stored.
• With an AMP controller holding several servers, Servycore finds the Rust instance of this server by its game port. When it cannot tell, it lists your Rust instances: pick the right one and save again.
• Use an AMP user that only has access to this instance. If your AMP is reached over http://, the password crosses the Internet in clear text once: prefer its https:// address.
• Servycore makes no AMP backup during a wipe (AMP backs up the whole instance): wipes go on without one.
• The instance itself must be running in AMP (not only the game): Servycore starts and stops the game, not the instance.