- 11 Feb, 2020 5 commits
-
-
neil authored
Initial support for Synology DSM deployhook
-
neil authored
fix #2031 dns_me id parse
-
neil authored
All inkl kasserver dns script
-
neil authored
-
Brian Hartvigsen authored
-
- 10 Feb, 2020 1 commit
-
-
neil authored
Add DNS API support for Constellix
-
- 09 Feb, 2020 14 commits
-
-
Blfrg authored
Locate only the outer most "id" property
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
This is a lot more fragile then the previous code due to treating JSON as just a string
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
-
Brian Hartvigsen authored
This allows you to update a key on a Synology DSM using the existing API. Handles restarting the necessary services the certificate is attached to and all other internal stuff (copying the certificate around, etc.) This is way less error prone than most articles I've found on how to update a Synology DSM certificate.
-
-
- 08 Feb, 2020 2 commits
- 31 Jan, 2020 4 commits
- 30 Jan, 2020 6 commits
- 27 Jan, 2020 8 commits
-
-
neil authored
fix 2695
-
neilpang authored
-
neilpang authored
-
neil authored
sync
-
neilpang authored
-
https://github.com/Neilpang/acme.sh/issues/2695neilpang authored
If a domain was already verified by http-01 method, when we try to issue a cert for them same domain with dns-01 method, we just get only one challenge object of type http-01 with "valid" status, from the authz-v3 url. So, we report error that we are not able the validate the domain, because of that we don't find dns-01 challenge. This behavior is not the same as before. I believe it was changed by the letsencrypt CA.
-
neilpang authored
-
neilpang authored
-