How to Manage Your Game Server: A Complete Dashboard Guide

Starting a game server is step one. Managing it well is everything that comes after — and it’s where most server owners either build a thriving community or watch it fall apart from neglect and preventable mistakes.

A modern hosting dashboard gives you a full set of tools: real-time console access, file management, backups, databases, scheduled automation, plugin installation, resource monitoring, and security controls. Knowing what each tool does and when to reach for it is the difference between reacting to problems and preventing them.

This guide walks through every major feature you’ll find in the Witchly dashboard, but the concepts apply to any panel-based hosting setup. If you’ve just created your first server or you’ve been running one for months without exploring beyond the start button, this is for you.

Server Console

The console is your direct line to the server. It shows real-time output — every log message, player join/leave, error, and warning streams here as it happens.

Reading the Output

The console streams the server’s standard output. For Minecraft, this includes startup progress, plugin load messages, player activity, and error stack traces. For Rust, you’ll see server events, console commands, and player connections. Learning to read this output is one of the most valuable skills you can develop as a server admin.

Pay attention to:

• [ERROR] and [WARN] messages: These indicate problems. Not every warning is critical, but errors during startup usually mean something is misconfigured or a plugin failed to load.
• Startup sequence: Watch for the “Done” message (Minecraft) or the equivalent ready indicator for your game. If the server never reaches it, something is blocking startup.
• Player activity: Connection messages, chat, and command usage all appear here.

Sending Commands

The command input at the bottom of the console lets you run server commands directly. These are the same commands you’d type in-game with operator privileges, but without needing to be connected to the server.

For Minecraft:

op PlayerName
whitelist add PlayerName
say Server restarting in 5 minutes
stop

For Rust:

status
server.save
kick PlayerName "reason"
server.writecfg

Commands execute immediately. There’s no undo — double-check before running destructive commands like world resets or permission changes.

Power Controls

Four power actions are available, and each does something different:

• Start: Boots the server from a stopped state. Loads world files, initializes plugins/mods, opens the port for connections. This is the normal way to turn your server on.
• Stop: Sends a graceful shutdown signal. The server saves all data, disconnects players with a message, and shuts down cleanly. Always prefer this over kill.
• Restart: Performs a stop followed by a start. Use this after config changes, plugin updates, or when performance has degraded over time.
• Kill: Immediately terminates the server process without saving. Use this only when the server is frozen and won’t respond to a stop command. Killing a server can cause data loss or world corruption — it’s a last resort.

Minecraft EULA

The first time you start a Minecraft server, a modal will appear asking you to accept Mojang’s End User License Agreement. This is required — the server won’t start until you accept. It’s a one-time step that sets eula=true in the eula.txt file on your server.

File Management

You have two ways to access your server’s files: the built-in file browser in the dashboard, and SFTP for external access.

Web File Browser

The dashboard file browser lets you navigate your server’s file system directly in your web browser. You can:

• Upload files by dragging and dropping or using the upload button
• Download files individually or download entire folders as ZIP archives
• Create new files and folders directly in the browser
• Edit text files with the built-in editor — useful for quick config changes to server.properties, YAML configs, or JSON files
• Rename and delete files and folders
• Navigate through the directory structure with breadcrumb paths

The web file browser is ideal for quick edits: changing a config value, checking a log file, uploading a single plugin JAR, or downloading a crash report. It’s fast, requires no setup, and works from any device.

SFTP (Secure File Transfer Protocol)

For bulk file transfers — uploading a modpack, downloading your entire world folder, or managing large numbers of files — SFTP is significantly faster and more reliable than the web browser.

Setting up FileZilla (or any SFTP client):

1. Open your server’s settings page in the dashboard to find your SFTP connection details
2. In FileZilla, open the Site Manager and create a new site
3. Set the protocol to SFTP - SSH File Transfer Protocol
4. Enter the host (your server’s SFTP address)
5. Set the port to 2022
6. Enter your username exactly as shown in the dashboard — copy-paste it to avoid errors
7. Enter your password (the same password you use to log into the dashboard)
8. Connect

Once connected, you’ll see your server’s files on the right panel and your local files on the left. Drag files between them to upload or download.

