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 Certificate resource and the Create (Using Custom) operation, it enables creating SSL/TLS certificates by specifying domain names. This is useful for automating certificate management tasks such as provisioning certificates for multiple domains in bulk or integrating certificate creation into deployment pipelines.
Practical examples include:
- Automatically generating certificates for newly deployed web applications.
- Managing SSL certificates across multiple domains without manual intervention.
- Integrating certificate creation into CI/CD workflows to ensure secure HTTPS setups.
Properties
| Name | Meaning |
|---|---|
| Domain Names | A collection of one or more domain names for which the certificate will be created. Each domain must be specified individually. |
The property "Domain Names" is a fixed collection that supports multiple values, where each entry requires a single domain string.
Output
The node outputs JSON data representing the result of the certificate creation request. This typically includes details about the created certificate such as its ID, associated domains, status, and other metadata returned by the Nginx Proxy Manager API.
No binary data output is indicated for 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 access token.
- The node uses the NPM API token authentication mechanism internally.
- Proper API permissions are necessary to create certificates on the NPM server.
Troubleshooting
- Login failed: No token received: This error occurs if authentication to the NPM API fails. Verify that the provided credentials (email, password, and URL) are correct and that the NPM instance is reachable.
- Invalid domain names: Ensure that all domain names provided are valid and properly formatted.
- API permission errors: If the user account lacks sufficient permissions, certificate creation will fail. Confirm that the API user has rights to manage certificates.
- Network issues: Connectivity problems between n8n and the NPM instance can cause request failures. Check network settings and firewall rules.
Links and References
- Nginx Proxy Manager GitHub Repository
- Nginx Proxy Manager API Documentation (if available)
- Let's Encrypt Documentation (for understanding certificate issuance)
Note: The summary focuses on the Certificate resource's Create operation using custom domain input, based on static analysis of the provided source code and property definitions.