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 NPM resources programmatically. Specifically, for the Redirection Host resource and the Delete operation, it enables deleting a redirection host entry from the NPM configuration. This is useful in scenarios where you want to automate cleanup or removal of URL redirections managed by NPM.
Practical examples include:
- Automatically removing obsolete or invalid redirection hosts as part of a deployment pipeline.
- Cleaning up test or temporary redirection entries after testing phases.
- Managing redirection hosts dynamically based on external triggers or events.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the redirection host to delete. This property is required to specify which redirection host entry should be removed. |
Output
The node outputs a JSON array containing the result of the deletion operation. Typically, this will include confirmation of success or failure and may contain messages related to the operation status.
If the node supports binary data output, it is not indicated here; thus, the output is purely JSON-based reflecting the API response.
Dependencies
- Requires an active connection to an Nginx Proxy Manager instance.
- Needs credentials including the NPM instance URL, an email, and a password to authenticate and obtain an access token.
- The node internally performs an authentication request to
/api/tokensendpoint to retrieve a token before executing operations. - No additional external dependencies beyond the NPM API and proper credential configuration in n8n.
Troubleshooting
- Login failed: No token received: This error indicates that authentication to the NPM API failed. Verify that the provided credentials (email, password, and URL) are correct and that the NPM instance is reachable.
- Invalid ID or resource not found: If the specified redirection host ID does not exist, the API may return an error. Ensure the ID corresponds to an existing redirection host.
- Network issues: Connectivity problems between n8n and the NPM instance can cause failures. Check network settings and firewall rules.
- Permission errors: The user associated with the credentials must have sufficient permissions to delete redirection hosts.
Links and References
- Nginx Proxy Manager GitHub Repository
- Nginx Proxy Manager API Documentation (if available)
- n8n Documentation for general node usage and credential setup guidance