A paid order and a ready Lightsail server are different stages. In Blesta, paid pending services are normally activated by Provision Paid Pending Services, or by staff when the package is held for manual activation. The Lightsail setup then needs to finish before the customer can use its server controls.

Check activation first

1. Open the affected service and check its payment and pending/active state.
2. Confirm whether the package holds paid services for manual activation. If so, follow your agreed staff activation process.
3. If activation should be automatic, check that Blesta’s normal cron and Provision Paid Pending Services task are running.
4. Review the package under Packages → Packages. Confirm PD AWS Lightsail, the intended AWS account, region, platform, plan and blueprint.

Do not assume that editing package defaults has already activated an older pending service. The package creation guide covers the initial offering setup.

Distinguish activation from finishing steps

Open PD Modules → PD AWS Lightsail → Clients & Services and Activity. Read the service’s operation state. Static-IP attachment and extra-storage work may still be finishing after the main instance request.

For a reported provider error, check the AWS account under Settings → Company → Modules → PD AWS Lightsail → Manage, then use Test Connection in the module’s Settings. Check the permission or capacity issue identified by the failing operation; a successful connection check does not establish every provisioning permission.

Compare the service with the instance in AWS

You run the Blesta installation and AWS account for your hosting business. Check the Lightsail region selected for this package using your own AWS access, and compare the instance state with the operation shown for your customer’s service.

• The service is still pending and activation has not run: complete the payment, manual-activation or scheduled-task check above. Changing a package does not itself activate that service.
• An instance exists and setup is still running: let the current operation finish. Check the recorded result of any static-IP or extra-storage step before attempting activation again.
• An instance exists but Blesta reports a failure: note the instance state and the failed module operation. Include that mismatch in a diagnostic report rather than placing another order for your customer.
• Creation failed and no instance exists: use the actual error to check the named AWS permission, package selection or capacity requirement. Correct the identified cause before attempting activation again.
• The result is unclear: record what the module shows and what you can see in the selected AWS region. A report should explain this uncertainty instead of assuming that nothing was created.

Once setup completes, confirm that the intended instance is Running and that the connection details shown for your customer’s service match it. Check the application separately if your package includes one.

See the PD AWS Lightsail Blesta guide for related tasks, or explore the module.

Clients who need help with an unexplained module result can follow our reporting guide (client sign-in required).