Control panel basics

The console streams your server’s live output and accepts commands exactly as a server operator would type them — no leading slash. Start, Restart and Stop send a graceful shutdown; Kill terminates the process immediately and can corrupt a world mid-save, so keep it for a genuinely hung server.

The built-in file manager handles quick edits, uploads and archive extraction. For bulk transfers use SFTP with the host, port and username shown on your server’s settings tab; the password is your panel password. Always stop the server before replacing world folders or jars.

Create a MySQL database from the Databases tab and the panel generates the host, name, user and password for you. Plugins usually want the internal host rather than the public one. Your plan sets how many databases you can create; upgrading raises the limit immediately.

Backups snapshot the whole server directory and count against your plan’s backup slots. Take one before every modpack update or major config change, and download anything you want to keep long term — slots rotate as new backups are created.

Schedules run cron-style actions: nightly restarts, automated backups, or a warning command broadcast before a restart. Chain tasks inside one schedule with delays so a broadcast fires before the restart it announces.

Invite staff by email and grant only the permissions they need — console access without file deletion is a good default for moderators. Subusers need their own panel account; billing stays with the account owner.

CPU is expressed in percent where 100% equals one core, memory is a hard cap enforced by the container, and disk is total on-disk usage including backups stored in place. Hitting the memory cap kills the process with exit code 137 — that is a sizing problem, not a crash. You can resize at any time from your service settings.