Closed mw-0 closed 10 months ago
@mw-0 Do you get a specific error message in the pod logs?
When I have a chance, I will compare the versions and see if I can spot differences. One suspicion might be minimum TLS versions; do you know what is supported by your server?
@zachomedia The only error on the challenge is Error presenting challenge: failed loading existing records for _acme-challenge.host.sub.domain.net. in domain sub.domain.net.: failed loading zone sub.domain.net.:
On the web hook pod there is no errors it just keeps repeating lines starting Presenting challenge:
I have enabled all TLS1-1.3 to test and it makes no difference.
Hm, that's interest @mw-0. I expected to see a more specific error message, but it looks like that part is empty.
Would it be possible to share more about your setup?
I'll see if I can reproduce the setup.
As nothing has been heard on this for a while, I'm going to close the issue. If you have any further issues, please don't hesitate to reach out.
If I use http for the api it works fine. My pdns api is already behind a public certificate so I didn't add any certificate bundle to the release. If I exec into the web hook container and add curl I can access the https endpoint without problem.
I tested a few older versions and found that v1.0.0 of the container works ok with https but all after that are broken. Is there any other debugging I can enable here?