Certbot DNS Plugin for Hetzner Cloud DNS
This is a Certbot DNS plugin for the new Hetzner Cloud DNS, which allows you to automate the process of obtaining and renewing SSL/TLS certificates using the DNS-01 challenge method. This Plugin is not compatible with the old Hetzner DNS Console and you might want to take a look at the certbot-dns-hetzner plugin instead.
Setup
Installation
To install the Certbot DNS plugin for Hetzner Cloud DNS, you can either use pip or snap.
Installation using pip
If you installed Certbot within a virtual environment (e.g., /opt/certbot) as per official Certbot instructions
you can install the plugin using the following command:
/opt/certbot/bin/pip install certbot-dns-hetzner-cloud
Installation using snap
If you installed Certbot using snap, you can install the plugin with the following commands:
sudo snap install certbot-dns-hetzner-cloud
sudo snap set certbot trust-plugin-with-root=ok
sudo snap connect certbot:plugin certbot-dns-hetzner-cloud
Verify installation
After installation, you can verify that the plugin is available by running:
certbot plugins
you should see dns-hetzner-cloud listed among the available plugins.
Storing the API Token
Create a configuration file under /etc/letsencrypt/hetzner-cloud.ini with the following content:
# Hetzner Cloud API Token
dns_hetzner_cloud_api_token = your_api_token_here
Make sure to set the correct permissions for the configuration file to protect your API token:
sudo chmod 600 /etc/letsencrypt/hetzner_cloud.ini
If you want to use a different path for the configuration file, you can specify it using the --dns-hetzner-cloud-credentials option when running Certbot.
Usage
You can use the plugin with Certbot by specifying the dns-hetzner-cloud authenticator.
Here is an example command to obtain a certificate for a wildcard subdomain:
certbot certonly --agree-tos \
--authenticator dns-hetzner-cloud \
-d '*.example.eu'
If you want to use a different path for the configuration file, you can specify it using the
--dns-hetzner-cloud-credentials option.
certbot certonly --agree-tos \
--authenticator dns-hetzner-cloud \
--dns-hetzner-cloud-credentials /path/to/your/hetzner_cloud.ini \
-d '*.example.eu'
Metadata
Release files for certbot-dns-hetzner-cloud 1.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| certbot_dns_hetzner_cloud-1.0.5.tar.gz | 15.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| certbot_dns_hetzner_cloud-1.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.1 kB
Release files / certbot_dns_hetzner_cloud-1.0.5.tar.gz
| Download URL | certbot_dns_hetzner_cloud-1.0.5.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18f1c8b9e763f16f3f37ee7190d14c2f7eb15ce28200d6aaf90448a6d6316b13
|
|
BLAKE2b-256 checksum How to use checksums |
fb13bbae2f44d85b2c4ee63d3580a620b627f1b561b81bd53af910bf57fe027d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 3, 2026.
Transparency logRelease files / certbot_dns_hetzner_cloud-1.0.5-py3-none-any.whl
| Download URL | certbot_dns_hetzner_cloud-1.0.5-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cddc57a499c12c4a34bc1dc8ec26864d3dd41d7ff014a650966495fe29ce38ea
|
|
BLAKE2b-256 checksum How to use checksums |
ee3cc4eb96fb4df54e05587201d7a21be20a8c705883f28416989e6ed9a7b305
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 3, 2026.
Transparency log