Direct answer
A hosting panel makes common actions clickable: start, stop, console, file upload and scheduled backup. A Linux shell exposes more OS tools and automation, but also more ways to damage permissions or services.
Step-by-step procedure
- Locate the panel’s actual startup command, Java selection, environment variables, and working directory.
- Identify whether you can download world files, plugin data and database dumps independently of the panel.
- For SSH access, use a non-root service account; identify how the server starts (systemd, screen, tmux or a container) before changing anything.
- Test uploading a small config file and restarting in a staging instance; confirm the log reflects the edited file.
Common mistakes and trade-offs
Do not run a second Java process from SSH while the panel already runs the same server directory: simultaneous writes can corrupt data.
How to verify it worked
After a reboot, confirm the server starts once, can be stopped gracefully, and the correct Java binary and port are used.
Version and platform differences
Exact menus vary by hosting provider; command examples in Linux guides are not interchangeable with restricted panel consoles.
Official references
These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.