Overview

The ALYPOD Console lets you start, stop, reboot and force-off a Pod at any time. Doing it correctly protects your data and filesystem. This article explains each action and when to use it.

Power actions

• Start: powers on a stopped Pod and boots the OS.
• Shut down (Stop): sends an ACPI/graceful signal so the OS closes services and flushes data. Use this whenever possible.
• Reboot: graceful restart, equivalent to reboot inside the OS.
• Force stop / Force off: cuts power immediately. Use only when the Pod is unresponsive — repeated force-offs risk filesystem corruption.

Steps

1. Sign in to account.alypod.com and open the ALYPOD Console.
2. Select your Pod and open the Overview tab.
3. Use the power buttons in the top toolbar:

• Start to boot a stopped Pod.
• Shut down for a clean stop before maintenance.
• Reboot to restart.
• Force stop as a last resort.

1. Confirm any warning dialogue and watch the status indicator change.

Preferred: shut down from inside the OS

If you still have shell access, graceful actions from within the guest are safest:

```bash

Linux

sudo systemctl poweroff # shut down sudo systemctl reboot # reboot ```

```powershell

Windows

shutdown /s /t 0 # shut down shutdown /r /t 0 # reboot ```

When to power off

• Before resizing CPU/RAM or attaching an ISO.
• Before a manual filesystem check.
• To save cost on a Pod you are not using (check whether stopped Pods are still billed — storage usually remains chargeable).

Troubleshooting

• Problem: Pod will not power off. Solution: try Shut down again, then fall back to Force stop and run fsck afterwards if needed.
• Problem: Pod stuck on boot. Solution: open the VNC console to see where it stops, or boot rescue mode to repair.
• Problem: services down after a reboot. Solution: check that they are enabled with systemctl is-enabled <service>.

Related articles

• [Using the web console and VNC]
• [Resizing a Pod (upgrading resources)]
• [Accessing rescue mode]