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 → Stop
AI-generatedOverview
This node interacts with the Hostinger API to manage VPS (Virtual Private Server) resources. Specifically, for the 'Stop' operation under the 'VPS' resource, it sends a POST request to stop a specified virtual machine by its ID. This is useful for scenarios where you need to programmatically control the power state of your VPS, such as stopping a server to save costs or perform maintenance.
Use Case Examples
- Stopping a VPS before performing system updates to ensure no active processes interfere.
- Automating VPS shutdowns during off-hours to reduce operational costs.
Properties
| Name | Meaning |
|---|---|
| Virtual Machine ID | The unique identifier of the VPS to be stopped. This is a required string input. |
Output
JSON
response- The JSON response from the Hostinger API after attempting to stop the VPS, containing details about the operation's success or failure.
Dependencies
- Hostinger API authentication credential required to authorize API requests.
Troubleshooting
- Ensure the Virtual Machine ID is correct and corresponds to an existing VPS in your Hostinger account.
- Check that the API credentials are valid and have sufficient permissions to stop VPS instances.
- Common errors include authentication failures, invalid VM IDs, or network issues. Verify API endpoint accessibility and credentials.
Links
- Hostinger VPS API Documentation - Official documentation for stopping a VPS using the Hostinger API.