Use the console and power controls

The Console tab is where you watch a server run. It streams the server's output as it happens, takes the commands you type, and shows live CPU, memory, disk and network use. The power buttons sit at the top of the server page, so you can start or stop the server from any tab.

• The server must have finished installing. The console is not available while the server's status is installing, install_failed, transferring or suspended.
• On a server someone shared with you, the owner must have given you the matching permissions: Console (or Command, which grants the same) to open the console and send commands, and Power to start, stop, restart and kill. Share a server with other users lists them.

1. In the dashboard, go to App Deployment and open the server.
2. At the top of the page, select the power action you need:
   • Start starts a stopped server.
   • Restart stops a running server and starts it again.
   • Stop shuts a running server down cleanly, so it saves its data first.

The page only offers the actions that fit the server's state: Start while it is stopped, Restart and Stop while it runs.

Kill ends the server process at once, without letting it save. Use it only when Stop does not work.

1. Open the server, then open More power actions (the button with three dots) at the top of the page.
2. Select Kill process….
3. Read the warning and select Kill process.

1. Open the server, then the Console tab.
2. Type the command in the box under the output, for example say Server restarts in 5 minutes.
3. Press Enter or select Send.

The server's reply appears in the output. While the console is not connected, the box reads Type a command. It still reaches the server. The output then shows > followed by your command.

• The status next to the server's name says whether the output is live: Connected, Connecting, Reconnecting, Paused in background or Disconnected. It reads Reconnecting to server process while the console waits on the machine that runs the server, and Not available. Trying again. while it cannot connect and keeps trying. Select Reconnect whenever it is not connected.
• When you leave the tab in the background, the console pauses and reconnects when you come back.
• The output keeps the last 2,000 lines.
• The Live stats card shows CPU, Memory and Disk against the plan's limits, Network in, Network out and Uptime.
• For Minecraft servers, the card and the bar above the output also show Players, Version and Online now when the game answers the server list ping.

The status badge at the top of the page changes as the server starts or stops, and a message confirms each action, such as Starting the server. The output shows the server's own messages as it boots, and commands you send appear with their replies.

Console unavailable

The server is installing, being moved, suspended, or its install failed. The page says which. The console opens again when the server is ready. For a failed install, see Troubleshoot servers.

Access denied. You need console permission.

The owner has not given you the Console permission on this server. Ask them to add it on the Users tab.

Connection limit reached. Close other console sessions first.

Your account has 8 consoles open on this server, or 32 across all servers. Close console tabs you are not using.

Session expired. Please sign in again.

Your session ended. Sign in again, then reopen the console.

Cannot reach the host this server runs on

The console could not reach the machine that runs the server. It keeps trying. If it stays disconnected, contact support.

Cannot send power actions while server is suspended

A suspended server cannot start. Its owner can select Open Billing on the banner to open the server's Billing tab. You can also contact support.

This server's deployment is paused by its spend limit. Raise or remove the limit to start it

The deployment reached a budget set to Pause, which stopped its servers. Until the budget lets go, a server can be stopped but not started or restarted. Its owner can raise or remove the budget under Budget on the deployment's Billing tab, and the servers it stopped then start again, as they do when the month turns (Set a budget).

This server is locked

We locked the server during an abuse review. It can be stopped but not started. Select Open review ticket to reply to the ticket.

world_optimization_running

We are removing unused chunks from the world, and the server cannot start until that finishes. Try again after the number of seconds in retry_after_seconds.

A file import is running on this server. Start it again when the import finishes.

The server has an import that is queued, copying or stopping, so Start and Restart are refused (409 through the API). The same goes for a start from a schedule or a rule. Stop and Kill still work. Wait until the import is Completed, Failed or Cancelled, or stop the import first, then start the server.

rate_limited

You sent more than 24 power actions to this server in 60 seconds. Wait for the number of seconds in the Retry-After header.

• Server settings shows the startup command the server runs, under Advanced.
• Schedule server tasks sends commands and power actions on a timer.
• Server limits and rate limits lists every limit on this page.

Send a power action with POST /api/v1/client/servers/{uuid}/power. The body's signal is start, stop, restart or kill.

curl -X POST https://api.coritan.com/api/v1/client/servers/$SERVER/power \
  -H "Authorization: Bearer $CORITAN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"signal": "restart"}'

The response is {"message": "Power action 'restart' sent"}. It confirms that the signal was sent, so read the server's state afterwards to see the result.

Send a console command with POST /api/v1/client/servers/{uuid}/command. The command goes in the command query parameter, URL-encoded, at most 1,000 characters.

curl -X POST "https://api.coritan.com/api/v1/client/servers/$SERVER/command?command=say%20Hello" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

A server that is not running answers 409 with The server is not running. Start it, then send the command again. A 200 means the server received the command. To see what it did, read the console.

Read the newest console lines with GET /api/v1/client/servers/{uuid}/console. lines takes 1 to 200 (100 by default). The response is {"lines": [...]}, oldest first, without colour codes. It works for every game, including Bedrock, which has no logs/latest.log.

curl "https://api.coritan.com/api/v1/client/servers/$SERVER/console?lines=20" \
  -H "Authorization: Bearer $CORITAN_TOKEN"

GET /api/v1/client/servers/{uuid}/resources returns the server's state (such as running, starting, stopping or offline), is_suspended, and utilization, which holds cpu_absolute, memory_bytes, memory_limit_bytes, disk_bytes, network.rx_bytes, network.tx_bytes and uptime in milliseconds.

GET /api/v1/client/servers/{uuid}/status-ping asks a Minecraft server who is online. When reachable is true, the response carries players_online, players_max, sample (some player names), version, motd and latency_ms. When the game does not answer (stopped, still booting, or not Minecraft), reachable is false and the other fields are empty.

To stream the output, open the console socket with your access token in the token query parameter. The socket signs you in with that token.

wss://api.coritan.com/ws/console/<server uuid>?token=<access token>

GET /api/v1/client/servers/{uuid}/websocket used to return this address. It is deprecated and may stop answering after 31 March 2027, so connect to the address above instead.

Messages are JSON objects with an event and args. Send {"event": "send logs", "args": []} for the recent output, {"event": "send command", "args": ["say Hello"]} to run a command, and {"event": "set state", "args": ["restart"]} for a power action. The socket sends console output, status and stats events as the server runs.