The panel works in a phone browser, and that matters more than it sounds: most emergencies happen when you are not at a computer. Knowing in advance which jobs are practical from a phone decides whether an evening is saved or lost.
From a phone
| Task | Practical? |
|---|---|
| Restarting a crashed server | Yes. One button, and the most common need. |
| Reading the console | Yes, if you can scroll. This answers most questions. |
| Running a command | Yes. Kicking, banning, save-all are all one line. |
| Small config edits | Possible, but a typo in YAML on a touch keyboard is easy. |
| Uploading a plugin | Awkward. Wait until you are at a computer. |
| Restoring a backup | Technically yes. Do not, unless it is genuinely urgent. |
Setting yourself up before you need it
- Log in on your phone once, now
Doing it for the first time during an incident, with two-factor and a password manager involved, is the worst possible moment.
- Bookmark the console page directly
Not the panel home. Two taps saved matters when you are on a bus.
- Add a trusted subuser with console access
Someone else who can restart it is worth more than any monitoring you set up for yourself.
- Set up a restart schedule
The best phone management is the incident that resolved itself before you saw it.
YAML is whitespace-sensitive and touch keyboards insert autocorrections. An edit that looks fine on a small screen can stop the server from starting, and then you are at a bus stop with a server that will not boot rather than one that just needed a restart.
Reading the console tells you whether this is «restart it» or «this needs a computer». That single judgement, made in thirty seconds from anywhere, is most of the value.