# Manage your Minecraft server

> Start, stop, restart, inspect status, and operate an AppLaunch Minecraft server safely.

The service **Overview** shows runtime status and resource information. Day-to-day tools are under **Server**.

## Start the server

Use **Start** after installation has completed. Follow **Server → Console** until the software reports that startup is complete. First startup can take longer while files and the world are generated.

## Stop cleanly

Use the dashboard **Stop** action or send the server's normal `stop` command in **Console**. Wait for shutdown to finish before replacing a world, changing server software, moving many files, or restoring a backup.

A forced interruption can leave world or plugin data inconsistent.

## Restart

Use **Restart** after a configuration change that requires it. Do not use repeated restarts as a fix for a crash loop; read the first error in **Console**, correct it, and then start again.

## Understand offline controls

When the hosting node is offline, actions requiring it are disabled. Existing backups may still be downloadable, but server power, file, database, port, and restore actions wait for the node to return.

## Safe routine maintenance

1. Tell players about the maintenance window.
2. Create a completed backup.
3. Stop the server cleanly.
4. Change one plugin, mod, configuration, world, or runtime setting.
5. Start and watch **Console**.
6. Join and test before opening the server to everyone.

Use [Console and commands](/minecraft/console-and-commands/) for live output, [Files and SFTP](/minecraft/files-and-sftp/) for content changes, and [Backups and restore](/minecraft/backups/) before risky work.