Nginx Proxy Manager (NPM) icon

Nginx Proxy Manager (NPM)

Interact with your NPM instance
Join our community

Actions38

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 Renew Certificate operation under the Certificate resource, the node enables renewing an existing SSL/TLS certificate managed by NPM. This is useful in scenarios where certificates are about to expire or need to be refreshed to maintain secure HTTPS connections.

Practical examples include:

  • Automatically renewing Let's Encrypt certificates before expiration.
  • Refreshing certificates after changes in domain validation.
  • Managing multiple certificates programmatically within an infrastructure automation workflow.

Properties

Name Meaning
ID The unique numeric identifier of the certificate to renew. This property is required to specify which certificate should be renewed.

Output

The node outputs a JSON array containing the response from the Nginx Proxy Manager API related to the renewal request. Typically, this includes details about the renewed certificate such as its new expiration date, status, and any relevant metadata returned by the API.

If the node supports binary data output (not explicitly shown here), it would likely relate to certificate files or keys, but based on the provided code and properties, the output is JSON only.

Dependencies

  • Requires an active Nginx Proxy Manager instance accessible via its API.
  • Needs credentials including a URL, email, and password to authenticate and obtain an API token.
  • The node uses HTTP requests to interact with the NPM API endpoints.
  • Proper configuration of the API credentials in n8n is necessary for successful authentication and operations.

Troubleshooting

  • Login failed: No token received: This error indicates that authentication with the NPM API failed, possibly due to incorrect credentials or network issues. Verify the API URL, email, and password are correct and that the NPM instance is reachable.
  • Invalid certificate ID: If the specified certificate ID does not exist or is invalid, the API may return an error. Ensure the ID corresponds to an existing certificate.
  • Network or API errors: Timeouts or connectivity problems can cause failures. Check network settings and API availability.
  • Permission issues: The API user must have sufficient permissions to renew certificates.

Links and References

Discussion