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
Remote Access Control → Request Access
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage remote access control among other server-related operations. Specifically, for the Remote Access Control - Request Access operation, it allows users to request a NAT (Network Address Translation) access for remote management of a dedicated server by specifying the server IP and the source IP address that should be granted access.
Common scenarios where this node is beneficial include:
- Automating the process of granting temporary or permanent remote access to dedicated servers.
- Integrating remote access requests into broader workflows for server maintenance or troubleshooting.
- Managing access permissions programmatically without manual intervention in the hosting provider’s control panel.
Practical example:
- A system administrator wants to allow a specific external IP address to remotely access a dedicated server for debugging purposes. Using this node, they can automate the request for remote access by providing the server's IP and the source IP to be allowed.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server on which to request remote access. |
| Source IP | The source IP address that will be granted Remote Access Control NAT access. |
| Response Format | The format of the API response returned by the node. Options: JSON, XML. |
Output
The node outputs the API response in the specified format (json or xml). When JSON is selected, the output is parsed into an object under the json field. This typically contains details about the success or failure of the remote access request, including any relevant metadata or error messages from the API.
If XML format is chosen, the raw XML string is returned as a string inside the json.data field.
No binary data output is produced by this operation.
Example JSON output structure (simplified):
{
"json": {
"status": "success",
"message": "Remote access granted",
"details": {
"serverIp": "123.45.67.89",
"ipSource": "98.76.54.32",
"accessExpires": "2024-07-01T12:00:00Z"
}
}
}
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 encrypt the password before sending it to the API.
- Network connectivity to the Ikoula API endpoint (
https://api.ikoula.comby default). - No additional environment variables are required beyond the API credentials.
Troubleshooting
No credentials provided!
Error thrown if the node is executed without proper API credentials configured. Ensure that the API authentication details are set up correctly in n8n credentials.API request failures
If the API returns errors (e.g., invalid IP addresses, unauthorized access), these will be included in the node output. Verify that the server IP and source IP are correct and that the API user has sufficient permissions.Incorrect response format
Selecting XML format returns raw XML as a string; ensure downstream nodes can handle this format or use JSON for easier parsing.Encryption issues
The password is encrypted using a hardcoded RSA public key. If the API changes its key or encryption method, the node may fail to authenticate.
Links and References
- Ikoula API Documentation (general reference for API endpoints and usage)
- n8n Documentation for general guidance on using API nodes and managing credentials