Package: certbot-dns-ispconfig
ISPConfigDNS Authenticator plugin for CertbotThis plugin automates the process of completing adns-01challenge by
creating, and subsequently removing, TXT records using the ISPConfig Remote API.Configuration of ISPConfigIn theSystem -> Remote Usersyou have to have a user, with the following rightsClient FunctionsDNS zone functionsDNS txt functionsInstallationpip install certbot-dns-ispconfigNamed ArgumentsTo start using DNS authentication for ispconfig, pass the following arguments on
certbot’s command line:--authenticatorcertbot-dns-ispconfig:dns-netcupselect the authenticator plugin (Required)--certbot-dns-ispconfig:dns-ispconfig-credentialsispconfig Remote User credentials
INI file. (Required)--certbot-dns-ispconfig:dns-ispconfig-propagation-secondswaiting time for DNS to propagate before askingthe ACME server to verify the DNS record.(Default: 10, Recommended: >= 600)(Note that the verbose and seemingly redundantcertbot-dns-ispconfig:prefix
is currently imposed by certbot for external plugins.)CredentialsAn examplecredentials.inifile:certbot_dns_ispconfig:dns_ispconfig_username = myremoteusercertbot_dns_ispconfig:dns_ispconfig_password = verysecureremoteuserpasswordcertbot_dns_ispconfig:dns_ispconfig_endpoint = https://localhost:8080The path to this file can be provided interactively or using the--certbot-dns-ispconfig:dns-ispconfig-credentialscommand-line argument. Certbot
records the path to this file for use during renewal, but does not store the
file’s contents.CAUTION:You should protect these API credentials as you would the
password to your ispconfig account. Users who can read this file can use these
credentials to issue arbitrary API calls on your behalf. Users who can cause
Certbot to run using these credentials can complete adns-01challenge to
acquire new certificates or revoke existing certificates for associated
domains, even if those domains aren’t being managed by this server.Certbot will emit a warning if it detects that the credentials file can be
accessed by other users on your system. The warning reads “Unsafe permissions
on credentials configuration file”, followed by the path to the credentials
file. This warning will be emitted each time Certbot uses the credentials file,
including for renewal, and cannot be silenced except by addressing the issue
(e.g., by using a command likechmod 600to restrict access to the file).ExamplesTo acquire a single certificate for bothexample.comand*.example.com, waiting 900 seconds for DNS propagation:certbotcertonly\\--authenticatorcertbot-dns-netcup:dns-netcup\\--certbot-dns-netcup:dns-netcup-credentials~/.secrets/certbot/netcup.ini\\--certbot-dns-netcup:dns-netcup-propagation-seconds900\\--serverhttps://acme-v02.api.letsencrypt.org/directory\-d'example.com'\\-d'*.example.com'DockerIn order to create a docker container with a certbot-dns-ispconfig installation,
create an empty directory with the followingDockerfile:FROMcertbot/certbotRUNpipinstallcertbot-dns-ispconfigProceed to build the image:docker build -t certbot/dns-ispconfig .Once that’s finished, the application can be run as follows:docker run --rm \
   -v /var/lib/letsencrypt:/var/lib/letsencrypt \
   -v /etc/letsencrypt:/etc/letsencrypt \
   --cap-drop=all \
   certbot/dns-ispconfig certonly \
   --authenticator certbot-dns-ispconfig:dns-ispconfig \
   --certbot-dns-ispconfig:dns-ispconfig-propagation-seconds 900 \
   --certbot-dns-ispconfig:dns-ispconfig-credentials \
       /var/lib/letsencrypt/ispconfig_credentials.ini \
   --no-self-upgrade \
   --keep-until-expiring --non-interactive --expand \
   --server https://acme-v02.api.letsencrypt.org/directory \
   -d example.com -d '*.example.com'You may want to change the volumes/var/lib/letsencryptand/etc/letsencryptto local directories where the certificates and
configuration should be stored.