You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hetzner DNS Console API is deprecated and it appears AMCE challenges are failing (at least I suspect that might be the cause for #806)
libdns/hetzner has implemented support for the new Hetzner DNS Cloud API: libdns/hetzner@43c0630
maddy needs to use "github.com/libdns/hetzner/v2" now instead. But it appears that causes a terrible dependency update chain. I have not had success building maddy after such an update.
maddy needs to use "github.com/libdns/hetzner/v2" now instead. But it appears that causes a terrible dependency update chain. I have not had success building maddy after such an update.
New library requires Go 1.24. I guess it's time to upgrade.
libdns/hetzner/v2 is based on libdns 1.1, while maddy uses pre-1.0 libdns. libdns/vultr is also apparently stuck on pre-1.0 libdns. So currently it is either hetzner or vultr libdns.
Judging by the fact this issue is almost a year old: libdns/vultr#4, it is unlikely to be updated by the original maintainer.
So, here is the plan. I will tag 0.9.1 with old hetzner and pre-1.0 libdns then will build oddly named 0.9.1-libdns1 release that updates to libdns 1.0, dropping providers mentioned above and adding hetzner/v2. 0.10.0 will use libdns 1.x and will therefore also drop them - 0.9.1 will be the last release to support old hetzner API along with providers mentioned above (unless they all update to libdns 1.x).
Hetzner ACME renewal is broken for the last couple of months. Band aid is to schedule renewal on the host, then copy certs over to maddys volume. Is there anything still preventing a bump to a recent Hetzner libdns release?
Activity
hasufell commentedon Dec 6, 2025
Also see acmesh-official/acme.sh#6554
feat: Add new issues for bug reports and feature requests
foxcpp commentedon Jan 6, 2026
New library requires Go 1.24. I guess it's time to upgrade.
foxcpp commentedon Mar 25, 2026
libdns/hetzner/v2 is based on libdns 1.1, while maddy uses pre-1.0 libdns. libdns/vultr is also apparently stuck on pre-1.0 libdns. So currently it is either hetzner or vultr libdns.
Judging by the fact this issue is almost a year old: libdns/vultr#4, it is unlikely to be updated by the original maintainer.
foxcpp commentedon Mar 25, 2026
libdns providers incompatible with libdns 1.x:
foxcpp commentedon Mar 25, 2026
So, here is the plan. I will tag 0.9.1 with old hetzner and pre-1.0 libdns then will build oddly named 0.9.1-libdns1 release that updates to libdns 1.0, dropping providers mentioned above and adding hetzner/v2. 0.10.0 will use libdns 1.x and will therefore also drop them - 0.9.1 will be the last release to support old hetzner API along with providers mentioned above (unless they all update to libdns 1.x).
feat(container): update image ghcr.io/foxcpp/maddy ( 0.8.2 → 0.9.5 ) …
paxbit commentedon Sep 24, 2026
0.9.5 still uses the inital libdns Hetzner API 0.0.1.
https://github.com/foxcpp/maddy/blob/v0.9.5/go.mod#L41
The library is currently released at 2.0.1:
https://github.com/libdns/hetzner/releases
Hetzner ACME renewal is broken for the last couple of months. Band aid is to schedule renewal on the host, then copy certs over to maddys volume. Is there anything still preventing a bump to a recent Hetzner libdns release?