This guide shows you how to shut a VPS down from Virtualizor, the panel Noiz VPS clients use to manage their servers. Virtualizor gives you two very different ways to do it: a graceful shutdown that asks the operating system to close down properly, and a forced power off that cuts the virtual machine dead. They look almost identical in the panel and they are not remotely equivalent, so the important part of this guide is knowing which one to click.
The product is Virtualizor, not "Virtualizer". You will see the misspelling in older notes and forum posts, and it is the same panel.
Last reviewed: 27 July 2026, against the current Virtualizor release and its end-user panel. This guide is written for Noiz hosting and is kept current against Virtualizor. It complements, and does not replace, the official Virtualizor documentation linked below.
Official Documentation Reference
Prerequisites
- Your Virtualizor end-user panel URL and login details, which are in your Noiz VPS welcome email.
- An active Noiz VPS service.
- A way to start the server again afterwards. Once a VPS is off, SSH is gone with it, so the only way back on is the panel. See How to Start or Boot Your VPS in Virtualizor.
Graceful Shutdown Versus Forced Power Off
Understand the difference before you click anything.
- Stop is the graceful option. Virtualizor signals the operating system to shut itself down in an orderly way. Services are told to stop, open files are closed, buffered writes are flushed to disk, and the machine powers off when that is finished. This is the option you want almost every time.
- Power Off is the forced option. It removes power from the virtual machine immediately, with no warning to anything running inside it. It is the exact equivalent of pulling the plug out of the wall on a physical server.
A forced power off can corrupt data. Anything still sitting in memory or in a write buffer is lost, and a database, mail queue or filesystem journal caught mid-write can be left inconsistent. In practice that shows up later as a database table that will not open, a filesystem that needs a check on the next boot, or an application that starts but behaves oddly. Use Power Off only when the server has genuinely stopped responding and a graceful Stop has already been tried and failed.
Gracefully Shut Down a VPS in Virtualizor
- Log in to your Virtualizor end-user panel.
- From the left-hand menu, click List VPS.
- Hover over the row for the VPS you want to shut down. The row highlights. Click the Manage icon on that row.
- At the top right of the management page, click Stop.
The shutdown is not instant. The operating system has to stop each service in turn, and a busy database or mail server can take a while to close cleanly. Give it a minute or two. Virtualizor displays a confirmation message when the VPS has stopped, and the status indicator on List VPS turns red.
Force a Shutdown When the VPS Will Not Stop
If the graceful Stop does nothing, the operating system is usually too wedged to respond to the shutdown signal, commonly after it has run out of memory or a kernel-level fault. In that case use Power Off on the same management page.
Before you click it, wait long enough to be sure the graceful stop has really failed rather than simply being slow. A server that takes three minutes to shut down cleanly is normal; killing it at thirty seconds because nothing appeared to happen is how avoidable corruption gets caused.
After a forced power off, allow extra time on the next boot. The filesystem may run a consistency check, and databases may replay their journals before accepting connections. Do not force another power off part-way through that recovery, because interrupting a filesystem check is considerably worse than the original unclean shutdown.
Shut Down From the Command Line
If you can still reach the server over SSH, you can shut it down from inside. This is an orderly shutdown, the same in effect as the panel's Stop, because the request comes from the operating system itself.
- Connect to the VPS over SSH as
rootor a user withsudo. - Run:
poweroff
The connection drops as soon as the shutdown begins, which is expected and not an error. shutdown -h now and halt do the same job.
The important gotcha: a VPS shut down from the command line will not come back on its own. There is nothing left running inside it to start anything, and SSH is unreachable, so the machine can only be powered on from Virtualizor. If what you actually wanted was for the server to come back up, use reboot instead, or follow How to Reboot or Restart a VPS in Virtualizor.
Before You Shut Anything Down
- Everything on the VPS goes offline. Websites, mail, databases and any application on the server stop answering for the whole time it is powered off. If mail is hosted on the VPS, sending servers will queue and retry rather than deliver, and a long outage risks bounces.
- Take a backup or snapshot first if the shutdown is part of maintenance you might need to undo.
- Check you can get back in. Confirm you can log in to Virtualizor before you power the server off, not after.
- Shutting down does not pause billing. The VPS keeps its resources, its IP address and its invoice while it is off. If you are shutting down because you no longer need the service, cancel it from your Noiz client area instead.
Troubleshooting
Symptom: Stop was clicked and nothing happens. Give it a couple of minutes and refresh the page. If the status is still green, the operating system is not responding to the shutdown signal. Try once more, then fall back to Power Off.
Symptom: the VPS shows as offline but the website is still resolving. That is cached DNS or a caching proxy in front of the site, not the server. The origin is down.
Symptom: the VPS was shut down and now will not start. Check whether the service is suspended in your Noiz client area, since a suspended VPS will not stay powered on. If the service is in good standing and the VPS still will not boot, the operating system is likely failing during boot and needs console access to diagnose.
Symptom: after a forced power off, services do not come back. Give the boot longer than usual, because filesystem checks and database recovery run first. If a database still refuses to start, its tables may need repairing after the unclean shutdown.
Symptom: the server shut down without anyone asking it to. A poweroff, halt or shutdown -h issued inside the VPS, including one triggered by an automatic update or a script, powers the machine off permanently. It has to be started again from the panel.
Related Guides
- How to Start or Boot Your VPS in Virtualizor
- How to Reboot or Restart a VPS in Virtualizor
- How to Check Whether Your VPS Is Online or Offline in Virtualizor
Need a Hand?
If a VPS will not shut down, will not start again afterwards, or came back from a forced power off with damaged data, open a support ticket from your Noiz client area. The support team can check the host node, confirm the real power state and help recover a server that did not come back cleanly.