When to use SFTP over the file browser:

• Uploading modpacks or resource packs (multiple large files)
• Downloading a full world backup to your local machine
• Batch-renaming or reorganizing files
• Transferring files larger than 100MB
• Working with files regularly enough that a persistent connection saves time

Backups

Backups are insurance. They cost nothing to create but save everything when something goes wrong — a bad plugin update, a corrupted world, an accidental deletion, or a griefer with operator access.

Creating Backups

The backup panel lets you create manual backups with one click. Each backup captures a snapshot of your server’s files at that moment in time. Give backups meaningful names so you can identify them later — “before-1.21-update” is more useful than “backup-3.”

Restoring Backups

When restoring, you have two options:

• Keep existing files: The backup contents are extracted alongside your current files. Existing files with the same name get overwritten, but files that don’t exist in the backup are left untouched. This is useful when you only want to roll back specific files.
• Replace all files: Your server’s current files are completely replaced with the backup contents. This is a full rollback to the exact state when the backup was created. Use this when you want a clean restore.

Always stop your server before restoring a backup. Restoring while the server is running can cause conflicts between the running process and the files being replaced.

Downloading Backups

You can download any backup as an archive file. This gives you an off-panel copy of your data — useful for local storage, migrating to a different server, or keeping a personal archive that isn’t dependent on your hosting account.

Locking Backups

Locked backups are protected from automatic deletion. When your backup storage fills up, the oldest unlocked backups are removed first to make space. Lock your most important backups — the ones taken before major updates, after significant builds, or at milestones you’d never want to lose.

Backup Strategy

At minimum:

• Before any update: Game version upgrades, plugin updates, mod changes. If the update breaks something, you can roll back in seconds.
• Before installing new mods or plugins: New additions can conflict with existing ones. A backup lets you revert cleanly.
• After major milestones: Finished building your spawn area? Backup. Configured all your permissions? Backup. Just finished a week-long build project? Backup.
• On a regular schedule: Weekly at minimum for active servers. Daily if your community is building constantly. (More on automating this in the Scheduled Tasks section below.)

Database Management

Some plugins and mods need a proper database backend instead of flat files. Economy plugins, permissions managers (like LuckPerms), web-based live maps (like Dynmap or Bluemap), and analytics plugins all perform better — or only work — with a MySQL database.

Creating a Database

The dashboard lets you create MySQL databases directly from your server’s management page. Each database gets its own credentials:

• Host: The database server address
• Port: The connection port (typically 3306)
• Database name: The name of your database
• Username: The database user
• Password: An auto-generated password

You’ll also see a JDBC connection string — this is the full URL that Java-based plugins use to connect. Most Minecraft plugins ask for this in their config files. Copy-paste it directly instead of manually constructing it.

Rotating Passwords

If you suspect a database password has been compromised — or just want to follow good security hygiene — you can rotate the password from the dashboard. After rotating, update the password in every plugin config that references it, then restart your server.

When You Need a Database

Not every server needs one. Here’s when to set one up:

• Economy plugins (EssentialsX Economy, CMI, PlayerPoints): Store balances, transaction logs
• Permissions plugins (LuckPerms): Allows syncing permissions across multiple servers on a network
• Web maps (Dynmap, Bluemap): Store map tile data and markers
• Analytics (Plan, CoreProtect): Track player activity, block changes, and server statistics
• Multi-server setups: Any plugin that needs to share data across servers requires a database

If you’re running a single server with basic plugins, flat-file storage (the default) works fine. Add a database when a plugin specifically benefits from it.

Scheduled Tasks

Manually restarting your server every day and remembering to run backups is tedious and unreliable. Scheduled tasks automate recurring actions so they happen consistently, even when you’re not online.

What You Can Schedule

Three types of actions can be automated:

• Power actions: Automatic restarts, starts, or stops at specific times
• Console commands: Any command that works in the console can be scheduled — say, save-all, whitelist reload, or game-specific commands
• Backup creation: Automated backups on a recurring schedule

Cron Timing

Schedules are defined using cron expressions. If you’ve never used cron before, the dashboard provides presets:

