actions-marketplace-validations/Issue Certificates via Let's Encrypt DNS + cPanel

Issues a certificate through Let's Encrypt using DNS entries via the cPanel API. Resultant private key is saved to secrets.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stalelast commit Apr 13, 2021
License
Public domain

Pinned Snippet

workflow.ymlSHA-pinned
uses: actions-marketplace-validations/cinderblockgames_letsencrypt-dns-cpanel-action@1989804ce76d087e1c184097efe33784d4ee095c # no releases — HEAD as of 2026-07-13

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
hostHost portion of the cPanel server.yes
portPort for the cPanel server.no2083
cpanelUsernameUsername for the cPanel server.yes
cpanelApiTokenAPI Token for the cPanel server.yes
domainDomain under which to place the DNS verification on the cPanel server.yes
acmeAccountEmailAddressThe email address to associate with the account when communicating with Let's Encrypt. REQUIRED if AcmeAccountKey is not provided.no
acmeAccountKeyPathThe file holding the key associated with the account to use when communicating with Let's Encrypt. REQUIRED if AcmeAccountEmailAddress is not provided.no
certCNThe common name to be used for the issued certificate.yes
certDomainListThe domains to be included in the issued certificate, separated by a pipe (|) character.yes
certOrgThe organization to be included for the issued certificate.yes
certOUThe unit within the organization to be included for the issued certificate.yes
certLocalityThe locality in which the ogranization is located, to be included for the issued certificate.yes
certStateThe state in which the ogranization is located, to be included for the issued certificate.yes
certCountryThe country in which the ogranization is located, to be included for the issued certificate.yes
certPasswordThe password to apply to the issued PFX.no""
certKeyAlgorithmAlgorithm to use for private key. See options at https://github.com/fszlin/certes/blob/master/src/Certes/KeyAlgorithm.cs.noES256
githubAccessTokenPersonal Access Token with repo access for GitHub secrets access.yes
secretsRepoRepo in which to store outputs from this Action.yes
acmeAccountKeyNameName to use when saving the ACME account key as a secret in SecretsRepo.noACME_ACCOUNT_KEY
publicChainNameName to use when saving the certificate's public chain as a secret in SecretsRepo.noCERT_PUBLIC_CHAIN
privateKeyNameName to use when saving the certificate's private key as a secret in SecretsRepo.noCERT_PRIVATE_KEY

no outputs