Portainer icon

Portainer

Interact with Portainer via API

Actions190

Ssl → SSL Update

AI-generated

Overview

This node interacts with the Portainer API to update SSL settings. It is designed to send custom SSL configuration data to Portainer, allowing users to programmatically manage SSL parameters for their container environments. This can be particularly useful in automated deployment pipelines or infrastructure management workflows where SSL configurations need to be updated dynamically without manual intervention.

For example, a user might use this node to update SSL certificates or change SSL-related options on their Portainer-managed containers as part of a continuous integration/continuous deployment (CI/CD) process.

Properties

Name Meaning
Body SSL Settings in JSON string format. This property contains the SSL configuration data that will be sent in the request body to update the SSL settings.

Output

The node outputs the response from the Portainer API after attempting to update the SSL settings. The output is structured as JSON and typically includes confirmation of the update or details about any errors encountered.

If the API returns binary data (not indicated here), it would represent related SSL files or certificates, but based on the provided code and properties, the output is expected to be JSON only.

Dependencies

  • Requires an active connection to a Portainer instance via its API.
  • Needs an API authentication token or key configured in the node credentials to authorize requests.
  • The base URL for the Portainer API must be set in the node credentials.
  • The node uses the @devlikeapro/n8n-openapi-node package internally to build and handle OpenAPI-based requests.

Troubleshooting

  • Invalid SSL Settings Format: If the "Body" property does not contain valid JSON or the required SSL configuration structure, the API may reject the request. Ensure the JSON string is correctly formatted and matches Portainer's expected schema.
  • Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Verify that the API key/token and base URL are correctly configured.
  • Network Issues: Connectivity problems to the Portainer server will prevent the node from completing the request. Check network access and firewall settings.
  • API Changes: If Portainer updates their API, some fields or endpoints might change, causing errors. Keep the node and API documentation up to date.

Links and References

Discussion