• Every hour: Good for automated saves on busy servers
• Every 6 hours: A reasonable restart interval for most game servers
• Daily: Standard for backups and daily restarts
• Weekly: For less-frequent maintenance tasks

For custom schedules, you can write your own cron expressions. For example:

• 0 6 * * * — Every day at 6:00 AM
• 0 */4 * * * — Every 4 hours
• 30 3 * * 1 — Every Monday at 3:30 AM

Task Chaining

A single schedule can contain multiple tasks that execute in sequence with configurable delays between them. This is powerful for creating graceful restart routines:

1. Send warning (command: say Server restarting in 5 minutes) — delay: 0 seconds
2. Send reminder (command: say Server restarting in 1 minute) — delay: 4 minutes
3. Save the world (command: save-all) — delay: 50 seconds
4. Restart (power action: restart) — delay: 10 seconds

This gives players time to finish what they’re doing, ensures the world is saved, and then restarts cleanly. Without task chaining, you’d need separate schedules for each step.

Recommended Schedule for Most Servers

A solid baseline for any active game server:

• Daily restart at your lowest-traffic time (often 4-6 AM in your community’s timezone), with a 5-minute warning chain
• Daily backup 30 minutes after the restart (so you’re backing up a freshly restarted, clean state)
• Hourly save via save-all (Minecraft) or equivalent — protection against crashes between backups

Adjust frequency based on how active your server is. A 200-player Rust server needs more frequent saves than a 5-player private Minecraft world.

Plugin and Mod Management

Minecraft: Built-in Plugin Installer

For Minecraft servers, the dashboard includes an integrated plugin installer that searches across three major sources:

• Modrinth: The fastest-growing mod and plugin repository
• Hangar: PaperMC’s official plugin repository
• CurseForge: The largest and oldest modding platform

You can search for plugins by name, browse results, select specific versions compatible with your server version, and install with one click. The installer downloads the JAR file directly to your server’s plugins folder.

Update detection: The installer can identify when newer versions of your installed plugins are available, making it easy to keep everything current.

Version selection matters: Always match the plugin version to your server version. A plugin built for 1.21 may not work on 1.20.4, and running mismatched versions is one of the most common causes of server crashes.

Other Games

For Rust, Palworld, Hytale, and other games, plugin and mod management is handled through the file manager or SFTP:

1. Download the mod/plugin from its official source
2. Upload it to the correct directory (e.g., oxide/plugins for Rust with Oxide/uMod)
3. Restart the server to load the new plugin
4. Check the console for load confirmation or errors

The process is straightforward but manual. Always check compatibility with your game version before installing.

Resource Monitoring

The dashboard provides real-time graphs for your server’s resource usage. Learning to read them turns vague complaints like “the server is laggy” into actionable diagnostics.

CPU Usage

Displayed as a percentage of your allocated CPU resources.

• 0-50%: Healthy. Your server has headroom for player surges or intensive tasks.
• 50-80%: Moderate load. Normal during peak activity, but if it sits here constantly, consider optimization.
• 80-100%: High load. Players will experience lag. Investigate what’s consuming CPU — too many entities, unoptimized plugins, or insufficient allocation.
• Sustained 100%: Your server is bottlenecked. It can’t process ticks fast enough. Either optimize (remove heavy plugins, reduce render distance, cull entities) or upgrade your plan for more CPU.

RAM Usage

Shows how much memory your server is consuming out of its allocation.

• Gradual increase over time that periodically drops: This is normal garbage collection in Java-based servers. The JVM allocates memory, uses it, and periodically cleans up. The sawtooth pattern is healthy.
• Steady climb that never drops: Possible memory leak. A plugin or mod is holding references it shouldn’t. Restart the server as an immediate fix and investigate which plugin is responsible.
• Constantly near the limit: Your server needs more RAM, or you have too many plugins/mods loaded. Each plugin, each loaded chunk, and each entity consumes memory.

Disk Usage

Shows current storage consumption. Disk usage tends to grow over time as worlds expand, logs accumulate, and backups stack up.

If you’re approaching your disk limit:

