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 certificates, proxy hosts, access lists, and more. Specifically, the Certificate - Get operation retrieves detailed information about a particular SSL certificate managed by NPM. This is useful for scenarios where you need to programmatically fetch certificate details for monitoring, auditing, or automation purposes.

For example, you might use this node to:

  • Retrieve certificate details by ID to verify expiration dates.
  • Fetch additional related data like the certificate owner.
  • Filter certificates by name when querying multiple entries.

Properties

Name Meaning
ID The unique numeric identifier of the certificate to retrieve. This is required.
Additional Fields Optional extra parameters to customize the request:
- Expand Owner Boolean option to include detailed information about the certificate's owner.
- Filter A string filter to narrow down results by certificate name (used mainly in get_many).

Output

The node outputs JSON data representing the certificate details retrieved from the NPM API. The structure typically includes fields such as:

  • Certificate ID
  • Domain names covered by the certificate
  • Expiration date
  • Issuer information
  • Owner details (if expanded)
  • Status and other metadata

If the "Expand Owner" option is enabled, the output will also contain nested information about the certificate owner.

No binary data output is expected from this operation.

Dependencies

  • Requires an active connection to an Nginx Proxy Manager instance.
  • Needs credentials including the URL, email, and password for authentication.
  • The node authenticates by requesting a token from the NPM API before making further requests.
  • No additional external services are required beyond the NPM API.

Troubleshooting

  • Login failed: No token received: Indicates that authentication with the NPM API failed. Verify that the provided credentials (URL, email, password) are correct and that the NPM instance is reachable.
  • Invalid or missing ID: Ensure the certificate ID is provided and corresponds to an existing certificate in NPM.
  • Network errors or timeouts: Check network connectivity to the NPM server and ensure the API endpoint is accessible.
  • If filtering by name returns no results, confirm the filter string matches existing certificate names.

Links and References

Discussion