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 interact programmatically with various resources managed by NPM. Specifically for the Log - Get operation, it retrieves log entries from the NPM system. This is useful for monitoring access, debugging issues, or auditing activities on your proxy hosts.

Typical use cases include:

  • Fetching recent logs to analyze traffic patterns.
  • Filtering logs by user or query string to troubleshoot specific requests.
  • Automating log retrieval for external reporting or alerting systems.

Properties

Name Meaning
Additional Fields A collection of optional parameters to customize the log retrieval:
- Expand User Boolean option to include detailed user information in the log results.
- Filter A string to filter logs by name or other criteria, narrowing down the returned entries.

Note: The "Additional Fields" property only appears when the resource is "logs" and the operation is "get_many".

Output

The node outputs a JSON array where each element represents a log entry retrieved from the Nginx Proxy Manager. Each log entry typically contains details such as timestamps, request information, status codes, and optionally expanded user data if requested.

If binary data were involved (e.g., log files), it would be indicated here, but this node returns structured JSON log data only.

Dependencies

  • Requires an API key credential with email and password to authenticate against the Nginx Proxy Manager API.
  • The node performs an initial login POST request to /api/tokens to obtain a bearer token used for subsequent API calls.
  • The base URL for the NPM instance must be configured in the credentials.
  • No additional external dependencies beyond the NPM API are required.

Troubleshooting

  • Login failed: No token received: This error indicates that authentication to the NPM API failed. Verify that the provided email, password, and URL in the credentials are correct and that the NPM instance is reachable.
  • Empty or no logs returned: Check the filter criteria; overly restrictive filters may result in no matching logs.
  • API connection errors: Ensure network connectivity to the NPM server and that the API endpoint is accessible.
  • If expanding user data, ensure the user information exists and is accessible via the API.

Links and References

Discussion