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
{{ message }}
This repository has been archived by the owner on Feb 3, 2025. It is now read-only.
Deployed using Helm chart v1.0.1 with image set to ghcr.io/rkosegi/cert-manager-webhook-active24:v1.0.1 (you've got it wrong in the v1.0.1 - it points to rkosegi/cert-manager-webhook-active24:1.0.1 which doesn't exist).
API key is correct (issued last year, still valid)
ClusterIssuer also appears correct (created last year, not changed since then)
Note that I can't find the expected TXT record there - based on the above piece of log it should be at least created, but there's nothing visible in those records. Maybe even that part doesn't work properly, or it's just a consequence.
The text was updated successfully, but these errors were encountered:
Petr, thanks for bug report.
I can confirm issue. Not sure about root cause, I'm sure this worked before.
Even stranger is what you pointed out already, swagger UI or curl are producing OK results while pretty same requests coming from this app not. Let me do more tests
Recently I started having issues with the certificate renewal (worked a few months ago, but not any longer).
ghcr.io/rkosegi/cert-manager-webhook-active24:v1.0.1
(you've got it wrong in the v1.0.1 - it points torkosegi/cert-manager-webhook-active24:1.0.1
which doesn't exist).Do you know if the Active24 API hasn't changed in any way?
I looked at https://api.active24.com/swagger-ui.html and tried some manual requests to get some records (using my API key) - those work and it appears to match what the https://github.com/rkosegi/active24-go/blob/main/active24/dns.go does. But maybe I'm missing something.
Note that I can't find the expected TXT record there - based on the above piece of log it should be at least created, but there's nothing visible in those records. Maybe even that part doesn't work properly, or it's just a consequence.
The text was updated successfully, but these errors were encountered: