# Console, power and troubleshooting

> Run commands, understand server states and recover from common Terraria errors.

## Console and power

Open **Server → Console** to read runtime output and send server commands. Useful Terraria commands include `help`, `playing`, `say Hello`, `save`, `kick PlayerName` and `exit`. Commands available in mods may differ. Do not use Minecraft commands such as `op` or `whitelist` expecting Terraria behavior.

**Start** launches installed software. **Stop** requests a save and graceful shutdown. **Restart** stops and starts it. **Force stop** is a last resort for a stuck runtime and may lose unsaved progress.

## Common issues

- **Provisioning or installation:** wait for the current task; controls unlock when it finishes.
- **Cannot join:** check that the console reports a listening server, then check the hostname, displayed port, password and exact client version. Disable Cloudflare's proxy for a custom game hostname.
- **Version mismatch:** Vanilla and tModLoader are separate runtimes. Install the matching client/server version.
- **World is missing:** stop and check `Worlds`, the selected world name and `.wld` filename. A modded world also needs its `.twld` and mods.
- **Mod load failure:** review missing dependencies and supported tModLoader release. Restore a known-good backup if needed.
- **Node offline:** node-dependent actions remain unavailable. Contact support rather than repeatedly queuing actions.
- **Task failed:** retain its task ID and error when opening a support ticket. Staff can inspect AppLaunch operational error logs and resolve the logged issue after a verified fix.

The development node may use a different CPU architecture from future production nodes. Do not infer production performance from development tests.