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 NPM resources programmatically. Specifically, the Dead Host - Create operation enables users to add one or more domain names as "dead hosts" in the NPM system. Dead hosts typically represent domains that should not be proxied or are intentionally disabled.

Common scenarios for this node include automating the management of domains that should be blocked or marked inactive within a proxy environment, such as during maintenance windows or when decommissioning services. For example, a user might create dead hosts to prevent traffic routing to deprecated domains without manually updating the NPM UI.

Properties

Name Meaning
Domain Names A collection of one or more domain names to be added as dead hosts. Each domain is specified individually.
Options Additional configuration options for the dead host:
  SSL Forced Boolean flag to force SSL usage on the dead host.
  HTTP2 Support Boolean flag to enable HTTP/2 support.
  HSTS Enable Boolean flag to enable HTTP Strict Transport Security (HSTS).
  HSTS Subdomains Boolean flag to apply HSTS policy to subdomains.
  Certificate ID Numeric ID referencing an SSL certificate to associate with the dead host.
  Advanced Config Free-text field for advanced custom configuration in raw format.

Output

The node outputs a JSON array containing the result of the create operation. The exact structure depends on the response from the NPM API but generally includes confirmation of success and details about the created dead host(s).

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to an Nginx Proxy Manager instance.
  • Needs credentials including URL, email, and password to authenticate via the NPM API.
  • The node internally obtains an authentication token by posting credentials to the /api/tokens endpoint before performing operations.
  • No additional external dependencies beyond the NPM API and proper credential setup.

Troubleshooting

  • Login failed: No token received
    This error indicates that authentication with the NPM API failed. Verify that the provided URL, email, and password credentials are correct and that the NPM instance is reachable.

  • Invalid domain input
    Ensure that domain names are valid strings and properly formatted. Empty or malformed domain entries may cause API errors.

  • Permission issues
    The API user must have sufficient permissions to create dead hosts. Check user roles and access rights in the NPM instance.

  • Network connectivity
    Confirm that the n8n instance can reach the NPM server URL and that no firewall or network restrictions block the requests.

Links and References

Discussion