Power Cycle

  • Posted June 6, 2013

When I click on the name of my droplet, it displays several different icons, such as Power, Access, Resize, Snapshots, Backups etc.

Under the Power tab, which is open by default, there is another tab Power Cycle, which, as shown below, says “This will reboot your droplet” and then it provides more info about how they recommend that it be done through the command line.


  1. Is this something I’m supposed to do at the beginning after creating a droplet? or is it something do during management of the server (for whatever reason if need arises)

  2. Since it’s recommended to do it through the command line, how do I do that?

I’m using ‘Ubuntu 12.10 x32 Server’

Power CyclePower Off This will reboot your droplet.

We recommend rebooting your droplet through the command line, as this action is the same as hard resetting the server and may cause data corruption.

Do you wish to proceed?


This comment has been deleted

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hello, all

In order to reboot the droplet using the command line you can use these two options:

  1. sudo reboot


  1. sudo shutdown -r now

They basically do the exact same thing so using any of them will complete the task.

Generally speaking, the shutdown command is preferable because you have the option to specify the reason for the system reboot, e.g maintenance. An additional feature is that you can schedule when the system needs to be powered down.

  1. sudo shutdown -r now 'System maintenance'

Hope that this helps!

I have a perhaps related problem. I used a third-party Android app to ‘power cycle’ a droplet that had a SQL crash on one of the websites. It seemed to work fine. That was last week. All the sites are showing fine, but today I checked and the droplet says it is OFF! How is this possible?


After I power off my droplet, how can I turn it on again?


@cjrajeev: You can reboot a droplet by running the <code>sudo reboot</code> command as root. <br> <br>If you want to power it off, you have to run <code>sudo shutdown -h now</code> or <code>sudo poweroff</code>.

Dear Sir, <br>“We recommend rebooting your droplet through the command line, as this action is the same as hard resetting the server and may cause data corruption…” <br> <br>I am a new user. I created droplet with Ubuntu, and installed zPanel, my website started working now/ I want resize my server to next level. I saw one option to resize using snapshot method. But I don’t want to lose my IP (even in accidently), so i want to power off the droplet and resize it in a safeway. I read in CP saw above quoted recommendation. But I couldn’t see any concrete instruction for how to re-boot from command line, How to Power off etc. I can see some API Commands in Control Panel but struggling to know how to use it. <br> <br>Please Help…

Thanks to DO support, I found out that to power off the droplet from the command line I can use the “poweroff” command (also “shutdown -h now” works). The “halt” command will not actually power off the droplet.

Sorry, I meant I have the same problem as simon.waddington.

I’m having the same problem as LazyTiger. I have to Power Off my droplet in order for DO control panel to recognize it as Off. I created a support ticket.

@simon.waddington: I haven’t seen that happening before – are you able to reproduce it on a fresh new Ubuntu 13.04 64-bit droplet?

Same question - I don’t want to reboot I want to shutdown. I used ‘shutdown now’ from the commandline which is what I’ve always used and I get logged out from the shell but the console says the machine goes to single user maintenance mode (or waiting to enter it) and remains active. Is that something peculiar about your standard Ubuntu 13.04 (64-bit) image? Every other machine I’ve used, virtual or not, really shuts down after ‘shutdown’… <br> <br>The same behavior applies to ‘halt’ (except there is no “maintenance mode” prompt). <br> <br>I guess I could take it to single user and then trigger power off from the console but shouldn’t I be able to do it just from the command line?
<br> <br>Or is there actually really no difference between “Power off” state and a machine that is active but halted?