Open lcx opened 4 months ago
ok Seems this is actually coming from certbot-dns-ispconfig and there is already an issue and is suppossedly already fixed but pip install
get's the wrong (older) version. Guess this can be closed as I don't see why and how nginx-proxy-manager could fix that.
There is a new version of the certbot-dns-ispconfig
plugin. Is there anything to do in this project to test and use this version?
Describe the bug
Using ISPConfig as DNS Challenge for a wildcard Let's Encrypt certificate request fails with
The reason for this is that the
stamp
is a Timestamp field but no value is provided in the API request.I have reported this with ISPConfig as well and also posted a workaround here
As far as I could debug the API call it sends the
_acme-challenge
+ the key that is added in the text field which makes ISPconfig use the provided default value of '' that lead to the mysql Error.Versions
Nginx Proxy Manager Version: v2.11.3 ISPConfig: v3.2.12
To Reproduce Steps to reproduce the behavior:
How can I help?
If someone shows me where the ISPConfig thing is in NPM I could try to create a pull request since I have a ISPConfig at my disposition to test with.