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
Network Diagnostic → Abort Diagnostic
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage network diagnostics among other server-related operations. Specifically, the "Abort Diagnostic" operation under the "Network Diagnostic" resource allows users to abort an ongoing network diagnostic process on a specified dedicated server.
Common scenarios for this node include:
- Managing and monitoring network diagnostics on dedicated servers.
- Aborting a network diagnostic that is no longer needed or was started by mistake.
- Integrating server network diagnostic controls into automated workflows.
Practical example:
- A user initiates a network diagnostic on a server to check connectivity issues but realizes the test is taking too long or is no longer necessary. Using this node's "Abort Diagnostic" operation, they can programmatically cancel the diagnostic process without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server on which the network diagnostic is running. |
| Netdiag ID | The unique identifier of the network diagnostic to be aborted. |
| Response Format | The format in which the API response should be returned. Options: JSON, XML. |
Output
The node outputs the API response in the selected 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 confirmation of the abort action or details about the diagnostic status after the abort request.
If the response format is XML, the raw XML string is provided as a string inside the json.data field.
No binary data output is produced by this operation.
Example JSON output structure might look like:
{
"json": {
"status": "success",
"message": "Network diagnostic aborted successfully"
}
}
Dependencies
- Requires valid credentials for the Ikoula API, including email, password, and optionally a custom API URL.
- The node uses RSA public key encryption to securely transmit the password.
- The API endpoint defaults to
https://api.ikoula.comunless overridden in credentials. - No additional external dependencies beyond standard HTTP requests and cryptography libraries bundled with n8n.
Troubleshooting
No credentials provided!
Error thrown if the node is executed without proper API credentials configured. Ensure that the required API authentication token or credentials are set up correctly in n8n.Invalid Server IP or Netdiag ID
If the server IP or diagnostic ID is incorrect or does not exist, the API will likely return an error. Verify these inputs before execution.API Response Errors
The API may return errors related to permissions, invalid states (e.g., trying to abort a diagnostic that is not running), or rate limits. Check the API response message for details.Response Format Issues
Selecting XML format returns raw XML strings; ensure downstream nodes can handle XML if chosen.
Links and References
- Ikoula API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding how HTTP calls are made within n8n nodes.