Give customers control over planned server downtime through PD AWS Lightsail. They can start a stopped server, stop a running server or reboot it from their service page when your offering enables the corresponding action.

Before using a power action

Check that the customer is viewing the correct service and server. Arrange downtime before stopping or rebooting a server that hosts a live website, database or application, and save work that is still in progress.

As the hosting company, enable the actions included in your offering through Client: Start, Client: Stop and Client: Reboot. These are separate controls. See customer-control settings for the configuration steps.

Start a stopped server

1. Open the Lightsail service in the WHMCS client area and select Overview.
2. Check the displayed server state, then choose Start for the intended stopped server.
3. Wait for the operation to complete and the server state to become Running. Check Activity for its progress.
4. Connect to the server and check the application you expect it to run. A running server does not by itself confirm that a website or database has started successfully.

Stop a server for planned downtime

1. On the same service page, choose Stop.
2. Read the confirmation that the server will go offline until it is started again. Confirm when the customer is ready for that downtime.
3. Wait for the server state to show that it has stopped, and check Activity for the result.

Stopping a server is a power action. It does not cancel the customer's billing service or remove the server. When the maintenance window ends, use Start and check the application again.

Reboot a running server

1. Choose Reboot on the service page.
2. Review and confirm the reboot request.
3. Allow the server time to restart. Check Activity, then reconnect and verify the customer's application.

Use reboot when a restart is intended, such as after a planned operating-system change. It does not reinstall the operating system or restore a snapshot.

Check the result before repeating an action

The controls depend on both the permissions you offer and the server's current state. If an action is unavailable, check those two things first. If an operation is already progressing, follow its result instead of repeatedly pressing the button.

After a stop/start cycle, review the service's connection details before reconnecting or checking DNS. A service using a static IP keeps that fixed address; do not assume a service without one still has its previous public address.