What the Console tab does

Every Witchly server has a Console tab in its manage page. The console gives you:

A live, real-time view of your server’s output (everything the server logs, as it happens)
Power controls — Start, Stop, Restart, Kill
A command input where you type commands and the server executes them
A live state badge — RUNNING, STARTING, STOPPING, OFFLINE
Live resource graphs (CPU, RAM, Disk usage)
A “Jump to latest” button when you scroll up through old logs

It’s the single most-used page on the dashboard once your server is up and running.

Power controls

Four power buttons, in the order you’ll use them most:

Start (green)

Boots the server. The console output streams the startup logs in real time. For a Minecraft server, you’ll see things like “Loading worlds,” “Done!” and similar status messages as the server initialises.

For Minecraft specifically: the first time you click Start on a fresh server, you may be prompted to accept the EULA. See the accepting the EULA doc.

Stop (red)

Sends a graceful shutdown signal. The server saves its world, plugins write their state, players are politely disconnected. This is the right way to stop a server in normal use.

For Minecraft, this is equivalent to typing stop in the console — same shutdown sequence.

Restart (purple)

Combines Stop + Start in one click. Useful after config changes, plugin updates, or as a routine refresh.

Kill (grey, dangerous)

Force-kills the server process immediately. Doesn’t save state. Doesn’t notify plugins. Use only when:

The server is hung and won’t respond to Stop
A startup is stuck mid-init
Something is seriously wrong and you need an immediate hard reset

Don’t use Kill as a normal stop method. You’ll lose the most recent few seconds of game state.

When power buttons are disabled

Power buttons grey out when:

The server is mid-state-transition (during STARTING → can’t Start again, during STOPPING → can’t Stop again)
The server is being installed or reinstalled (entire control plane is locked)
Your account is suspended or banned

If buttons are unexpectedly disabled, check the live state badge — it tells you what state the server is currently in.

The live state badge

Between the power buttons and the uptime display, you’ll see a status pill showing one of:

RUNNING (green) — Server is up and accepting connections
STARTING (purple, pulsing) — Boot sequence in progress
STOPPING (orange, pulsing) — Shutting down
OFFLINE (grey) — Server is not running

The badge updates in real time via the same data feed that drives the resource graphs — no need to refresh the page.

Reading console output

The terminal area shows live server output. Scroll up to see history (the dashboard preserves the last several thousand lines per session).

When new output arrives while you’re scrolled up, a Jump to latest pill appears in the bottom-right of the terminal. Click it to smoothly scroll back to the latest line. This way, you can read older output without losing track of what’s currently happening.

A few output-reading patterns:

Errors are usually prefixed with [ERROR], Exception, or Caused by. Scroll up from a server crash to find the last error before the crash.
Warnings ([WARN]) are non-fatal but worth investigating — often plugin compatibility issues or config errors.
INFO lines are normal operations — don’t worry about them unless you’re debugging something specific.
Stack traces are multi-line dumps starting with at .... The line just above the stack is usually the original cause.

For more on debugging server failures, see Why Your Minecraft Server Won’t Start.

Sending commands

Below the terminal is a command input field. Type a command and press Enter (or click Send) to run it on the server.

Commands are game-specific:

Minecraft

say Hello players! — broadcast a message
kick PlayerName Reason — kick a player
op PlayerName — give a player operator privileges
whitelist add/remove PlayerName — manage whitelist
give @a minecraft:diamond 64 — give every player 64 diamonds
tp PlayerName 100 64 100 — teleport
weather clear / weather rain / weather thunder — change weather
time set day / time set night — change time

The full Minecraft command reference is enormous — see the commands cheat sheet.

Rust

say Hello! — broadcast
kick "PlayerName" "Reason" — kick
ban "PlayerName" "Reason" — ban
oxide.grant user PlayerName admin — grant admin via Oxide
inventory.give PlayerName wood 1000 — give items

See the Rust admin guide for the broader command set.

Palworld, Hytale, etc.

Each game has its own command set. Check that game’s section in the docs for specifics.

Command input is disabled during install

While a server is installing or reinstalling its egg, the command input is greyed out and shows the placeholder “Command input disabled during install…”. This is intentional — the install script needs exclusive control of the server.

The console still streams the install script’s output during this time, so you can watch progress live.

When install finishes, the command input re-enables automatically and the live state badge transitions to RUNNING (or OFFLINE if you have to start manually).

Resource graphs

Below the terminal, you’ll see live graphs for:

CPU usage — percentage of your allocated CPU being used
RAM usage — how much of your allocated RAM the server is using
Disk usage — how full your server’s allocated disk is

These update every second or two. They’re the first place to look when:

Server is laggy → check CPU
Server is crashing → check RAM (probably out of memory)
Server can’t save → check disk (probably full)

Each graph shows a horizontal line marking your plan’s limit, so you can see at a glance how close to the cap you are.

Common console questions

“How do I copy text from the console?” Click and drag to select, then Ctrl+C (or Cmd+C on Mac) — same as any web text. The terminal supports text selection.

“My commands aren’t doing anything” Check that the live state badge says RUNNING. Commands sent to a stopped server are queued or dropped, depending on the game. Also check your spelling — most games are case-sensitive about command syntax.

“The console is showing red errors but the server seems to work” That’s normal. Most modded servers log a handful of non-fatal errors at startup. Worry about errors only if they correlate with actual problems (crashes, missing features, players reporting issues).

“Can I increase the scrollback length?” The console keeps a fixed number of lines per session in your browser. For long-running history, the server writes everything to a log file in /logs/ — open it via the File Manager for older history.

“Can I get notifications when something specific happens?” The dashboard’s notification bell surfaces alerts for renewal, billing, suspension, and a few other system events. For game-specific notifications (e.g., “ping me when a player joins”), most games support this via plugins/mods that send Discord webhooks.

In-Browser File Manager — file editing and uploads
Notifications and Email Preferences — alerts setup
Schedules and Auto-Restarts — automating common commands
Minecraft Commands Cheat Sheet