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 → Request Reboot
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage various server-related operations. Specifically, for the Automatic Power Control resource and the Request Reboot operation, it allows users to request a reboot of a dedicated server's Automatic Power Control (APC) system. This is useful in scenarios where remote power cycling of servers is needed, such as recovering from unresponsive states or applying certain hardware-level changes.
Practical examples include:
- Remotely rebooting a server after a failed software update.
- Scheduling a reboot with an optional tempo parameter to delay or time the reboot.
- Integrating server power control into automated workflows for maintenance or incident response.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server on which the APC reboot will be requested. |
| Tempo | Optional parameter to specify timing or delay for the APC reboot action. |
| Response Format | The format of the API response; options are JSON or XML. |
Output
The node outputs the API response in the selected format (JSON or XML). When JSON is selected, the output is parsed into a JavaScript object under the json field. The structure depends on the API's response but generally includes details about the reboot request status or confirmation.
If XML is selected, the raw XML string is returned inside the json.data field as a string.
No binary data output is produced by this node.
Example JSON output snippet (conceptual):
{
"json": {
"rebootId": "12345",
"status": "requested",
"message": "Reboot request accepted"
}
}
Dependencies
- Requires an API key credential for authentication with the Ikoula API.
- The node uses RSA public key encryption to encrypt the password before sending requests.
- The base URL defaults to
https://api.ikoula.combut can be overridden via credentials. - HTTP requests are made using standard REST methods (GET, POST, DELETE).
- No additional external libraries beyond those bundled with n8n are required.
Troubleshooting
No credentials provided!
Error thrown if the API credentials are missing or not configured properly. Ensure that the API key credential is set up in n8n.Invalid Server IP
If the server IP is incorrect or unreachable, the API may return errors or fail to process the reboot request. Verify the IP address is correct and accessible.API Response Errors
The API might return error messages related to invalid parameters, unauthorized access, or server issues. Check the response message for details.Encryption Issues
Password encryption uses a fixed RSA public key. If the API changes its key or encryption method, the node will need updating.Response Format Mismatch
Selecting XML format returns raw XML strings, which may require parsing downstream. Choose JSON for easier integration unless XML is specifically needed.
Links and References
- Ikoula API Documentation (general reference for API endpoints and usage)
- n8n HTTP Request Node Documentation (for understanding HTTP request handling)
This summary focuses on the Automatic Power Control resource and the Request Reboot operation as requested.