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, the "Proxy Host" resource with the "Get" operation retrieves detailed information about a single proxy host by its ID. This is useful for scenarios where you want to fetch configuration or status details of a specific proxy host managed by NPM, such as verifying settings, monitoring, or automating audits.
Practical examples include:
- Fetching the configuration of a proxy host before updating it.
- Retrieving expanded details like owner, access list, or certificate associated with the proxy host.
- Filtering proxy hosts by name when querying multiple entries (though filtering applies more to bulk operations).
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the proxy host to retrieve. Required for fetching a specific proxy host. |
| Additional Fields | Optional extra parameters to customize the returned data: |
| - Expand Owner | Boolean flag to include detailed information about the owner of the proxy host. |
| - Expand Access List | Boolean flag to include detailed information about the access list associated with the proxy host. |
| - Expand Certificate | Boolean flag to include detailed information about the SSL certificate linked to the proxy host. |
| - Filter | A string to filter results by the proxy host's name (more relevant for bulk retrieval). |
Output
The node outputs JSON data representing the requested proxy host's details. Depending on the selected additional fields, this JSON may include nested objects for the owner, access list, and certificate information, providing a comprehensive view of the proxy host configuration.
If binary data were involved (not indicated here), it would typically represent files or certificates, but this node focuses on JSON metadata output.
Dependencies
- Requires an active connection to an Nginx Proxy Manager instance.
- Needs credentials including URL, email, and password to authenticate and obtain an API token.
- The node uses the NPM API token for subsequent requests.
- No other external services are required.
Troubleshooting
- Login failed: No token received: Indicates authentication failure. Verify that the provided URL, email, and password credentials are correct and that the NPM instance is reachable.
- Invalid ID or resource not found: Ensure the proxy host ID exists in the NPM instance.
- Network errors or timeouts: Check network connectivity to the NPM server and ensure the API endpoint is accessible.
- If expansions (owner, access list, certificate) return empty or incomplete data, verify that these related entities exist and are properly linked in NPM.
Links and References
- Nginx Proxy Manager GitHub
- Nginx Proxy Manager API Documentation (if available)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls