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, proxy hosts, certificates, and more. Specifically, for the Download Certificate operation under the Certificate resource, the node enables downloading a certificate by its ID from the NPM server.
Common scenarios include automating certificate management workflows, such as retrieving SSL/TLS certificates for backup, inspection, or deployment purposes. For example, a user might automate the download of updated certificates to distribute them across multiple servers or services.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the certificate to download. This is required to specify which certificate to retrieve from the NPM instance. |
Output
The output contains a JSON array where each item corresponds to the result of the executed operation. For the Download Certificate operation, the json field will include the certificate data retrieved from the NPM API. This typically includes certificate details such as the certificate content, private key, and metadata.
If the certificate includes binary data (e.g., the actual certificate file), it may be returned in encoded form within the JSON or as binary data attached to the output, depending on implementation specifics not fully visible here.
Dependencies
- Requires an active connection to an Nginx Proxy Manager instance.
- Needs credentials including:
- The base URL of the NPM API.
- An email and password for authentication to obtain an API token.
- The node performs an initial login request to
/api/tokensto get an authentication token before executing operations. - Proper API permissions are necessary to access certificate data.
Troubleshooting
- Login failed: No token received: This error occurs if the authentication request does not return a valid token. Check that the provided credentials (email and password) are correct and that the NPM API endpoint is reachable.
- Invalid certificate ID: If the specified certificate ID does not exist or is incorrect, the API may return an error or empty response. Verify the ID before running the node.
- Network issues: Ensure the NPM server URL is accessible from the n8n environment and that no firewall or network restrictions block the requests.
- Permission errors: The authenticated user must have sufficient rights to read certificate information.
Links and References
- Nginx Proxy Manager GitHub Repository
- Nginx Proxy Manager API Documentation (if available)
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)