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 resources such as access lists, certificates, proxy hosts, and users. Specifically, for the User resource and the Update Password operation, it enables updating a user's password in the NPM system. This is useful for automating user management tasks, such as resetting passwords or enforcing security policies programmatically.
Practical examples include:
- Automatically resetting user passwords on a schedule.
- Integrating password updates into a broader user lifecycle management workflow.
- Synchronizing user credentials between NPM and other systems.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the user whose password will be updated. |
| Password | The new password string to set for the specified user. |
Output
The node outputs JSON data representing the result of the password update operation. Typically, this includes confirmation of success or details about the updated user. The exact structure depends on the NPM API response but generally contains fields indicating whether the password change was successful.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to an Nginx Proxy Manager instance.
- Needs valid API authentication credentials (an email and password) to obtain an access token before performing operations.
- The node uses HTTP requests to communicate with the NPM API endpoints.
Troubleshooting
- Login failed: No token received: This error indicates that authentication with the NPM API failed. Verify that the provided API credentials (email and password) are correct and that the NPM instance URL is reachable.
- Invalid User ID: If the specified user ID does not exist, the API may return an error. Ensure the user ID is correct and corresponds to an existing user.
- Password Policy Violations: The NPM API might reject passwords that do not meet its complexity requirements. Check the password format and try again.
- Network Issues: Connectivity problems between n8n and the NPM server can cause request failures. Confirm network accessibility and firewall settings.
Links and References
- Nginx Proxy Manager GitHub Repository
- Nginx Proxy Manager API Documentation (if available)
- n8n Documentation for general node usage and credential setup guidance