Actions38
- Access List Actions
- Certificate Actions
- Dead Host Actions
- Log Actions
- Proxy Host Actions
- Redirection Host Actions
- Setting Actions
- User Actions
Overview
This node integrates with an Nginx Proxy Manager (NPM) instance, allowing users to manage various resources such as access lists, certificates, proxy hosts, and more. Specifically, for the Access List - Delete operation, it enables the removal of a specified access list entry by its ID. This is useful in scenarios where you want to revoke or clean up access permissions managed through NPM.
Practical examples include:
- Automatically deleting outdated or unused access lists as part of a cleanup workflow.
- Removing access restrictions dynamically based on external triggers or events.
- Managing access control programmatically without manual intervention in the NPM UI.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the access list entry to delete. This property is required for the delete operation. |
Output
The output of this node operation will be a JSON array containing the result of the deletion request. Typically, it will confirm whether the deletion was successful or provide relevant status information from the NPM API.
No binary data output is expected for this operation.
Dependencies
- Requires an active connection to an Nginx Proxy Manager instance.
- Needs credentials including the URL, email, and password to authenticate and obtain an API token.
- The node performs an HTTP POST request to
/api/tokensto retrieve an authentication token before executing resource-specific operations. - Proper API access rights are necessary to perform delete operations on access lists.
Troubleshooting
- Login failed: No token received: This error indicates that authentication with the NPM API failed. Verify that the provided URL, email, and password credentials are correct and that the NPM instance is reachable.
- Invalid ID or resource not found: If the specified access list ID does not exist, the API may return an error or no effect. Ensure the ID is valid and corresponds to an existing access list entry.
- Network issues: Connectivity problems between n8n and the NPM server can cause request failures. Check network settings and firewall rules.
- Insufficient permissions: The user credentials must have permission to delete access lists. Confirm the account's role and privileges in NPM.
Links and References
- Nginx Proxy Manager GitHub Repository
- Nginx Proxy Manager API Documentation (if available)
- n8n Documentation for general guidance on using HTTP Request nodes and credential management