Actions32
- Automatic Power Control Actions
- Dedicated Server Actions
- DNS Secondary Actions
- Network Boot Actions
- Network Diagnostic Actions
- Remote Access Control Actions
- Reset Actions
- Reverse DN Actions
- Security Scan Actions
Automatic Power Control → Abort Reboot
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage various server-related operations, including Automatic Power Control (APC) functions such as aborting a reboot. Specifically, the "Abort Reboot" operation under the "Automatic Power Control" resource allows users to cancel an ongoing APC reboot process on a dedicated server identified by its IP address and a reboot ID.
Common scenarios for this node include:
- Managing power cycles of dedicated servers remotely.
- Aborting unintended or problematic reboots initiated via the API.
- Integrating server power control into automated workflows for maintenance or incident response.
Practical example:
- If a reboot was requested but needs to be stopped due to detected issues, this node can abort that reboot by specifying the server IP and the reboot ID.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server on which the APC reboot is being managed. |
| Reboot ID | The unique identifier of the APC reboot process to be aborted. |
| Response Format | The format in which the API response will be returned. Options: JSON, XML. |
Output
The node outputs the API response in the specified format (JSON or XML). When the response format is JSON, the output is parsed into a JavaScript object under the json field. This typically contains details about the success or failure of the abort reboot request.
If the response format is XML, the raw XML string is provided in the json.data field as a string.
No binary data output is produced by this operation.
Example JSON output structure might look like:
{
"json": {
"status": "success",
"message": "Reboot aborted successfully"
}
}
or in case of error:
{
"json": {
"error": "Invalid reboot ID"
}
}
Dependencies
- Requires an API key credential for authenticating with the Ikoula Dedicated Server API.
- The node uses RSA public key encryption to encrypt the password before sending it to the API.
- The base URL for the API defaults to
https://api.ikoula.combut can be overridden in credentials. - No additional external dependencies are required beyond standard HTTP requests.
Troubleshooting
No credentials provided!
Error thrown if the API authentication credentials are missing. Ensure that valid API credentials are configured in n8n.Invalid Server IP or Reboot ID
The API may return errors if the server IP or reboot ID does not exist or is incorrect. Verify these inputs carefully.API Response Errors
The node returns the API's error messages in the output JSON. Common issues include authorization failures, invalid parameters, or network problems.Network Issues
Ensure that the n8n instance has network access to the Ikoula API endpoint.Response Format Mismatch
If XML format is selected, downstream nodes expecting JSON may fail. Choose the response format according to your workflow needs.
Links and References
- Ikoula Dedicated Server API Documentation (general reference; actual link may vary)
- n8n Documentation - Creating Custom Nodes
- RSA Public Key Encryption#Encryption)