Actions100
- Billing Actions
- DNS Actions
- Domain Actions
- Domain Forwarding Actions
- Domain WHOIS Actions
- Reach Actions
- VPS Actions
- VPS Actions Actions
- VPS Backups Actions
- VPS Data Centers Actions
- VPS Docker Manager Actions
- VPS Firewall Actions
- VPS Malware Scanner Actions
- VPS Post Install Scripts Actions
- VPS PTR Actions
- VPS Public Keys Actions
- VPS Snapshots Actions
- VPS Templates Actions
VPS → Start
AI-generatedOverview
This node interacts with the Hostinger API to manage VPS (Virtual Private Server) instances. Specifically, the 'Start' operation sends a request to start a specified VPS by its Virtual Machine ID. This is useful for automating the control of VPS instances, such as starting a server after maintenance or scaling operations.
Use Case Examples
- Starting a VPS instance by providing its Virtual Machine ID to automate server management workflows.
- Integrating VPS start operations into a larger automation pipeline for cloud infrastructure management.
Properties
| Name | Meaning |
|---|---|
| Virtual Machine ID | The unique identifier of the VPS to be started. This is a required string input. |
Output
JSON
response- The JSON response from the Hostinger API after attempting to start the VPS, containing details about the operation's success or failure.
Dependencies
- Hostinger API authentication credential required for API access.
Troubleshooting
- Ensure the Virtual Machine ID is correct and the VPS exists; otherwise, the API will return an error.
- Check that the Hostinger API credentials are valid and have the necessary permissions to start VPS instances.
- Network issues or API endpoint changes may cause request failures; verify connectivity and API documentation if errors occur.
Links
- Hostinger API VPS Start Documentation - Official documentation for the VPS start operation in the Hostinger API.