Namecheap icon

Namecheap

Consume Namecheap API

Overview

The node integrates with the Namecheap API to manage SSL certificates, specifically supporting operations such as reissuing an SSL certificate. The "Reissue" operation allows users to request a new SSL certificate based on a new Certificate Signing Request (CSR). This is useful when you need to replace or update an existing certificate without changing the domain or other certificate details.

Common scenarios include:

  • Renewing or updating an SSL certificate after changing server configurations.
  • Replacing a compromised or lost private key by generating a new CSR and reissuing the certificate.
  • Changing the validation method or approver email during the certificate lifecycle.

Example use case: A user has an expiring SSL certificate and wants to generate a new CSR with updated information, then reissue the certificate using this new CSR and specify the preferred domain control validation method.

Properties

Name Meaning
Certificate ID The unique identifier of the SSL certificate to be reissued.
CSR The Certificate Signing Request in PEM format, containing the public key and identifying info for the new certificate.
DCV Method The Domain Control Validation method used to verify domain ownership. Options: DNS, Email, HTTP, HTTPS.
Approver Email The email address used for domain validation when the DCV method is set to Email.

Output

The node outputs a JSON object with the following structure:

{
  "success": true,
  "data": { ... }
}
  • success: Boolean indicating whether the reissue operation was successful.
  • data: Contains the response data from the Namecheap API related to the reissued SSL certificate. This typically includes details about the certificate status, validation instructions, and any relevant metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Namecheap API.
  • Needs an API authentication credential configured in n8n to authorize requests.
  • The node depends on the bundled internal classes that handle SSL-related API calls.

Troubleshooting

  • Missing or invalid Certificate ID: Ensure the correct certificate ID is provided; otherwise, the API will reject the request.
  • Invalid CSR format: The CSR must be in valid PEM format; malformed CSRs will cause errors.
  • Incorrect DCV method or missing approver email: If using Email validation, the approver email must be specified and valid.
  • API authentication errors: Verify that the API credentials are correctly configured and have sufficient permissions.
  • Network or API downtime: Temporary connectivity issues may cause failures; retry after some time.

Common error messages might include:

  • "The operation 'reissue' is not known for resource 'ssl'" — indicates a misconfiguration or typo in operation name.
  • "Certificate ID is required" — missing required input.
  • "CSR format invalid" — CSR content does not meet expected format.

Resolving these usually involves verifying input parameters and ensuring proper API credentials.

Links and References

Discussion