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 Dead Host resource with the Get operation, it retrieves details about a specific dead host by its ID. This is useful in scenarios where administrators want to monitor or audit hosts that are no longer active or reachable through the proxy manager.
Practical examples include:
- Fetching detailed information about a dead host to investigate why it became unreachable.
- Integrating with monitoring workflows to alert when certain hosts become dead.
- Automating cleanup or reporting tasks based on dead host data.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the dead host to retrieve. |
| Additional Fields | Optional parameters to customize the response: |
| - Expand Owner | Boolean flag to include detailed owner information in the response. |
| - Expand Certificate | Boolean flag to include detailed certificate information related to the dead host. |
| - Filter | A string filter to narrow down results by name (used mainly in list operations). |
Output
The node outputs JSON data representing the dead host's details. This includes all standard properties of the dead host and optionally expanded owner and certificate information if requested.
The output structure typically contains fields such as:
- Dead host ID
- Hostname or domain
- Status and metadata
- Owner details (if expanded)
- Certificate details (if expanded)
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Nginx Proxy Manager instance.
- The node performs an initial login request to obtain a token before making further API calls.
- The base URL and authentication credentials (email and password) must be configured in the node's credentials.
Troubleshooting
- Login failed: No token received: This error indicates that authentication with the NPM API failed. Verify that the provided email, password, and URL are correct and that the NPM instance is accessible.
- Invalid ID or resource not found: If the specified dead host ID does not exist, the API may return an error or empty result. Confirm the ID is valid.
- Network issues: Ensure the NPM server is reachable from the n8n environment.
- Permission errors: The API user must have sufficient permissions to access dead host data.
Links and References
- Nginx Proxy Manager Official Documentation
- Nginx Proxy Manager API Reference (community) (for understanding available endpoints and data structures)