DNS: Add Hetzner cloud#892
Merged
timkimber merged 3 commits intosrvrco:masterfrom May 2, 2026
Merged
Conversation
Getssl supports Hetzner DNS API, but they are phrasing out[^1] the DNS API. This adds support for Hetzner's Cloud API[^2] to manage zones to add and remove ACME DNS records. [^1]: https://docs.hetzner.com/networking/dns/migration-to-hetzner-console/process/ [^2]: https://docs.hetzner.cloud/reference/cloud#tag/zones Similar to the Hetzner DNS API integration, this works by setting additional environment variables either within the global `.getssl` config file, or certificate-specific `getssl.cfg` file. - `HETZNER_KEY`: Required, set project-specific API key. - `HETZNER_ZONE_ID`: The numeric zone ID - `HETZNER_ZONE_NAME`: If `HETZNER_ZONE_ID` is not provided, the zone ID will be fetched by searching for this name. This may not work reliably, and setting `HETZNER_ZONE_ID` is recommended. Either `HETZNER_ZONE_ID` or `HETZNER_ZONE_ID` _must_ be set. The system also must have `jq` installed.
|
Your way of setting txtname="_acme-challenge.$fulldomain"
txtname="${txtname%.$zone_name}" |
Member
@xrat Thanks for pointing this out, I've just tested and the script only works for 2 level domains (e.g. |
Buypass.no have stopped selling SSL certificates and their API now returns 404 not found
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Getssl supports Hetzner DNS API, but they are phrasing out1 the DNS API.
This adds support for Hetzner's Cloud API2 to manage zones to add and remove ACME DNS records.
Similar to the Hetzner DNS API integration, this works by setting additional environment variables either within the global
.getsslconfig file, or certificate-specificgetssl.cfgfile.HETZNER_KEY: Required, set project-specific API key.HETZNER_ZONE_ID: The numeric zone IDHETZNER_ZONE_NAME: IfHETZNER_ZONE_IDis not provided, the zone ID will be fetched by searching for this name. This may not work reliably, and settingHETZNER_ZONE_IDis recommended.Either
HETZNER_ZONE_IDorHETZNER_ZONE_IDmust be set.The system also must have
jqinstalled.Footnotes
https://docs.hetzner.com/networking/dns/migration-to-hetzner-console/process/ ↩
https://docs.hetzner.cloud/reference/cloud#tag/zones ↩