Quick start
From an approved access request to a running server, in about ten minutes.
Before you start
You need the panel invitation that arrived after your access request, and the game you want to run. Ports are opened by the panel — you do not need to touch a firewall rule to get started.
Create the instance
- Sign in to the panelUse the address from the invitation. The account is already attached to a node; the panel shows which one in the header.
- New instancePick the game from the template list. Templates are grouped by game and marked with the version they pin.
- Choose a planThe panel shows the memory and disk the template needs at minimum. If you pick something smaller, it warns you instead of failing later.
- Name itThe name becomes the subdomain (
myworld.amber.cfngg.net) and the directory name. Lowercase letters, digits and dashes. - StartFirst start downloads the game files. Minecraft takes about a minute; Rust and ARK take longer because the download is several gigabytes.
What you get
| Item | Where |
|---|---|
| Server address | Panel → instance → Connection |
| Console | Panel → instance → Console |
| Files | Panel → instance → Files, or SFTP |
| Backups | Panel → instance → Backups |
| Usage | Panel → instance → Traffic |
First settings worth changing
Set the player limit, the world seed and the difficulty before inviting anyone. On Minecraft, set view-distance to 8 rather than 10 if you are on Sandbox 2 — it is the single most effective memory setting and it costs very little visually.
Console first
If the server does not appear in the game's server browser, open the console before changing anything. Nine times out of ten the last line says exactly what is wrong, and it is usually a wrong game version on the client.