According to the latest FAQ’s it should be “shutdown -h now” and not “sudo shutdown -h now.
See: https://www.digitalocean.com/help/technical/product/
My question is, does it matter if you use "sudo shutdown -h” now?
I did this command with the “sudo” and concerned that it may cause issues with my droplet.
sudo just means ‘become root’ to run the command. The behaviour will not change
The power on button only shows up if the droplet has been powered down:
Nearly 2 years later, this still happens.
I had powered off in ssh, but on the snapshot page there was no button to start the snapshot process. Without that button, the text there seems to mean that by powering off (as I had done) a snapshot was already, automatically, being created. That didn’t really make sense, so I searched and found this question page.
Request to DO:
on the Snapshot page, please add this information :
After powering off from within the droplet (sudo shutdown -h now or systemctl poweroff), we have to go to the Power page and power it off there too. (That doesn’t do anything to the droplet in this situation, but it gets the web interface in sync.) Then go back to the Snapshot page and the “Take Snapshot” button will be there.
Can confirm that after powering off with sudo poweroff from the command line the server successfully powered off and the web UI was in sync, ie. It now has a “Power On” option. Looks like the good people at digitalocean fixed the problem now.
These things are working in today’s time. shutdown syncs with status on the dashboard and power on button is available.
I used sudo poweroff in terminal, got locked out of SSH, and still had to power off from the web UI. After I powered off from the web UI and took a snapshot, my droplet powered on as soon as the snapshot finished (without me clicking “power on”) and my SSH access was reestablished.
I don’t think the problem is completely fixed. I had to request console access from the Web UI for it to recognize that I powered off from terminal.
The “poweroff” command worked perfectly for me when I used it after logging in as ROOT (so no need for sudo). When I went back to web interface, the droplet had indeed been powered down.
I did sudo poweroff but the control panel never showed it being powered off until I clicked the power off button in the control panel
I use poweroff. But you can also use shutdown -h now