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 proxy hosts, access lists, certificates, and more. Specifically, the "Delete" operation on the "Proxy Host" resource enables users to remove a configured proxy host from their NPM setup. This is useful for cleaning up unused or obsolete proxy configurations, helping maintain an organized and efficient proxy environment.
Practical examples include:
- Removing a proxy host that is no longer needed after a service decommission.
- Cleaning up test proxy hosts created during development.
- Automating the removal of proxy hosts based on external triggers or workflows.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the proxy host to delete. This is required to specify which proxy host should be removed. |
Output
The node outputs a JSON array containing the result of the deletion operation. Typically, this will include a success indicator and possibly a message confirming the deletion. The exact structure depends on the response from the NPM API but generally confirms whether the proxy host was successfully deleted.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to an Nginx Proxy Manager instance.
- Needs credentials including the URL of the NPM instance, an email, and a password to authenticate and obtain an API token.
- The node performs an HTTP POST request to the
/api/tokensendpoint to retrieve an authentication token before executing operations. - Proper API permissions are necessary to delete proxy hosts.
Troubleshooting
- Login failed: No token received: This error indicates that authentication with the NPM instance failed. Verify that the provided URL, email, and password are correct and that the NPM instance is reachable.
- Invalid ID or Proxy Host not found: If the specified ID does not correspond to any existing proxy host, the deletion will fail. Ensure the ID is correct and that the proxy host exists.
- Network issues or API errors: Connectivity problems or API changes in NPM might cause failures. Check network connectivity and confirm compatibility with the NPM API version.
- Insufficient permissions: The API user must have rights to delete proxy hosts. Confirm the user's role and permissions within 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 managing credentials