Actions38
- Access List Actions
- Certificate Actions
- Dead Host Actions
- Log Actions
- Proxy Host Actions
- Redirection Host Actions
- Setting Actions
- User Actions
Overview
The 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, the Access List - Update operation enables updating an existing access list by its ID. This is useful for modifying access control rules, such as changing authorized users or IP addresses allowed to access certain services.
Practical examples include:
- Updating an access list to add or remove user credentials.
- Changing IP subnet restrictions dynamically.
- Modifying authentication requirements like "Satisfy Any" or "Pass Auth" flags.
Properties
| Name | Meaning |
|---|---|
| ID | The unique numeric identifier of the access list to update. |
| Name | The new name for the access list. |
| Satisfy Any | Boolean flag indicating if any one of the authorization items is sufficient to grant access. |
| Pass Auth | Boolean flag indicating whether to pass authentication through. |
| Authorization | A collection of username/password pairs that define authorized users. Multiple entries allowed. |
| Access | A collection of client IP addresses or subnets allowed access, each with a directive (default "allow"). Multiple entries allowed. |
Output
The node outputs JSON data representing the result of the update operation on the access list. This typically includes confirmation of success and details of the updated access list object as returned by the NPM API.
No binary data output is involved in this operation.
Dependencies
- Requires connection to an Nginx Proxy Manager instance.
- Needs valid API credentials (email and password) to authenticate and obtain a token.
- The node uses HTTP requests to communicate with the NPM API endpoint configured via credentials.
Troubleshooting
- Login failed: No token received: Indicates authentication failure. Verify the email and password credentials are correct and that the NPM instance URL is reachable.
- Invalid ID or resource not found: Ensure the provided access list ID exists in the NPM instance.
- Missing required fields: Make sure all required properties, especially authorization and clients collections, are properly filled.
- Network errors or timeouts may occur if the NPM server is unreachable or misconfigured.
Links and References
- Nginx Proxy Manager GitHub
- Nginx Proxy Manager API Documentation (if available)