• Delete old logs: The logs/ directory can grow to several gigabytes on active servers. Keep the last week, delete the rest.
• Prune old backups: Unlock and delete backups you no longer need.
• Trim unused worlds: If you’ve generated large worlds you no longer use, removing them frees significant space.
• Check plugin data: Some plugins (especially logging and analytics plugins like CoreProtect) can accumulate large databases.

Uptime

Shows how long the server has been running since its last restart. Long uptimes aren’t inherently good — most game servers benefit from regular restarts to clear memory, reset entity counts, and apply any pending updates.

Network and Ports

Your Server Address

Every server gets an address in the format IP:port. This is what players type into their game client to connect. You can find it on your server’s main page in the dashboard.

Some games have a default port (Minecraft uses 25565, for example). If your server happens to be assigned the default port, players can connect with just the IP address — the game client assumes the default port automatically. Otherwise, the port must be included.

Additional Port Allocations

Some server setups need more than one port:

• Dynmap/Bluemap (Minecraft): Web-based maps that serve a website on a separate port
• RCON: Remote console access on a dedicated port
• Voting plugins: Some voting sites require a specific listener port
• Plugin APIs: Plugins that expose HTTP APIs or webhooks need their own ports

You can request additional port allocations from the dashboard. Each additional port is assigned from the available range and can be configured in your plugin or mod configs.

Setting the Primary Port

If you have multiple ports allocated, you can designate which one is the primary port. This is the port shown as your server’s main address and is the one players connect to.

Custom Domains

Instead of asking players to remember 123.456.789.0:25565, you can point a custom domain at your server. This requires:

1. Owning a domain name
2. Creating an SRV record (for Minecraft) or an A record with the appropriate port configuration
3. Configuring the DNS TTL low enough for changes to propagate quickly

The Witchly documentation covers custom domain setup in detail for each supported game.

Security

Subusers

If you have staff members, builders, or co-admins who need access to the server panel, don’t share your account. Add them as subusers with granular permissions.

You can control exactly what each subuser can do:

• Console access: View output and send commands
• File management: Read, write, create, delete files
• Backup management: Create, restore, delete, download backups
• Database access: View and manage database credentials
• Schedule management: Create and modify scheduled tasks
• User management: Add or remove other subusers
• Power controls: Start, stop, restart, kill the server
• Allocation management: Manage network ports

Follow the principle of least privilege: give each person only the permissions they need. A builder needs file access and maybe console access. They don’t need database management or the ability to add other subusers.

Audit Logs

The dashboard tracks actions taken on your server — who started it, who modified files, who restored a backup. This is invaluable when something goes wrong on a server with multiple people who have access. Instead of asking “who changed the config?”, you can check the audit log and see exactly what happened.

SFTP Password Management

Your SFTP password is the same as your dashboard account password. If you need to change it, do so through your account settings. If you’ve shared SFTP access with someone and need to revoke it, changing your password immediately locks them out.

For shared access, it’s better to use the subuser system with file management permissions rather than sharing your personal SFTP credentials. Subusers get their own SFTP access with their own credentials.

Putting It All Together

A well-managed game server uses all of these tools together. Here’s what a healthy management routine looks like:

Daily (automated):

• Server restarts during low-traffic hours (scheduled task)
• Automated backups after restart (scheduled task)
• World saves every hour (scheduled task)

Weekly (manual check-in):

• Review resource graphs for trends — is RAM usage creeping up? Is CPU spiking at certain times?
• Check disk usage and clean up old logs if needed
• Review the console for recurring errors or warnings
• Check for plugin/mod updates

Before any change:

• Create a manual backup with a descriptive name
• Make the change (plugin update, config edit, mod install)
• Monitor the console during the next startup for errors
• Test in-game that everything works as expected

When something goes wrong:

• Check the console for errors — they usually tell you exactly what happened
• Review resource graphs — was the server out of memory or CPU?
• Restore from backup if needed
• Check the audit log if multiple people have access

The dashboard puts all of these tools in one place. Take the time to explore each section, set up your automation, and build a routine. A server that runs well is a server that retains players.

---

For detailed documentation on specific features covered in this guide, see: Server Management Guide and Schedules and Auto-Restarts.

---

For detailed guides on specific features, check the Witchly documentation. If you get stuck, the community on Discord is always ready to help.