Overview
Connecting a server takes two customer values: a licence key (a secret shared across your network) and a friendly server name unique to this install. Copy the two-line config into the recorder and start the server; ReplayCore validates online, establishes private per-install identity, and registers itself with your account. If the console then prints [RC-CLAIM-GATE], or the legacy alias [RC-CONFIG-CLAIM] on an already-shipped box, that registration is still unclaimed. Open the printed Downloads URL (https://replaycore.com/en/dashboard/downloads, or /en/dashboard/downloads on a configured self-hosted origin), match the short code, and approve the server.
Your plan's instance limit controls how many distinct servers can record to the cloud at once: Free covers 1 server instance, Starter covers 5, Pro covers 15, and Enterprise is unlimited.
Where to find your credentials
Open Downloads and enter a friendly server name. ReplayCore supplies the two-line configuration, including the secret rck_v1_ account key shared by every server in your network. The owner, or an admin with Server configuration permission, can show the existing key after confirming their password and, when enabled, the emailed two-factor code. Rotate only when the key has leaked or you intentionally want to replace it, because rotation immediately invalidates the old value.
The same licence key is reused across your network. Give each installation a distinct server-name; ReplayCore generates and persists its identity privately, then creates the dashboard server entry on first check-in.
Adding the credentials to a server
Copy the two-line config ReplayCore shows you into plugins/ReplayCore/config.yml, or supply those values as environment variables on container hosts. Keep the licence key out of public repositories and shared backups.
# plugins/ReplayCore/config.yml
license-key: "rck_v1_xxxxxxxxxxxxxxxxxxxx" # secret
server-name: "EU Hub 1" # friendly dashboard label
# Container hosts (recommended): set these instead and keep the secret off disk
# REPLAYCORE_LICENSE_KEY=rck_v1_xxxxxxxxxxxxxxxxxxxx
# REPLAYCORE_SERVER_NAME=EU Hub 1What happens on first start
On startup ReplayCore validates the licence key, creates or reloads a private persistent installation identity, and registers the server under its friendly name. It then appears on the Servers page. An automatic listing is not owner approval. If the console prints [RC-CLAIM-GATE] or the legacy alias [RC-CONFIG-CLAIM], the real short code is in that server's console and /replaycore status. Open the printed Downloads URL (https://replaycore.com/en/dashboard/downloads, or /en/dashboard/downloads on a configured self-hosted origin), match the short code, and approve the server. Approval is not automatic.
A valid licence key and non-blank server name are required for a fresh installation. If either is missing or wrong, the plugin records nothing and logs a clear fix. After a successful registration, a brief cloud outage can use the securely persisted binding during the offline grace window; a brand-new server fails closed until its first registration succeeds.
If activation fails
If you have just purchased a subscription, allow a few minutes for the licence to become active. If validation still fails, open Downloads, enter a friendly server name, and re-copy the two-line config. Confirm server-name is non-blank, and check that the server can reach api.replaycore.com over outbound HTTPS on port 443. The Licence errors article covers the specific error codes.